CN101471813B - Configuration method, system and equipment for implementing domain-striding maintenance management - Google Patents
Configuration method, system and equipment for implementing domain-striding maintenance management Download PDFInfo
- Publication number
- CN101471813B CN101471813B CN2007103075387A CN200710307538A CN101471813B CN 101471813 B CN101471813 B CN 101471813B CN 2007103075387 A CN2007103075387 A CN 2007103075387A CN 200710307538 A CN200710307538 A CN 200710307538A CN 101471813 B CN101471813 B CN 101471813B
- Authority
- CN
- China
- Prior art keywords
- maintenance
- oam
- domain
- information
- configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 180
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000000875 corresponding effect Effects 0.000 claims description 19
- 230000002596 correlated effect Effects 0.000 claims description 2
- 230000005540 biological transmission Effects 0.000 description 12
- 101150111724 MEP1 gene Proteins 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 230000011664 signaling Effects 0.000 description 5
- 101150056991 MEP2 gene Proteins 0.000 description 3
- 230000006399 behavior Effects 0.000 description 3
- 239000012467 final product Substances 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 238000004064 recycling Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention discloses a configuring method for realizing cross-domain maintenance management, which is applied to an end-to-end network, at least comprises two maintenance management domains, and concretely comprises the steps as follows: a maintenance point to be configured receives a message carrying with OAM attribute configuration indicating information, wherein, the message includes terminal node information of a plurality of maintenance management domains; and the maintenance point to be configured configures the OAM attribute of the maintenance point according to the terminal node information. The embodiment of the invention further discloses a cross-domain maintenance management system and a device. By adopting the technical, the relevant information configuration among administrative domains can be realized automatically; and a network manager does not need to send network management commands to each maintenance point to be configured and configure the OAM attribute of each maintenance point respectively, and only needs to transmits the message carrying with the OAM attribute information among the maintenance points to be configured so as to automatically figurate the OAM attribute to multizone maintenance points, so that the configuration efficiency is increased, and the task quantity of the network manager for configuring the OAM attribute is relieved.
Description
Technical field
The present invention relates to data communication technology field, especially a kind of collocation method, system and equipment of realizing domain-striding maintenance management.
Background technology
Traditional transmission net is an example with synchronous digital transmission system (SDH), and an important characteristic is exactly the maintenance management function (OAM, Operation Administration and Maintenance) that controllable high-efficiency can be provided.Wherein, tandem connection monitor (TCM, Tandem Connection Monitoring), be with one end to end the path be divided into the continuous serial connection path of multistage, each the section all manage voluntarily by operator.Like this, can be distributed on each serial connection path along the malfunction monitoring on road and to realize, thus fault location more fast, and between operator the clear failure responsibility.
Packet Transport Network, (Tansport MPLS is the technology of representative with Ethernet T-MPLS), has also inherited this technology, and one professional end to end can come maintenance management through different management domains to transmit MPLS.Fig. 1 has provided the domain maintenance management sketch map of T-MPLS layer network.As shown in Figure 1, grouping transport layer network possibly comprise a plurality of management domains, and such as client territory (Customer level), service provider territory (Provider level) and the network operation quotient field (Operator Level), these three management domains are nested relations.Like Fig. 1, the network operation quotient field can be divided into A, B and three territories of C again, their (flat) non-nested relations that is parallel.Also can there be MEG in all corresponding Maintenance Entity (MEG, ME Group) of each management domain between adjacent management domain.MEG can be corresponding the point-to-point clean culture connect, also can corresponding points multicast connection to multiple spot or multiple spot to multiple spot.When these MEG were nested, the OAM message that each MEG is used for territory, maintenance management oneself place was wanted to discern and is made a distinction with the OAM message of other MEG.Can't encapsulate when distinguishing these OAM messages through skin, the MEG rank (MEL:MEG Level, Chinese full name are the domain maintenance management ranks) that we can utilize the OAM message to carry is distinguished.
In order to say something conveniently, the figure of simplification is as shown in Figure 2.The destination node MEP of MEG (MEGEnd Point, the destination node of domain maintenance management) representes with triangle that in Fig. 2 the intermediate point MIP of MEG (MEG Intermediate Point, the intermediate node of domain maintenance management) representes with circle in Fig. 2.
Ethernet and T-MPLS are different to the processing of MEL, and Ethernet OAM is supported 8 MEL.When judging that belonging to not same area (like customer, when provider, operator) OAM message, can distinguish the OAM message that belongs to different management domains through 8 MEL through Ethernet encapsulation.The MEL distribution principle of acquiescence (not necessarily will use entirely, and the numerical value of these acquiescences can be at customer, is changed through consulting between provider and the operator) as follows:
Customer uses 3 MEL:7,6 and 5;
Provider uses 2 MEL:4 and 3;
Operator uses 3 MEL:2,1 and 0.
Ethernet MEL is fixing static configuration; The MEL in each territory will be configured to fixed numeric values in advance; Each territory is handled different to the message of different MEL values: the identical OAM message of MEL with self configuration is only handled in each territory, carries out transparent transmission for being superior to the OAM message that self disposes MEL; Being lower than the identical but OAM message that do not belong to same administrative domain of OAM message and the rank of self configuration MEL for rank blocks.
T-MPLS OAM also supports 8 MEL.(like customer, provider and operator) is nested when different management domains, and can't distinguish the OAM message of these management domains through outer encapsulation the time, can distinguish through MEL.Some of T-MPLS MEL are regular as follows:
Each MEL only just handles when equaling 0;
Each MEP only produces and handles the OAM message of MEL=0;
Each MIP only handles and responds the OAM message of MEL=0;
Each MEP produces AIS and the LCK of MEL=0, is used for the alarm of client layer.
T-MPLS adopts MEL flexibly to distinguish the OAM message of nested MEG; Need be to the MEL value of each management domain configuring fixed; But MEP is set unified behavior, promptly MEP increases MEL to the OAM message of all entering on the direction of source, on Su Fangxiang, reduces MEL.(annotate: source MEP will abandon all OAM messages that get into the MEL=7 in this territory, in case overflow in the MEL territory.) this method position that only need dispose different management domain MEP gets final product.
In order to realize cross-domain OAM(Operation Administration Maintenance), need a large amount of cross-domain OAM attribute informations of configuration, like maintenance field sign, maintenance field destination node, maintenance field intermediate point and maintenance field rank etc.At present, these attributes are mainly through the webmaster manual configuration.When the linking number that relates to and maintenance point number to be disposed more for a long time, the configuration task amount of webmaster is very big so, need be respectively the OAM attribute that each treats configuring maintenance point configuration correspondence.
The prior art research relevant with the present invention provides the method that how to dispose the OAM attribute automatically, still, all only relates to the OAM attribute configuration in the single domain.And the OAM configuration of striding a plurality of nested management domains does not still have research.
In the prior art one relevant with the present invention, the RSVP signaling is carried the parameter relevant with the Ethernet OAM attribute, like MEG ID, and MEL, MEP ID and corresponding address information pass to destination node from source node.The node of signaling process is according to entrained information configuration OAM property parameters.
The scheme of the prior art one relevant with the present invention has only been described the method for configuration ethernet OAM parameter in a territory, does not consider the situation of cross-domain OAM configuration.And acquiescence is MIP with the port arrangement of middle all processes, and this method underaction has limitation.In fact, under the situation that has the nested supervision of multiple domain, in a territory, need all not be arranged to MIP to each port of middle process, keep watch on and can accomplish through other nested territories.
The design of the prior art two relevant with the present invention is: utilize GARP (Generic Attribute Registration Protocol) or Ethernet CC frame (Continuity Check) to come the MEP and the MIP of different stage in the configuration ethernet; Wherein the configuration of MIP is to form automatically, has reduced the contingent mistake of manual configuration.The two is basic identical on processing procedure, and just the former needs state machine, and the latter does not need state machine, but periodically sends the CC frame.
The step of MEP and MIP configuration is following:
(1) disposes first MEP (supposition level is X);
(2) transmit OAM level information in first direction, can be by GARP or CC message;
(3) configuration second MEP point (1evel is X);
(4) transmit OAM level information in second direction, can be by GARP or CC message;
(5) between said first and second MEP, frame the bridge port of process, disposed MIP or A-MEP (MEP automatically) automatically, level is X.
The method of in this scheme, distinguishing MIP and A-MEP is following:
When the port of bridge receives the GARP/CC frame through physical link, mean registration (R) level value; When other ports of bridge obtain the level value in bridge, be called declare (D).For the MEP point at two ends, two-way transmission GARP/CC frame, confirm the level value of both direction.If port obtains the mode of level value on both direction be DR/RD, so such port is MIP; If port obtains the mode of level value on both direction be DD, this port is A-MEP (MEP automatically) so.
The CC frame is a kind of of Ethernet OAM frame in the design of the prior art two relevant with the present invention, is used to detect connectedness and the connectivity that Ethernet connects.Utilize the CC message to be configured to have and conflict with the mechanism of the CC frame of Ethernet detection failure own.Like fault: whether the unexpected ME Level fault type ME Level information that to be the ME Level that carries through CC frame relatively dispose with MEP itself is consistent judges that in addition, the MIP point also can filter through comparison ME Level.
In addition, this prior art has also only introduced how to dispose MEL in the single domain, does not relate to cross-domain situation.Also to be acquiescence become MIP or A-MEP with the port arrangement of processes in the middle of all to this prior art, and to require be two-way connection (being applicable to Ethernet), underaction.
In realizing process of the present invention, the inventor finds to exist at least in the prior art following problem:
Prior art has only been introduced the collocation method of maintenance management in the territory, and acquiescence is MIP or A-MEP with the port arrangement of middle all processes, underaction.
Summary of the invention
Embodiments of the invention provide a kind of collocation method of realizing domain-striding maintenance management, to be implemented in the collocation method that can cross over a plurality of domain maintenance management in the packet network.
For achieving the above object, embodiments of the invention provide a kind of collocation method of realizing domain-striding maintenance management, and this method is applied to a network end to end, comprise two domain maintenance management at least, the concrete following steps of this method:
Treat that configuring maintenance point receives the message of carrying operation management OAM attribute configuration indication information; Said message comprises the destination node information of a plurality of domain maintenance management; Said destination node information comprises the destination node position of domain maintenance management at least; The said configuring maintenance point of treating is allocated Maintenance Point Identification in advance; Carry the said positional information of treating configuring maintenance point in the said destination node information when treating that the configuring maintenance point detects, the said configuration node of treating is configured to destination node, identify pre-assigned Maintenance Point Identification as destination node simultaneously;
The said configuring maintenance point of treating detects the OAM information list that carries in the said message; Preserve the information relevant with self; Specifically comprise: the said configuring maintenance point of treating parses the OAM attribute information of corresponding this maintenance point according to the positional information of this maintenance point, and the said configuring maintenance point of treating is preserved the OAM attribute information of being correlated with;
The said OAM attribute of treating the configuring maintenance point according to said this maintenance point of destination node information configuration is specially: said treat that the configuring maintenance point receives the affirmation message of the OAM attribute configuration of returning after, according to the OAM attribute information of preserving, accomplish the OAM attribute configuration.
Compared with prior art, embodiments of the invention have the following advantages:
Automatically realize striding the relevant information configuration of management domain; The OAM attribute of each node need not ordered, dispose respectively to webmaster to each node transmission webmaster; And only need be in the message of treating between the configuration node to carry the OAM attribute information through transmission; Can realize the automatic OAM attribute configuration of a plurality of nodes, therefore improve allocative efficiency, alleviate the task amount of network management configuration OAM attribute.
Description of drawings
Fig. 1 is the sketch map of T-MPLS layer network domain maintenance management in the background technology;
Fig. 2 is the sketch map of the domain maintenance management of grouping transport layer network in the background technology;
Fig. 3 is a kind of collocation method flow chart of realizing domain-striding maintenance management in the embodiment of the invention;
Fig. 4 is the sketch map of the Ethernet multiple domain in the embodiment of the invention one;
Fig. 5 is PATH and the RESV message in the embodiment of the invention one;
Fig. 6 is the T-MPLS multiple domain sketch map in the embodiment of the invention two;
Fig. 7 is the domain-striding maintenance management system schematic in the embodiment of the invention;
Fig. 8 is the source maintenance point equipment sketch map in the embodiment of the invention;
Fig. 9 is the place maintenance point equipment sketch map in the embodiment of the invention;
Figure 10 is the middle maintenance point equipment sketch map in the embodiment of the invention.
Embodiment
Below in conjunction with accompanying drawing and embodiment, specific embodiments of the invention describes in further detail:
The embodiment of the invention provides a kind of collocation method of realizing domain-striding maintenance management, and is as shown in Figure 3, may further comprise the steps:
Step s100 treats that configuring maintenance point receives the message of carrying operation management OAM attribute configuration indication information; Said message comprises the destination node information of a plurality of domain maintenance management.Said destination node information comprises at least: the destination node sign and the position thereof of domain maintenance management; Or said destination node information comprises the destination node position of domain maintenance management at least; The said configuring maintenance point of treating is allocated Maintenance Point Identification in advance; Carry the said positional information of treating configuring maintenance point in the said destination node information when treating that the configuring maintenance point detects; The said configuration node of treating is configured to destination node, identifies pre-assigned Maintenance Point Identification as said destination node simultaneously.
Step s200, the said OAM attribute of treating the configuring maintenance point according to said this maintenance point of destination node information configuration.Specifically comprise: the said configuring maintenance point of treating receives after the message of carrying OAM attribute configuration indication information the directly OAM attribute of this maintenance point of configuration; Or the said OAM attribute of treating to preserve when the configuring maintenance point receives the message of carrying OAM attribute configuration indication information this maintenance point, the OAM attribute of this maintenance point of configuration after receiving the OAM attribute configuration acknowledge message of returning.
In the embodiments of the invention one; A kind of collocation method of automatic realization domain-striding maintenance management; With the Ethernet is example, and as shown in Figure 4 is the sketch map of Ethernet multi-management area, comprises two nested domains of provider and operator; Wherein, the operator territory is divided into two parallel territories of Operator A and Operator B again.Wherein:
(1) the corresponding MEG in Provider territory is MEG_P, and MEL is made as 4.The MEP point at two ends is separately positioned on the port one of Node B and the port 2 of node G, and middle MIP point is arranged on the port 2 of node D and the port one of node E.
Owing to have operator A and B territory, can realize TCM.So other intermediate node/port of provider territory process (being included in operator A and the B territory, like the port 2 of Node B, the port one of node C and 2, the port one of node D etc.) need not be provided with MIP.
(2) the corresponding MEG in Operator A territory is MEG_A, and MEL is made as 2.The MEP point at two ends is separately positioned on the port one of Node B and the port 2 of node D, and middle MIP point is arranged on the port 2 of Node B and the port one of node D.
(3) the corresponding MEG in Operator B territory is MEG_B, and MEL is made as 1.The MEP point at two ends is separately positioned on the port one of node E and the port 2 of node G, and middle MIP point is arranged on the port 2 of node E and the port one of node G.
Present embodiment is accomplished whole TCM configurations through sending a Path message, may further comprise the steps:
The source node of step s101, ESP (Ethernet Switching Path) sends Path message.Path message can be sent along explicit route (specified path).Path message is carried the OAM information list in each MEG territory; Its content includes but not limited to: MEG ID, MEL, MEP corresponding nodes/port address; MEP ID; MIP corresponding nodes/port address, some other OAM attribute (, perhaps whether enabling the indication information of OAM(Operation Administration Maintenance) etc.) like parameters relevant such as cycles with concrete OAM(Operation Administration Maintenance).
It should be noted that: MEP ID will guarantee unique in a MEG territory, can not repeat, and can directly be with in the OAM information list, forms one-to-one relationship with MEP place node/port address; Perhaps be sign of each port assignment (assurance does not repeat) in advance, and then set up the binding relationship of the node/port at MEP ID and its place through signaling through webmaster etc.
Step s102, each receives the node/port of Path message, detects the OAM information list that carries in the Path message, preserves the information relevant with self, up to destination node.
It should be noted that: whether the determination methods of " whether relevant " i.e. address/sign of this receiving node/port is the MEP/MIP corresponding nodes/port address that needs configuration in the OAM information list; If; Then this receiving node is preserved all relevant OAM attribute informations; Like MEG ID, MEL, MEP ID etc.If the OAM information list has only comprised the information (removing the part of grey like table 2) of node/port of waiting to dispose OAM information, so, only need judge whether the address/identification information of receiving node is included in the OAM information list.
After the destination node of step s103, ESP receives the Path message of carrying OAM information, send Resv message.Resv message can be carried OAM information.
Step s104, receive the node of Resv message,, accomplish the OAM attribute configuration according to the OAM attribute information of preserving.
Of (1), if the corresponding relation of MEP ID and MEP place node/port address is not carried in the OAM information list, the node at MEP ID and its place/port binding relation can be accomplished in this step so.
Illustrate according to Fig. 4, only consider to set up the situation in provider and operator territory.OAM information such as table 1 to be disposed.
The OAM information that table 1 ethernet management territory (Fig. 4) is to be disposed
For convenience of description, the node/port at MEP and MIP place representes that with identifying intuitively actual can be MAC Address, port numbers etc. here.In Ethernet, there is not MIP ID, directly representes with MAC Address.MIP only need dispose MEL.MIP can specify concrete position, also can all remaining node/ports that does not have to dispose be mixed with MIP (the MIP Lieque is economized in the form at this moment).Other info can be other need configuration parameters relevant with concrete OAM(Operation Administration Maintenance).
For the ease of obtaining information, can each node/port as index.From the Path message that node A sends, carry following OAM information list, like table 2.
The OAM information list that table 2 Path message is carried is (embodiment one) for example
The part of grey can not be listed in the table in the table, because there is not the informational needs configuration.MIP only need dispose MEL.When a plurality of maintenance point information of node/port arrangement, from top to bottom ordinal relation embodies the precedence relationship of these points of configuration in the form.
Concrete step is following:
(1) process of Path message transmission may further comprise the steps:
Step s201, Path message according to OAM information list (reference table 2), preserve following information: { MEG ID=MEG_P, MEL=4, MEP ID=MEP 1}, { MEG ID=MEG_A, MEL=2, MEP ID=MEP 1} during through the port one of Node B;
Step s202, Path message according to the OAM information list, preserve following information: { MEL=2, MIP} during through the port 2 of Node B;
When step s203, Path message process node C,,, continue to transmit Path message so this node is not preserved any OAM configuration information owing to do not comprise relevant OAM configuration information in the OAM information list;
Step s204, Path message according to the OAM information list, preserve following information: { MEL=2, MIP} during through the port one of node D;
Step s205, Path message according to the OAM information list, preserve following information: { MEG ID=MEG_A, MEL=2, MEP ID=MEP 2}, { MEL=2, MIP} during through the port 2 of node D;
Step s206, Path message according to the OAM information list, preserve following information: { MEL=4, MEP ID=MEP 2}, { MEG ID=MEG_B, MEL=1, MEP ID=MEP 1} during through the port one of node E;
Step s207, Path message according to the OAM information list, preserve following information: { MEL=1, MIP} during through the port 2 of node E;
When step s208, Path message process node F,,, continue to transmit Path message so this node is not preserved any OAM configuration information owing to do not comprise relevant OAM configuration information in the OAM information list;
Step s209, Path message according to the OAM information list, preserve following information: { MEL=1, MIP} during through the port one of node G;
Step s210, Path message according to the OAM information list, preserve following information: { MEG ID=MEG_B, MEL=1, MEP ID=MEP 2}, { MEG ID=MEG_P, MEL=4, MEP ID=MEP 2} during through the port 2 of node G;
When step s211, Path message process node H, owing to do not comprise relevant OAM configuration information in the OAM information list, so this node is not preserved any OAM configuration information.The H node is the destination node of ESP, and Path message is transmitted no longer downwards.The H node oppositely sends Resv message.
(2) each node is accomplished the OAM attribute configuration after receiving Resv message
In the embodiment of the invention two, a kind of collocation method of automatic realization domain-striding maintenance management is an example with the Ethernet; With reference to Fig. 4,, accomplish a TCM configuration (method of recycling single domain configuration OAM attribute through sending repeatedly Path message at every turn; Be the OAM attribute information that each Path message is only carried a territory, include but not limited to MEG ID, MEL; Address/the sign of MEP ID and MEP place node/port, the configuration in a territory of completion) mode realizes the OAM attribute configuration.Usually directly carry the MIP position and the MEL information in this territory in each Path message; Perhaps dispose MIP automatically, all remaining node configuration are become MIP, need not carry MIP this moment in the OAM information list information, latter's concrete steps are following:
Step s301, set up the TCM of a certain rank (MEL), specify sourcesink MEP, middle node directly is configured to the MIP point with MEL.
Step s302, adopt use the same method set up other the level other TCM; Low MEL principle of priority is satisfied in the foundation of MIP: on same node/port, and the MIP of the MIP of first rank (low) replacement second level (height) (mainly being situation) to " nested domain ", for example; With reference to figure 4; The rank of same maintenance point in the A of operator is first rank, and the rank in the service provider is a second level, and first rank is lower than second level grade; Promptly in territory nested, the territory rank that the leap scope is more little is low more; For ease, can consider to begin to set up from low-level TCM.
As shown in Figure 4; If dispose the Provider territory earlier; Be MEG ID=MEG_P, MEL=4 and MEP ID are respectively MEP1 and MEP2 (unique in MEG_P), and automatically with all remaining node/ports (1/2 port of node C, D, E, F in this territory; 2 ports of Node B, 1 port of node G) is configured to MIP (MEL=4).Dispose the Operator territory again, i.e. MEG ID=MEG_A, MEL=2 and MEP ID are respectively MEP1 and MEP2 (unique in MEG_A), and all remaining node/port arrangement become MIP (MEL=2) in this territory; MEG ID=MEG_B, MEL=1 and MEP ID are respectively MEP1 and MEP2 (unique in MEG_B)
Similarly; Can be placed on the information in parallel non-nested several territories and send (not involving the problem of " low-level MIP replaces high level MIP ") in the path message, concrete form can be with reference to the method for previous embodiment one " sends a Path message accomplish whole TCM dispose "; The information of different nested domains can realize that involve the problem of " low-level MIP replaces high level MIP ", concrete substitute mode is same as described above through sending different path message
In the description of the foregoing description one and embodiment two, also comprise:
1) property parameters of OAM can be handed down to the first node of LSP through webmaster; Perhaps by first node to the application of OAM attribute management module.
2) the above description with the RSVP signaling is example, but is not limited to RSVP, and other also can realize above-mentioned configuration like the Ping mechanism of the Link Trace or the MPLS of Ethernet, and basic step is similar, gives unnecessary details no longer one by one here.
3) foregoing description is to transmit the path and OAM is configured later on again setting up; Also can when setting up forward-path, realize the configuration of OAM attribute
4) the foregoing description is through Path message the OAM attribute information to be issued to each node, accomplishes attribute configuration through the Resv message of returning again; Also can only directly accomplish the configuration of OAM attribute information through Path message.
In the embodiments of the invention three; A kind of collocation method of automatic realization domain-striding maintenance management; With the T-MPLS network is example, and as shown in Figure 5 is the sketch map of T-MPLS multi-management area, comprises two nested domains of provider and operator; Wherein, the operator territory is divided into two parallel territories of Operator A and Operator B again).Wherein:
(1) the corresponding MEG in Provider territory is MEG P, and the MEP point at two ends is separately positioned on the port one of Node B and the port 2 of node G, and middle MIP point is arranged on the port 2 of node D and the port one of contact E.
It should be noted that:, can realize TCM owing to have operator A and B territory.So other intermediate node/port of provider territory process (being included in operator A and the B territory, like the port 2 of Node B, the port one of node C and 2, the port one of node D etc.) need not be provided with MIP.
(2) the corresponding MEG in Operator A territory is MEG_A, and the MEP point at two ends is separately positioned on the port one of Node B and the port 2 of node D, and middle MIP point is arranged on the port 2 of Node B and the port one of contact D.
(3) the corresponding MEG in OperatorB territory is MEG_B, and the MEP point at two ends is separately positioned on the port one of node E and the port 2 of node G, and middle MIP point is arranged on the port 2 of node E and the port one of contact G.
In fact, the MEL of T-MPLS does not need configuration, and the destination node MEP that only need indicate MEG gets final product, and each MEP is identical to the behavior of MEL operation, and each MEL only just handles when equaling 0; Each MEP only produces and handles the OAM message of MEL=0; Each MIP only handles and responds the OAM message of MEL=0; Each MEP produces AIS and the LCK of MEL=0, is used for the alarm of client layer.And T-MPLS adopts MEL flexibly to distinguish the OAM message of nested MEG; Need be to the MEL value of each management domain configuring fixed; But MEP is set unified behavior, promptly MEP increases MEL to the OAM message of all entering on the direction of source, on Su Fangxiang, reduces MEL.So the MEL configuration of T-MPLS is simpler than Ethernet.The content of above-mentioned Ethernet embodiment abridged get final product.
Utilize T-MPLS to realize that automatically the collocation method step of domain-striding maintenance management is following:
The source node of step s401, LSP (Label Switching Path) sends Path message.Path message can be sent along explicit route (specified path).Path message is carried the OAM information list in each MEG territory; Its content includes but not limited to: MEG ID; MEP ID and corresponding nodes/port address thereof; MIP corresponding nodes/port address (specifying the situation of MIP position), some other OAM attribute (, perhaps whether enabling the indication information of OAM(Operation Administration Maintenance) etc.) like parameters relevant such as cycles with concrete OAM(Operation Administration Maintenance).
Note following some:
(i) MEL of T-MPLS adopts flexible way, need not carry MEL information (these are different with Ethernet).
If (ii) same port has the MEP of different levels, need to specify hierarchical relationship/processing sequence relation
(iii) MEP ID will guarantee uniquely in a MEG territory, can not repeat, and can directly be with in the OAM information list, forms one-to-one relationship with MEP place node/port address; Perhaps be sign of each port assignment (assurance does not repeat) in advance, and then set up the binding relationship of the node/port at MEP ID and its place through signaling through webmaster etc.
Step s402, each receives the node/port of Path message, detects the OAM information list that carries in the Path message, preserves the information relevant with self, up to destination node.
After the destination node of step s403, LSP receives the Path message of carrying OAM information, send Resv message.Resv message can be carried OAM information.
Step s404, receive the node of Resv message,, accomplish the OAM attribute configuration according to the OAM attribute information of preserving.
Note following some:
I) as 1) said, if the corresponding relation of MEP ID and MEP place node/port address is not carried in the OAM information list, the node at MEP ID and its place/port binding relation can be accomplished in this step so.
Ii) if not according to appointed positions configuration MIP, but automatically remaining point is configured to MIP, so, need in the OAM information list, carry the positional information of MIP.The information of Path message arrangement MEG and MEP, when returning Resv message, automatically that all are remaining node configuration becomes MIP.According to the characteristics of T-MPLS MEL, MIP only handles the message of MEL=0, so, the determining positions of MIP it belong to which MEG territory, do not receive the influence of multilayer.
With Fig. 6 is example, and OAM information to be disposed does not have the information of MEL shown in table 3 and table 4.
The OAM information that table 3 T-MPLS management domain (Fig. 6) is to be disposed
The OAM information list that table 4 Path message is carried is (embodiment two) for example
Need to prove: the part of grey can not be listed in the table in the table, because there is not the informational needs configuration.When a plurality of maintenance point information of node/port arrangement, from top to bottom ordinal relation embodies the precedence relationship of these points of configuration in the form.
The embodiment of the invention also provides a kind of domain-striding maintenance management system; As shown in Figure 7, comprise a plurality of configuring maintenance points 1,2,3,4,5,6 of treating, wherein; In the territory of the A of operator; Treat that configuring maintenance point 1 is the source maintenance point, treat that configuring maintenance point 2 is middle maintenance point, treat that configuring maintenance point 3 is the place maintenance point; In the territory of the B of operator, treat that configuring maintenance point 4 is the source maintenance point, treat that configuring maintenance point 5 is middle maintenance point, treat that configuring maintenance point 6 is the place maintenance point.In service provider's territory, treat that configuring maintenance point 1 is the source maintenance point, treat that configuring maintenance point 2 is middle maintenance point; Treat that configuring maintenance point 3 is middle maintenance point; Treat that configuring maintenance point 4 is middle maintenance point, treat that configuring maintenance point 5 is middle maintenance point, treat that configuring maintenance point 3 is the place maintenance point.Wherein, the source maintenance point is used for the message of carrying OAM attribute configuration indication information according to specified path backward to the maintenance point transmission, and disposes the OAM attribute of said source maintenance point according to said OAM attribute configuration indication information; Middle maintenance point is used to receive the message of carrying OAM attribute configuration indication information from the forward direction maintenance point, and transmits said message of carrying OAM attribute configuration indication information to maintenance point backward according to specified path; OAM attribute according to the said middle maintenance point of said OAM attribute configuration indication information configuration; The place maintenance point is used to receive the message of carrying OAM attribute configuration indication information that middle maintenance point sends, and disposes the OAM attribute of said place maintenance point according to said OAM attribute configuration indication information.
The embodiment of the invention provides a provenance maintenance point, and is as shown in Figure 8, comprising: message sending unit 11 is used for the message of carrying OAM attribute configuration indication information according to specified path backward to the maintenance point transmission; OAM attribute configuration unit 12 is used for the OAM attribute according to said this maintenance point of OAM attribute configuration indication information configuration.First memory cell 13 is used to preserve the OAM attribute information relevant with this maintenance point.
The embodiment of the invention provides the place maintenance point, and is as shown in Figure 9, comprising: message sink unit 21 is used to receive the message of carrying OAM attribute configuration indication information that other maintenance point transmission are got off; OAM attribute configuration unit 22 is used for the OAM attribute according to said this maintenance point of OAM attribute configuration indication information configuration.Second memory cell 23 is used to preserve the OAM attribute information relevant with this maintenance point.
The embodiment of the invention provides a kind of middle maintenance point; Shown in figure 10; Comprise: message transfer unit 31; Be used to receive the message of carrying OAM attribute configuration indication information, and transmit said message of carrying OAM attribute configuration indication information to maintenance point backward according to specified path from the forward direction maintenance point; OAM attribute configuration unit 32 is used for the OAM attribute according to said this maintenance point of OAM attribute configuration indication information configuration.The 3rd memory cell 33 is used to preserve the OAM attribute information relevant with this maintenance point.
Embodiments of the invention also provide a kind of domain-striding maintenance management system; Comprise: the source maintenance point; The message that is used for carrying OAM attribute configuration indication information to place maintenance point transmission, and disposes the OAM attribute of said source maintenance point according to specified path according to said OAM attribute configuration indication information; The place maintenance point is used to receive the message of carrying OAM attribute configuration indication information that said source maintenance point sends, and disposes the OAM attribute of said place maintenance point according to said OAM attribute configuration indication information.
In the embodiment of the invention; Automatically realize striding the relevant information configuration of management domain; Webmaster need not send the webmaster order, dispose the OAM attribute of each node respectively to each node, and only need can realize the automatic OAM attribute configuration of a plurality of nodes in the message of treating between the configuration node to carry through transmission the OAM attribute information; Therefore improve allocative efficiency, alleviated the task amount of network management configuration OAM attribute.
Through the description of above execution mode, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware, but the former is better execution mode under a lot of situation.Based on such understanding; The part that technical scheme of the present invention contributes to prior art in essence in other words can be come out with the embodied of software product; This computer software product is stored in the storage medium, comprises that some instructions are used so that a station terminal equipment (like mobile phone, PDA etc.) is carried out the described method of each embodiment of the present invention.
More than disclosedly be merely several specific embodiment of the present invention, still, the present invention is not limited thereto, any those skilled in the art can think variation all should fall into protection scope of the present invention.
Claims (6)
1. collocation method of realizing domain-striding maintenance management, this method is applied to a network end to end, comprises two domain maintenance management at least, it is characterized in that this method specifically comprises:
Treat that configuring maintenance point receives the message of carrying operation management OAM attribute configuration indication information; Said message comprises the destination node information of a plurality of domain maintenance management; Said destination node information comprises the destination node position of domain maintenance management at least; The said configuring maintenance point of treating is allocated Maintenance Point Identification in advance; Carry the said positional information of treating configuring maintenance point in the said destination node information when treating that the configuring maintenance point detects, the said configuration node of treating is configured to destination node, identify pre-assigned Maintenance Point Identification as destination node simultaneously;
The said configuring maintenance point of treating detects the OAM information list that carries in the said message; Preserve the information relevant with self; Specifically comprise: the said configuring maintenance point of treating parses the OAM attribute information of corresponding this maintenance point according to the positional information of this maintenance point, and the said configuring maintenance point of treating is preserved the OAM attribute information of being correlated with;
The said OAM attribute of treating the configuring maintenance point according to said this maintenance point of destination node information configuration is specially: said treat that the configuring maintenance point receives the affirmation message of the OAM attribute configuration of returning after, according to the OAM attribute information of preserving, accomplish the OAM attribute configuration.
2. the collocation method of domain-striding maintenance management as claimed in claim 1 is characterized in that, the rank of the different domain maintenance management at said a plurality of domain maintenance management place is different.
3. the collocation method of domain-striding maintenance management as claimed in claim 1 is characterized in that, saidly treats that configuring maintenance point receives the message carry operation management OAM attribute configuration indication information and comprises:
The said configuring maintenance point of treating is accomplished all the not OAM attribute configuration of same area according to the OAM attribute indication information; Or
The said configuring maintenance point of treating carries out single domain configuration, the perhaps configuration of a plurality of parallel non-nested domain maintenance management according to the OAM attribute indication information at every turn; Repeat said operation, accomplish all the not OAM attribute configuration of same area.
4. the collocation method of domain-striding maintenance management as claimed in claim 3 is characterized in that, the said configuring maintenance point of treating carries out the single domain configuration according to the OAM attribute indication information at every turn, and perhaps the configuration of a plurality of parallel non-nested domain maintenance management specifically comprises,
For nested domain, on same node or port, use the intermediate node of the domain maintenance management of other domain maintenance management intermediate node replacement second level of the first order.
5. the collocation method of domain-striding maintenance management as claimed in claim 4 is characterized in that, also comprises:
When said treat the configuring maintenance point be in the middle of during maintenance point; Reception is from the message of carrying OAM attribute configuration indication information of forward direction maintenance point; Detect the OAM information list that carries in the said message; Preserve the information relevant, and transmit said message of carrying OAM attribute configuration indication information to maintenance point backward according to specified path with self.
6. like the collocation method of arbitrary described domain-striding maintenance management in the claim 1,3 to 5, it is characterized in that the said configuration node of treating is in the ethernet management territory or transmits multiprotocol label switching T-MPLS management domain.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007103075387A CN101471813B (en) | 2007-12-29 | 2007-12-29 | Configuration method, system and equipment for implementing domain-striding maintenance management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007103075387A CN101471813B (en) | 2007-12-29 | 2007-12-29 | Configuration method, system and equipment for implementing domain-striding maintenance management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101471813A CN101471813A (en) | 2009-07-01 |
| CN101471813B true CN101471813B (en) | 2012-06-27 |
Family
ID=40828956
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007103075387A Active CN101471813B (en) | 2007-12-29 | 2007-12-29 | Configuration method, system and equipment for implementing domain-striding maintenance management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101471813B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102045184B (en) | 2009-10-22 | 2012-09-05 | 华为技术有限公司 | Automatic management method for customer edge equipment and PE equipment |
| CN101771616B (en) * | 2010-02-23 | 2015-06-10 | 中兴通讯股份有限公司 | Method and system for forwarding and ending message |
| CN102255742B (en) * | 2010-05-19 | 2013-09-25 | 华为技术有限公司 | Method, device and related equipment for acquiring management route |
| CN102136991B (en) * | 2010-07-02 | 2013-10-09 | 华为技术有限公司 | Method and node for configuring tunnel on label switching path |
| CN102136945B (en) * | 2011-02-16 | 2014-03-12 | 华为技术有限公司 | Method for establishing label switch path (LSP) protection and node |
| CN102185764B (en) * | 2011-04-25 | 2015-04-01 | 中兴通讯股份有限公司 | Method and device for receiving and processing OAM (operation, administration and maintenance) messages in link layer and switch |
| CN102790702B (en) * | 2011-05-19 | 2017-09-08 | 中兴通讯股份有限公司 | The detection method of packet path Signal Degrade, apparatus and system |
| CN102843249B (en) * | 2011-06-21 | 2018-09-18 | 南京中兴新软件有限责任公司 | The method and apparatus that maintenance management state is transmitted in a kind of grouping conveying network |
| WO2012149763A1 (en) * | 2011-09-22 | 2012-11-08 | 华为技术有限公司 | Method and device for configuring operation, administration and maintenance attributes |
| CN102868569B (en) | 2012-06-30 | 2015-12-09 | 华为技术有限公司 | The method for testing performance of Layer3 Virtual Private Network, node and system |
| CN103152205B (en) * | 2013-03-22 | 2016-02-10 | 烽火通信科技股份有限公司 | Based on OAM processing method and the device of stream index |
| CN105308904B (en) | 2014-04-04 | 2019-05-21 | 华为技术有限公司 | A kind of OAM message processing method, the network equipment and network system |
| CN106301858A (en) * | 2015-06-09 | 2017-01-04 | 中兴通讯股份有限公司 | Packet Transport Network equipment and resource recovery method, device |
| CN113709049A (en) * | 2020-05-20 | 2021-11-26 | 中兴通讯股份有限公司 | Method for creating intermediate point of maintenance entity group, node and readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1334662A (en) * | 2000-07-24 | 2002-02-06 | 阿尔卡塔尔加拿大公司 | Network management support of operation and management functions, and method therefor |
| CN1728651A (en) * | 2004-07-08 | 2006-02-01 | 阿尔卡特公司 | Domain Configuration in Ethernet Operations Management Maintenance Networks with Multiple Levels |
| CN1794662A (en) * | 2004-12-22 | 2006-06-28 | 阿尔卡特公司 | Autoconfiguration of Ethernet oam points |
| CN1870504A (en) * | 2005-05-23 | 2006-11-29 | 阿尔卡特公司 | Extension to RSVP protocol for supporting OAM configuration |
-
2007
- 2007-12-29 CN CN2007103075387A patent/CN101471813B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1334662A (en) * | 2000-07-24 | 2002-02-06 | 阿尔卡塔尔加拿大公司 | Network management support of operation and management functions, and method therefor |
| CN1728651A (en) * | 2004-07-08 | 2006-02-01 | 阿尔卡特公司 | Domain Configuration in Ethernet Operations Management Maintenance Networks with Multiple Levels |
| CN1794662A (en) * | 2004-12-22 | 2006-06-28 | 阿尔卡特公司 | Autoconfiguration of Ethernet oam points |
| CN1870504A (en) * | 2005-05-23 | 2006-11-29 | 阿尔卡特公司 | Extension to RSVP protocol for supporting OAM configuration |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101471813A (en) | 2009-07-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101471813B (en) | Configuration method, system and equipment for implementing domain-striding maintenance management | |
| CN112104551B (en) | Border gateway protocol for communication between software defined network controllers | |
| EP2568670B1 (en) | Method for message forwarding and device for deep packet inspection | |
| CN101820395B (en) | Routing information configuration and private network label addition method and device based on MPLS (Multiple Protocol Label Switching) | |
| EP1986370B1 (en) | Control system, data message transmission method and network device in the ethernet | |
| US9692637B2 (en) | Fault protection method and fault protection apparatus in a multi-domain network | |
| JP6920533B2 (en) | Data flow transmission | |
| CN101971563A (en) | Method and apparatus for providing full logical connectivity in mpls networks | |
| CN108337111A (en) | Obtain the method and device of network node topology | |
| CN110417569A (en) | A kind of network link failure processing method and endpoint of a tunnel equipment | |
| CN102377679A (en) | Method for realizing link discovery and management in FTTX access system | |
| CN101771604B (en) | Routing detection method, system and intermediate routing device | |
| CN101355441A (en) | Method, system and equipment for configuring operation management maintain attribute | |
| CN101741678A (en) | A method, device and system for establishing a virtual local area network connection | |
| CN104468365A (en) | Method, system and device for obtaining topology connection relationship between devices | |
| US20140363160A1 (en) | Flexible interconnection of scalable systems integrated using optical networks for datacenters | |
| CN102136991A (en) | Method and node for configuring tunnel on label switching path | |
| CN104283802A (en) | Neighbor discovery method and device | |
| JP2010148087A (en) | Resource management required for calculating multi-level resource transfer network path, and method, and apparatus for calculating recursive path | |
| CN101296178B (en) | Inter-domain flux engineering route computing method and route computing device | |
| US20160013971A1 (en) | Network Element For a Telecommunications Network Having Decoupled Control and Data Planes | |
| CN101677294B (en) | Multilayer network resource optimization method, system and direct optical path server | |
| CN108282406B (en) | Data transmission method, stacking equipment and stacking system | |
| CN101442491B (en) | Route transmission method and routing device for nesting VPN | |
| CN101001124B (en) | Method and device for updating service configuration information |
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 |