CN1645819A - Rapid and convenient communication network managing method - Google Patents
Rapid and convenient communication network managing method Download PDFInfo
- Publication number
- CN1645819A CN1645819A CN 200510018165 CN200510018165A CN1645819A CN 1645819 A CN1645819 A CN 1645819A CN 200510018165 CN200510018165 CN 200510018165 CN 200510018165 A CN200510018165 A CN 200510018165A CN 1645819 A CN1645819 A CN 1645819A
- Authority
- CN
- China
- Prior art keywords
- management
- alarm
- network element
- objects
- performance
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000004891 communication Methods 0.000 title claims abstract description 8
- 238000007726 management method Methods 0.000 claims abstract description 160
- 230000006870 function Effects 0.000 claims abstract description 20
- 230000004044 response Effects 0.000 claims description 35
- 230000009471 action Effects 0.000 claims description 19
- 238000012217 deletion Methods 0.000 claims description 11
- 230000037430 deletion Effects 0.000 claims description 11
- 230000000875 corresponding effect Effects 0.000 claims 2
- 230000000873 masking effect Effects 0.000 claims 1
- 230000003993 interaction Effects 0.000 abstract 1
- 230000008859 change Effects 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- 238000007667 floating Methods 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 3
- 102100031184 C-Maf-inducing protein Human genes 0.000 description 2
- 101000993081 Homo sapiens C-Maf-inducing protein Proteins 0.000 description 2
- 230000007812 deficiency Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000007493 shaping process Methods 0.000 description 2
- 241001269238 Data Species 0.000 description 1
- 208000019209 Monosomy 22 Diseases 0.000 description 1
- 101100311330 Schizosaccharomyces pombe (strain 972 / ATCC 24843) uap56 gene Proteins 0.000 description 1
- 238000009825 accumulation Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- IXSZQYVWNJNRAL-UHFFFAOYSA-N etoxazole Chemical compound CCOC1=CC(C(C)(C)C)=CC=C1C1N=C(C=2C(=CC=CC=2F)F)OC1 IXSZQYVWNJNRAL-UHFFFAOYSA-N 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000005728 strengthening Methods 0.000 description 1
- 101150018444 sub2 gene Proteins 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明公开了一种方便快捷的通信网络管理方法，涉及一种通信网络管理方法，由一套管理信息模型的建立方法和一种自主定义网络管理协议组成；所述的一套管理信息模型的建立方法，即用面向对象的方法将被管对象建模成特定形式的管理对象树，将对象分成属性、方法和事件；所述的一种自主定义网络管理协议，即一种称为OML格式的协议。本发明将被管理网络资源抽象成对象，以这样一种特定的面向对象的方法建立起管理信息模型，并且通过简捷高效的网络管理协议实现管理端与代理端的交互，从而更简捷有效地实现了网络管理的五大基本功能。
The invention discloses a convenient and quick communication network management method, relates to a communication network management method, which is composed of a method for establishing a management information model and a self-defined network management protocol; the set of management information model The establishment method is to use the object-oriented method to model the managed object into a specific form of management object tree, and divide the object into attributes, methods and events; the above-mentioned self-defined network management protocol, that is, a format called OML agreement. The present invention abstracts managed network resources into objects, establishes a management information model with such a specific object-oriented method, and realizes the interaction between the management end and the agent end through a simple and efficient network management protocol, thereby more simply and effectively realizing Five basic functions of network management.
Description
Technical field
The present invention relates to a kind of communication network management method, relate in particular to the foundation of a cover management information model and a kind of NMP of autonomous definition.
Background technology
In the operation process of various communication networks, network management system plays key effect.On network management, mainly contain at present based on SNMP (Simple Network Management Protocol Simple Network Management Protocol) with based on the network management architecture of TMN (Telecommunications Management Network telecommunication management network).
1, based on the network management architecture of SNMP
By manager, agency and management information bank (MIB), management agreement etc. are partly formed.Wherein manager's (managing process) is the person of sending of supervisory instruction, and the agency is in charge of the execution of instruction, and reports some critical events that managed object takes place with the form of notice to the manager.SNMP provides minimum Network Management Function method to put forward as a kind of at first, it is all fairly simple with MIB that SNMP itself reaches the SMI (structure of management information) relevant with SNMP, therefore function is succinct, is easy to realize, is widely used in the management of the Internet at present; But the existing deficiency of itself makes it can't finish complicated management role, also can't be competent at the management of catenet.These deficiencies show:
(1) SNMP MIB only can store simple data type: scalar type and two-dimentional phenotype (its base type is a scalar type), and the information representation of SNMP mib information model is limited in one's ability, the message structure of complexity beyond expression of words;
(2) operational order that provides of SNMP is limited, mainly contains get (getting), get-next (getting the next one), and set (setting), four types of trap (notice) do not support as creating, deletion, the operation of types such as action also is not suitable for the inquiry of bulk information;
(3) trap of SNMP is what do not have to confirm, might cause like this guaranteeing whether very serious alarm sends to the manager, therefore is difficult to guarantee the synchronous and consistency of the information of management end and agent side.
2, based on the network management architecture of TMN
Complete function and powerful, but very complicated, can be described respectively from four aspects, i.e. functional architecture, physical architecture, information architecture and layering logic layers architecture.The basis of TMN technological frame is OSI (Open System Interconnection) network, OSI system management function, system management messages model and system management agreement and service.Basic functions is by agreement exchange of management information between two management entities in the OSI system management.In the OSI system management, this function is CMISE.CMISE is divided into two part: CMIS, describes the service that offers the user, and CMIS provides seven kinds of service primitives altogether; CMIP provides the application layer protocol of management information transmission service, describes the protocol Data Unit of finishing the CMIS service and the process that is associated thereof.It is Management Information Model that the OSI system management is used to define and organize the general framework of MIB, and this Management Information Model has adopted Object-oriented Technique, and use and management object definition guide (GDMO) is described.Each all is defined as management object by the Internet resources of pipe.The TMN architecture is to organize a Network Management system with more general more fully viewpoint, and its target is to handle the integrated management of any complication system.Yet this just large and complete thought causes it that many shortcomings are arranged, and is too big as target, the abstract degree is too high, the description of Management Information Model with realize all more complicated.The function of CMIP is powerful extremely flexibly, makes the OSI method for managing system too complicated, and OSI system management standard has only defined and managed operation one by one independently, as M-GET and M-SET.But do not define the sequence of these operations, to finish the particular problem that the manager will solve.
In sum, this two kinds of management methods or be easy to realize, but function is simple; Powerful, but be difficult to realize.Therefore in the network management practice of reality, press for a kind of both had enough powerful and expandable functions, again the network management that can be realized quickly and easily.
Summary of the invention
Purpose of the present invention just is to overcome the shortcoming and defect of above-mentioned network management, and provide a kind of conveniently communication network management method, be a kind of both had enough powerful and expandable functions, the network management that can be realized quickly and easily again.This method comprises the method for building up of a cover management information model and a kind of NMP of autonomous definition, and the supervisory process model of realizing every network management function.This method makes realization simpler, flexible, convenient, fast when strengthening management function.
The object of the present invention is achieved like this:
Form by the method for building up of a cover management information model and a kind of NMP of autonomous definition.
The foundation of model is will be become the management object (Managed Object) 10 of particular form by the pipe Resource Modeling with OO method, and the group of objects composition is attribute 7, incident 38 and operates 9 (as Fig. 1).According to the logical relation between object (side by side, affiliated) management object is formed tree, be called the management object tree.Except the object (being called entity object) of representing the actual management resource, in order to support specific management function, a series of special management objects 10 have been defined again, their not corresponding certain management resources, but being used for management functions such as support property management, fault management, daily record, this object is called support target 33.Support target 33 has daily record (Log) 34, alarm shield (AlarmMask) 12, current alarm (CurAlarm) 14, history alarm (HistoryAlarm) 18, historical performance management (HistoryPMAdmin) 18, historical performance (HistoryPM) 27, performance threshold values management (Threshold) 29, network element agency (Agent) 36 (as Fig. 5).Management object has also defined some particular community and method such as current performance (CurPM), accumulative total performance (AccPM) 1, and inquiry child node (GetSubNodes) 8 waits the inquiry of finishing current real-time performance information and the traversal of object.To being configured the read-write of information and the inquiry of real-time status, finish some specific function by property operations by method call by the pipe resource.
NMP PDU uses a kind of language description that is called the OML form, and it mainly is made of PDU head and two parts of PDU body: the PDU head is mainly described PDU sign, version, length, sequence number, coding, cipher mode etc., and some is optional; The PDU body is the protocol data part, and main contents have request, acknowledgement type, object identity, parameter, data acquisition system and other additional datas.It has defined the various operations that correspondent keyword comes network enabled to manage, and as inquiry Get, revises Set, action Action, and incident EventReport replys Response, creates Create, deletes Delete; The protocol data type is supported from fundamental type such as integer, floating-point, character string to binary stream, set, tree.
1. build a network element class NE (33), each network element all has the example ID of an integer, the NE type numbering of an expression network element device classification, and it is unified that NE type is numbered the overall situation, a kind of network element device of sign that can be unique;
2. set up following subobject: daily record Log (34) under NE (33) object, alarm shield AlarmMask (12), indicating which alarm will shield, current alarm CurAlarm (14), it is the current alarm of whole NE, history alarm HistoryAlarm (18), write down the alarm history of whole NE, historical performance management HistoryPMAdmin (35), the historical performance management information setting of writing down whole NE, historical performance HistoryPM (27), be the historical performance of whole NE, performance threshold values management Threshold (29) describes the performance threshold values setting of whole NE, network element is acted on behalf of Agent (36), be used to the agency relevant with network element is described for information about, these objects are present in each network element as standard object, realize the log management to whole network element, alarm management, performance management function;
3. based on network element by the concrete structure of management resource, under NE (33) object, set up other subobjects, subobject can comprise lower one-level subobject, has so just formed the structure of a tree type;
4. object consists of attribute, method and incident, at this version, operation at object has Create and Delete (21), the base attribute operation has the read-write (21) (23) of Get and the corresponding attribute of Set, basic skills is to return the information GetSubNodes of lower floor's subobject (8), be used for the support target traversal of tree, elementary event mainly contains attribute change, Object Creation, object deletion (22), and management end carries out the synchronous automatically of data according to these incidents and network element;
5. to each bookkeeping, comprise configuration management, performance management, alarm management, log management, incident sends, and protocol section has all been stipulated corresponding response primitive, guarantees that the integrality of each step operation all is as can be known.
The present invention have the following advantages and good effect:
The managed networks resource is abstracted into object, to be mapped as object properties, method and incident to the management method of resource, set up Management Information Model with a kind of so specific OO method, and realize the mutual of management end and agent side, thereby the simpler and more direct five big basic functions that realized network management effectively by simple and direct NMP efficiently.
Description of drawings
Fig. 1 is the hum pattern of a managed object;
Fig. 2 is fault administrative model figure;
Fig. 3 is configuration management model figure;
Fig. 4 is the performance management illustraton of model;
Fig. 5 is network element object information figure.
Wherein:
1-attribute: current performance, accumulative total performance number (CurPM, AccPM).
The 2-read only attribute is as real-time state etc.
The read-write attribute of 3-is as various configuration amount.
4-attribute change incident makes management end receive new state or the configuration of active synchronization after this incident.
5-alarms change events, makes management end refresh alarm list.
The deletion of 6-object, establishment make management end upgrade local data and network element is consistent.
Other proprietary incident of 7-refers to the peculiar incident of each object.
8-object method (GetSubNodes).
Other proprietary operation of 9-.
The 10-management object.
11-has produced new warning information.
12-alarm shield (AlarmMask).
The 13-alarm filter.
14-current alarm (CurAlarm).
15-alarm change events reports.
16-collects warning information.
17-alarms end: disappear or recovery.
18-history alarm (HistoryAlarm) is charged in the history alarm tabulation.
19-regularly (as 15 minutes) gathers history alarm.
The 20-management system.
21-revises (Set), creates (Create) or deletion (Delete) request.
22-notification event (attribute change incident, Object Creation incident, object deletion event).
23-inquiry, action.
The current real-time performance of 24-(CurPM).
25-gathers current performance and shows at terminal interface.
The 26-current performance is charged to the historical performance tabulation.
27-historical performance object (HistoryPM).
28-regularly gathers historical performance, and deposits system database in.
29-threshold values management object (Threshold).
30-monitors the scope of current performance value.
The 31-performance number is compared with pre-set threshold value, then will produce alarm if exceed the threshold values scope.
32-is according to the setting of alarm shield, and whether decision produces corresponding alarm.
33-network element (NE).
34-daily record object (Log), the log information of a NE inside of record.
35-HistoryPMAdmin is the historical performance management object of whole NE.
36-acts on behalf of (Agent).
Embodiment
1. build a class NE33 for network element, each network element all has the example ID of an integer, the NE type numbering of an expression network element device classification, and it is unified that NE type is numbered the overall situation, a kind of network element device of sign that can be unique;
2. set up following subobject under the NE33 object: daily record (Log) 34, alarm shield (AlarmMask) 12, current alarm (CurAlarm) 14, history alarm (HistoryAlarm) 18, historical performance management (HistoryPMAdmin) 35, historical performance (HistoryPM) 27, performance threshold values management (Threshold) 29, network element agency (Agent) 36, as shown in Figure 5.Alarm shield (AlarmMask) the 12nd, the alarm shield object, indicating which alarm will shield; Current alarm (CurAlarm) the 14th, the current alarm of whole NE; The alarm history of the whole NE of history alarm (HistoryAlarm) 18 records; The historical performance management information of the whole NE of historical performance management (HistoryPMAdmin) 35 records is provided with; Historical performance (HistoryPM) the 27th, the historical performance of whole NE; Performance threshold values management (Threshold) 29 describes the performance threshold values setting of whole NE.Network element agency (Agent) the 36th, agent object is used to the agency relevant with network element is described for information about.
Illustrate the method for definition object class below, can grasp flexibly according to the needs of actual management function.
Can be defined as follows for the current alarm class:
The CurAlarm class definition
Class?CurAlarm
{
Attribute：
Int length:ro current alarm bar number
List items:ro current alarm tabulation Action:
Clear () removes all current alarms
(DN scope) gets the alarm of the object of DN appointment to Get, and scope is that 1 expression is got this
It is the subtree alarm of root that node alarm, 0 expression are got with this node.Return the current alarm table result of a List type.
}
Current alarm list of entries field has:
The time that the begintime:datetime alarm takes place
The object that the object:DNtype alarm takes place
Alarmtype:int alarm type numbering;
The state:int alarm status, once alarm of 0 expression, 1 expression oscillating alarm.
Can be defined as follows for the history alarm class:
Class?HistoryAlarm
{
Attribute：
Int length:ro history alarm bar number
The maximum alarm bar number of Int MaxLength:rw
The tabulation of Listitems:ro history alarm
Action：
Clear (endtime) removes all history alarms
(starttime endtime) gets history alarm between starttime and the endtime to Get, returns the history alarm table result of a List type
}
History alarm list of entries field has:
The time that the begintime:datetime alarm takes place
Endtime:datetime alarms the concluding time
The object that the object:DNtype alarm takes place
Alarmtype:int alarm type numbering;
The state:int alarm status.
3. managed the concrete structure of resource based on network element, set up other subobjects under the NE object, set up lower one-level subobject again under subobject, the rest may be inferred.Parent object and subobject are memberships rather than comprise.
4. be object definition attribute, method and incident, at this version, operation at object has Create and Delete, the base attribute operation has the read-write of Get and the corresponding attribute of Set, attribute is divided into read only attribute and read-write properties, general read only attribute description object state, the configuration of read-write properties description object, if an object has performance data, then it must have CurPM and AccuPM attribute 1, and CurPM is an attribute 1, represents the current performance data of this object, AccuPM also is an attribute 1, and it represents the accumulation performance data of this object.Basic skills is an inquiry child node (GetSubNodes) 8, implication is to return the information of lower floor's subobject, is used for the support target traversal of tree, and elementary event mainly contains attribute change, Object Creation, object deletion 22, management end carries out the synchronous automatically of data according to these incidents and network element, sees Fig. 1.Class definition needs this descriptive language is mapped as the grammer of corresponding software programming language with the format description of figure below in software programming, this step can be by automatic tools software or manual finishing.Class definition form: Class xxx
{
Attribute: attribute definition
Action: method definition
Notification: event definition
}
Description: describe such corresponding management resource in detail, attribute, action, incident etc.
5. the realization of OML agreement.OML protocol transmission layer can adopt TCP (Transmission ControlProtocol, transmission control protocol) or UDP (User Datagram Protocol, User Datagram Protoco (UDP)) agreement, comprises packing, unpacks, part such as encryption and decryption, transmission.The OML protocol transmission requires and can discern legal protocol data automatically in big packet, filters out invalid information, decomposes big packet and reconfigures the recipient.
6. management system and agency's implementation method, the agency is the one deck in the middle of management object 10 and the management system 20, generally realize as a subsystem in the network element, be responsible for and the communicating by letter and ask forwarding of management system to management object, between management system and the agency to communicate by letter be client/server mode, the agency is server, and management system is the client, as Fig. 3.Management system 20 sends inquiry, action 23 to management object 10, modification, establishment, deletion 21 requests, and accept respective acknowledgement, can obtain or revise the relevant attribute in the appointed object or carry out the method that object provides.After the attribute of object is modified, can produce events corresponding, comprise attribute change incident, Object Creation incident, object deletion event 22, send to each management system 20, management system is handled this incident, upgrades corresponding data.
7. the basic process of performance management is referring to Fig. 4.The object that has attribute of performance in the network element writes down self current performance value 24 automatically, write down after 15 minutes, value of the comprehensive one-tenth of these records is counted in the historical performance 27, and management system 20 need go to read historical performance 27 tabulations every 15 minutes automatically and deposit system database 28 in.To current performance data, management system can be inquired about and in interface display according to user's request, and is promptly discardable after the user finishes watching.Whether object needs to gather historical performance by HistoryPMAdmin 35 controls, and whether management end can decide the History Performance Data of each object to be collected by configuration HistoryPMAdmin 35 objects.29 pairs of current performance of alarm threshold value processing module monitor that surveillance style is generally alarm threshold value is sent to corresponding module, and module monitors voluntarily thus, have the out-of-limit incident of performance to produce alarm automatically, to the management narration of face fault management as follows of alarm.
8. the basic process of fault management is referring to Fig. 2.The record of alarm is responsible for by common object CurAlarm 14 and HistoryAlarm 18, these two objects are safeguarded the current alarm tabulation and the history alarm tabulation of whole network element respectively, its main flow process: after certain object produces an alarm or alarm status change, this object judges that by alarm shield object AlarmMask 12 this alarms whether conductively-closed earlier, if shielding is then ignored, otherwise, this warning information is passed to CurAlarm 14, CurAlarm 14 adds this information in the current alarm tabulation, current alarm when its when alarm status is changed into normal condition, also can pass to CurAlarm14, CurAlarm 14 is from removing when the alarm table, and passing to HistoryAlarm 18, HistoryAlarm 18 adds this warning information in the history alarm table.And, when alarm produces or disappear, the object at alarm place needs to send alarm change notification message 15 to each management system 20, show that alarm changes, the alarm change notification message does not comprise detailed warning information, it just indicates the variation of the current alarm state generation of certain object, and this moment, management end can refresh warning information 16 again; Management end need regularly reach history alarm information 19 simultaneously, to add the history alarm database of management end.The shielding of alarm: management end can decide by the configuration alarm shield forbids which managed object produces alarm.
9. to each bookkeeping, comprise configuration management, performance management, alarm management, log management, incident sends, and protocol section has all stipulated to reply accordingly (Response) primitive, guarantees that the integrality of each step operation all is as can be known.Reply and also be encapsulated in based in the defined protocol Data Unit of OML standard (PDU), PDU transmits first-selected connection-oriented Transmission Control Protocol.
10. management agreement explanation:
This agreement is called Object Management group language (OML, Object Management Language), describes in detail below.
Be " name=value " such name value to expression to the data form in the OML system, separate with ", " between the field.Wherein name is a data name, and value is the value of data.The length restriction of Name is within 31 bytes.Name is by beginning of letter, can comprise numeral, English alphabet and " _ " etc., other is illegal.Value goes up any type that joint is mentioned.Distinguishingly, can omit name, only keep value, it is right that this form can be regarded the name value that does not have name as, as a=" xy " can be write as " xy ".Also can default value, as " name=", the named data of the no value of expression.
The functional requirement of map network management, OML have defined a series of keyword and order primitive is described.
Keyword mainly contains:
■ DN:DNType type, object identity.To forming, every pair is separated by ". ", as 1:2.2:6 by a series of classid and instid.When example can only have one, can omit instid.
■ cmd: identifier, order, optional value is: create, delete, get, cancelget, set, action, eventreport, response.
■ Peercmd: identifier, in the DDU of response expression it be answer to that order;
■ Result: type is indefinite, the return value of expression request;
■ Cmdstat: integer, coomand mode, i.e. the state of command execution, 0 represents successfully, the negative number representation failure, the numeric representation failure code, the general failure code of expression wherein-1, failure information can provide in the info field.Cmdstat is different from result, and it only shows the command execution state, as overtime, grammer is wrong, object does not exist, authority is illegal or the like.And result is the result that related command is carried out, as moving return value etc.
■ instid: shaping, object instance number;
■ classid: shaping, class numbering
■ method: character string, the method name of Action primitive.
■ EventType: character string, the event type name of eventreport primitive.
■ scope: integer, specified command sphere of action, numeral recursive hierarchical.1 expression order only acts on this node, and 0 expression order acts on this subtree.This parameter is optional.
The Param:(parameter list), promptly the name value that is bracketed by " (" and ") " is indicated the attribute and the list of attribute values of the object that relevant primitive is used to tabulation.Name value to tabulation be some shapes as " name=value " and set, middle with ", " separate, complicated situation is that value itself is again the attribute list that is bracketed by " (" and ") ", and can multilayer nest, constitutes a tree structure.As Param=(name1=(and sub1=subval1, sub2=subval2 ... .) ...).
The OML agreement is used data type self-defining and platform independence to the expression of data, and fundamental type has:
INT: integer, as 245 ,-22 etc.
Float: floating number, as 1.2,3.34 etc.
String: character string, as " abc "
Bytes: binary string, as [base64:8912fe] expression base64 coding, one 16 system number of [1a6f1122] every letter representation of expression, byte of per two letter representations.
Applied is the extension usage of basic model, as:
Bool: Boolean type, represent vacation with 0,1 expression is true.
DNType: object identifier, as " 1.3.5.6.3 ", use string representation.
String representation as " 10.12.145.142 ", is used in the Ipv4Addr:Ipv4 address.
DateTime: the time on date,, use string representation as " 2002-12-312:15:03 ".
Combined is the synthetic type of other type group, has:
List: tabulation, the set of the data of any type, form as (a=1, b=" xy ", c=(m=2)) value list that promptly comprises with round bracket, tabulation can comprise tabulation, the value in the tabulation can be dissimilar, can have the name also can be nameless; Once can transmit a large amount of baroque data by this data type.
Array: simple array, the set that simple types such as integer or floating type are formed, form is as { 1,3,8,9}, array value are tentative at present can only to be single integer type or floating point type.
Data type all is tagging, promptly directly can infer its fundamental type from the expression mode of data, must be integer as 123; Floating type must have decimal point, as 1.00.The Bytes types value is included in a pair of [] the inside, by coded system as " base64 " add ": " beginning, the data behind the heel coding.The value type can make a distinction with the identifier strictness, and identifier is used for representing the name or the value of " name=value " centering in the PDU definition, and the value type can only be used as the value part.
Describe the PDU structure of this NMP below in detail.PDU is made up of PDU head and PDU body, and is as follows:
OML?PDU＝PDU?Header?CRLF?CRLF
PDU?body?CRLF
CRLF
Cut apart by two CRLF between PDU head and the PDU body, whole PDU is finished by two CRLF
The PDU body is divided into request and replys two types:
PDU?BODY＝OML?Request
| OML?Response
Wherein, the form of PDU head is as follows: (annotate: following symbol SP represents the space, and CRLF represents the new line sequence.)
OML PDU data head adds version number by " OML/ " to begin, as " OML/1.0 ".Other characterising parameters of heel, between each characterising parameter with space or " n " separately.Parameter format is: parameter name=parameter value.Basic parameter has:
● ContentLength: data volume length, integer.
● Sequence:PDU sequence number, integer.
● Encoding: coded system, character string.As " Base64 ".
● Charset: character set, character string.As " gb2312 ".
ContentLength, Sequence are for must fill out parameter, and all the other are optional.
The example of PDU head:
OML/1.0?SP?Sequence＝1235?SP?ContentLength＝250?SP?Charset＝”gb2312”CRLF
PDU BODY is divided into OML Request and OML Response.
OML Request has following structure:
OML?Request：：＝DN＝xxx，cmd＝xxx，[param＝(xxx)，][scope＝xxx，]
[method＝xxx，][eventtype＝xxx]
Wherein:
The object that DN=xxx indicates to operate if the scope option is arranged, then indicates the root node of the subtree that will operate;
Cmd=xxx represents action type, as get, set, action etc.;
Param=(xxx) indicates the operation desired parameters, and is different according to different orders;
Scope=xxx represents opereating specification, is to this Object Operations or to being the subtree operation of root with this object, does not temporarily require realization;
Method=xxx represents if cmd is Action, the Method type that specifically calls;
Eventtype=xxx represents if cmd is eventreport, the event type that reports;
OML reponse has following structure:
OML?Response：：＝DN＝xxx，cmd＝Response，peercmd＝xxx，cmdstat＝xxx，
[Param＝(xxx)，][result＝xxx，][info＝xxx]
DN: the same
Cmd=Response is expressed as and replys
Peercmd=xxx is expressed as replying of which kind of order
Cmdstat=xxx represents the command execution state;
The parameter that Param=(xxx) expression is returned;
The Result=xxx ecbatic, data type is indefinite, and is different and different according to request
Info=xxx represents additional information
The primitive that network management protocol uses is described as follows:
● M-Create.Request: creative management object requests;
The PDU structure:
DN＝xxx，cmd＝Create，classid＝xxx，instid＝xxx，param＝(xxx)
Illustrate: DN indicates and will create the father node of object.The parameter establishment classid that indicates with param indicates
The class sign;
● M-Create.Response: create the object response;
The PDU structure:
DN＝xxx，Cmd＝response，peercmd＝create，cmdstat＝xxx，result＝xxx
Illustrate:
DN indicates the father node that is created object, if successful result returns the DN that is created object;
● M-Delete.Request: deletion management object request;
The PDU structure:
DN＝xxx，Cmd＝delete
Illustrate:
The object that deletion DN indicates, this object comprises that its child node is all deleted;
● M-Delete.Response: deletion management object response;
The PDU structure:
DN＝xxx，Cmd＝response，peercmd＝delete，cmdstat＝xxx
Illustrate:
● M-Get.Request: get the request of object properties value;
The PDU structure:
DN＝xxx，Cmd＝get，param＝(xxx)
Illustrate:
Obtain the property value of the object that DN indicates, attribute-name indicates in param, form be (param_name1=, param_name2=...);
● M-Get.Response: get the response of object properties value;
The PDU structure:
Cmd＝response，peercmd＝get，cmdstat＝xxx，param＝(xxx)
Illustrate:
Return the property value of the object that the DN that obtains indicates, value list indicates in param;
● M-Cancel: cancellation request
The PDU structure:
DN＝0，Cmd＝cancel，peerCequence＝xxx
Illustrate:
The request of cancellation peerCequence appointment, DN fills out 0;
● the M-Cancel.Response:Cancel response
The PDU structure:
DN＝0，Cmd＝response，peercmd＝cancel，cmdstat＝xxx
Illustrate:
● M-Set.Request: the request of object properties value is set;
The PDU structure:
DN＝xxx，Cmd＝set，param＝(xxx)
Illustrate:
The property value of the object that DN indicates is set;
● M-Set.Response: the response of object properties value is set;
The PDU structure:
DN＝xxx，Cmd＝response，peercmd＝set，cmdstat＝xxx
Illustrate:
M-Action.Request: allocating object method request;
The PDU structure:
DN＝xxx，Cmd＝action，method＝xxx，param＝(xxx)
Illustrate:
Call the method that the method for the object that DN indicates indicates, the parameter of method is specified by param;
● M-Action.Response: allocating object method response;
The PDU structure:
DN＝xxx，Cmd＝response，peercmd＝action，method＝xxx，cmdstate＝xxx，[result＝xxx]
Illustrate:
Return the result who calls the object method that DN indicates,, in result, indicate if the result is arranged;
● M-EventReport.Request: management object event report request;
The PDU structure:
DN＝xxx，Cmd＝eventreport，EventType＝”xxx”，param＝(xxx)
Illustrate:
Object reports the event of DN object, and event argument has param to indicate;
● M-EventReport.Response: management object event report response;
The PDU structure:
DN＝xxx，Cmd＝response，peercmd＝eventreport，cmdstat＝xxx
Illustrate:
Incident is received in expression;
Annotate: response primitive can add an info field, and side information is provided, and particularly returns when makeing mistakes, can the detailed error message of annex.
Claims (1)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100181652A CN100364275C (en) | 2005-01-18 | 2005-01-18 | A communication network management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100181652A CN100364275C (en) | 2005-01-18 | 2005-01-18 | A communication network management method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1645819A true CN1645819A (en) | 2005-07-27 |
| CN100364275C CN100364275C (en) | 2008-01-23 |
Family
ID=34875671
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100181652A Expired - Fee Related CN100364275C (en) | 2005-01-18 | 2005-01-18 | A communication network management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100364275C (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100370762C (en) * | 2006-03-08 | 2008-02-20 | 华为技术有限公司 | Method, device and system for processing alarm messages |
| WO2009062410A1 (en) * | 2007-11-15 | 2009-05-22 | Huawei Technologies Co., Ltd. | Method and device for instantiating management object of management tree in terminal device |
| WO2010145445A1 (en) * | 2009-06-19 | 2010-12-23 | 中兴通讯股份有限公司 | Device and method for enabling hierarchical quality of service services |
| CN101030271B (en) * | 2006-03-03 | 2011-09-28 | 中国电信股份有限公司 | Persistent inquiry method for resource service object |
| CN101217315B (en) * | 2008-01-04 | 2012-05-23 | 中兴通讯股份有限公司 | A configuration method and system for alarm shielding |
| CN102739440A (en) * | 2012-05-24 | 2012-10-17 | 大唐移动通信设备有限公司 | Method and device for accessing hardware device |
| CN104158695A (en) * | 2014-09-05 | 2014-11-19 | 上海斐讯数据通信技术有限公司 | Network management method for network management system |
| CN106789247A (en) * | 2016-12-22 | 2017-05-31 | 瑞斯康达科技发展股份有限公司 | A kind of warning information mapping method and device |
| CN113824587A (en) * | 2021-09-13 | 2021-12-21 | 中信科移动通信技术股份有限公司 | Multi-communication protocol equipment management method and system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5704041A (en) * | 1994-09-21 | 1997-12-30 | International Business Machines Corporation | Object independent scoping in an open system interconnection system |
| EP0991226A1 (en) * | 1998-09-30 | 2000-04-05 | Siemens Aktiengesellschaft | Method for accessing data in network elements |
| US6546415B1 (en) * | 1999-05-14 | 2003-04-08 | Lucent Technologies Inc. | Network management system using a distributed namespace |
-
2005
- 2005-01-18 CN CNB2005100181652A patent/CN100364275C/en not_active Expired - Fee Related
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101030271B (en) * | 2006-03-03 | 2011-09-28 | 中国电信股份有限公司 | Persistent inquiry method for resource service object |
| CN100370762C (en) * | 2006-03-08 | 2008-02-20 | 华为技术有限公司 | Method, device and system for processing alarm messages |
| US8543679B2 (en) | 2007-11-15 | 2013-09-24 | Huawei Technologies Co., Ltd. | Method and device for creating management object instance in management tree of terminal device |
| WO2009062410A1 (en) * | 2007-11-15 | 2009-05-22 | Huawei Technologies Co., Ltd. | Method and device for instantiating management object of management tree in terminal device |
| CN101437071B (en) * | 2007-11-15 | 2011-09-28 | 华为技术有限公司 | Method and equipment for management object instantiation of terminal equipment management tree |
| US8321552B2 (en) | 2007-11-15 | 2012-11-27 | Huawei Technologies Co., Ltd. | Method and device for creating management object instance in management tree of terminal device |
| CN101217315B (en) * | 2008-01-04 | 2012-05-23 | 中兴通讯股份有限公司 | A configuration method and system for alarm shielding |
| WO2010145445A1 (en) * | 2009-06-19 | 2010-12-23 | 中兴通讯股份有限公司 | Device and method for enabling hierarchical quality of service services |
| CN102739440A (en) * | 2012-05-24 | 2012-10-17 | 大唐移动通信设备有限公司 | Method and device for accessing hardware device |
| CN104158695A (en) * | 2014-09-05 | 2014-11-19 | 上海斐讯数据通信技术有限公司 | Network management method for network management system |
| CN106789247A (en) * | 2016-12-22 | 2017-05-31 | 瑞斯康达科技发展股份有限公司 | A kind of warning information mapping method and device |
| CN113824587A (en) * | 2021-09-13 | 2021-12-21 | 中信科移动通信技术股份有限公司 | Multi-communication protocol equipment management method and system |
| CN113824587B (en) * | 2021-09-13 | 2023-08-29 | 中信科移动通信技术股份有限公司 | Multi-communication protocol equipment management method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100364275C (en) | 2008-01-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1142489C (en) | Information processing method and server | |
| CN1115884C (en) | Programmable call processing system and method | |
| CN1302401A (en) | Visual data integration system and method | |
| CN1280716C (en) | Computer processing method, distributed computing method and network computing method | |
| CN1299467C (en) | Equipment and method for managing network apparatus | |
| CN101061688A (en) | Network management apparatus and method based on simple network management protocol | |
| CN1968133A (en) | Equipment configuration information management method and its system | |
| CN1601483A (en) | An Automated Software Testing System Based on Script Interpretation Tool | |
| CN1992728A (en) | Systems and methods for facilitating group collaborations | |
| CN1947106A (en) | Notification method, connection apparatus, communication method, and program | |
| CN1625865A (en) | Method and equipment for management of tree data exchange | |
| CN1405694A (en) | Post service device frame facing to object | |
| CN1074319A (en) | The software configuration of telecommunication switching system | |
| CN1820514A (en) | System architecture, method and computer program product for managing a telecommunications network | |
| CN1429362A (en) | Communication service provisioning method and apparatus and object programming language for developing provisioning modules | |
| CN1173933A (en) | Method and appts. for building a telecommunications network database | |
| CN1645819A (en) | Rapid and convenient communication network managing method | |
| CN1229728C (en) | WEB application system with session management and distributed management functions and corresponding operation management mechanism | |
| CN1218223A (en) | Method for executing moving object and recording medium storing moving object | |
| CN1601543A (en) | Working stream management appts. and method | |
| CN1627757A (en) | Method for realizing general message interpreter | |
| CN1770708A (en) | Information processing system and method, electronic appliance, and information processing method | |
| CN1713140A (en) | Interface generating method and device for computer | |
| CN1794647A (en) | Method and its system upload terminal information in equipment management | |
| CN1866250A (en) | Method and system for managing system data |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080123 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |