CN102299815A - Configuration method and node of OAM (operation, administration and maintenance) - Google Patents
Configuration method and node of OAM (operation, administration and maintenance) Download PDFInfo
- Publication number
- CN102299815A CN102299815A CN2010102138357A CN201010213835A CN102299815A CN 102299815 A CN102299815 A CN 102299815A CN 2010102138357 A CN2010102138357 A CN 2010102138357A CN 201010213835 A CN201010213835 A CN 201010213835A CN 102299815 A CN102299815 A CN 102299815A
- Authority
- CN
- China
- Prior art keywords
- oam
- node
- configuration information
- multicast
- attribute
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a configuration method and node of OAM (operation, administration and maintenance). The configuration method of the OAM comprises the following steps: using an intermediate node of a multicast tree to receive a multicast join message which is transmitted by a downstream node of the intermediate node, wherein the multicast join message comprises the configuration information of the OAM; and using the intermediate node to configure the OAM attribute of the intermediate node in accordance with the configuration information of the OAM and then transmit the multicast join message to an upstream node of the intermediate node, so that an upstream node of the intermediate node configures the self-OAM attribute according to the configuration information of the OAM in the multicast join message and transmit the multicast join message until the multicast join message is transmitted to a root node of the multicast tree hop-by-hop. According to the embodiment of the invention, the automatic configuration of the OAM attributes of the nodes on the multicast tree is realized, the workload of manual configuration is reduced, the human errors are avoided and reduced, and the operability is good.
Description
Technical field
The embodiment of the invention relates to communication technical field, relates in particular to the collocation method and the node of a kind of operation management and maintenance.
Background technology
Video traffic is one of important service of following Operator Specific Service growth, and operator need provide the service of satisfying the user quality demand to the user, improves user satisfaction, improves number of users and avoids customer loss, improves the operation management ability of video network.The operation of multicast network, administer and maintain (OperationAdministration and Maintenance; Hereinafter to be referred as: OAM) can before fault takes place, detect the deterioration of network performance, take appropriate measures to avoid the generation of fault by the fault point or the performance bottleneck point of active probe or monitoring discovery network; After breaking down, can respond fast, reduce the used time of fault location, trigger corresponding protection mechanism, and can optimize the utilization of Internet resources.
The function of OAM definition generally includes fault management and performance measurement two classes.Wherein, fault management comprises detection of connectivity, Connectivity Verification, loopback, alarm indication signal, remote defect indication, locking signal and APS etc.; Performance measurement comprises packet loss measurement, delay measurements and throughput measurement etc.
Web TV (Internet Protocol Television; Hereinafter to be referred as: video traffic IPTV) has unidirectional, as to put multiple spot multicast and transmits characteristics, and the OAM of multicast network finishes by the transmission of unidirectional OAM message usually.For example for performance measurement, can send packet loss by transmitting terminal and measure the OAM message, in this OAM message, carry the transmission message amount of transmitting terminal statistics, the message amount of receiving terminal statistics actual reception, contrast the transmission message amount of carrying in the above-mentioned OAM message again, obtain message dropping quantity; The delay measurements method that can beat timestamp by the delay measurements message that sends to transmitting terminal in like manner, measured message arrive receiving terminal the time delay of process.When the message dropping rate of certain hour at interval, or latency measurement is when exceeding normal thresholding, judges multicast network generation decreased performance or takes place unusually.
Above-mentioned performance measurement and other OAM detection meanss not only can be carried out between the root node of multicast tree and leaf node, also can carry out on the intermediate node between root node and the leaf node.Before measuring, network need be configured root node, leaf node and the intermediate node of multicast tree that participate in to measure, disposes the processing mode of these nodes to the OAM message, for example: enable and go to enable etc.
In the prior art, can carry out the OAM configuration to each node on the multicast tree by manual configuration or management agreement, to finish OAM configuration to root node, leaf node and the intermediate node of multicast tree that participate in to measure, but this method need be configured all nodes on the multicast tree, complicated operation when multicast tree is larger, and make mistakes the O﹠M cost height easily.
Summary of the invention
The embodiment of the invention provides the collocation method and the node of a kind of operation management and maintenance, to realize the automatic configuration to the OAM attribute of node on the multicast tree, reduces the workload of artificial configuration, avoids and reduces mistake.
The embodiment of the invention provides the collocation method of a kind of operation management and maintenance, comprising:
The intermediate node of multicast tree receives the multicast that the downstream node of described intermediate node sends and joins message, and described multicast joins message and comprises operation, administers and maintains (OAM) configuration information;
Described intermediate node disposes the OAM attribute of described intermediate node according to described OAM configuration information, and described multicast joined message send to the upstream node of described intermediate node, so that the OAM attribute of the configuration of the OAM configuration information during the upstream node of described intermediate node joins message according to described multicast self, and send described multicast and join message, be sent to the root node of described multicast tree until hop-by-hop that described multicast is joined message.
The embodiment of the invention also provides the collocation method of a kind of operation management and maintenance, comprising:
The root node of multicast tree receives the multicast that the downstream node of described root node sends and joins message, and described multicast joins message and comprises operation, administers and maintains (OAM) configuration information;
Described root node disposes the OAM attribute of described root node according to described OAM configuration information.
The embodiment of the invention also provides a kind of intermediate node of multicast tree, comprising:
Receiver module is used to receive the multicast that the downstream node of described intermediate node sends and joins message, and described multicast joins message and comprises operation, administers and maintains (OAM) configuration information;
Configuration module is used for disposing according to described OAM configuration information the OAM attribute of described intermediate node;
Sending module, be used for described multicast joined message and send to the upstream node of described intermediate node, so that the OAM attribute of the configuration of the OAM configuration information during the upstream node of described intermediate node joins message according to described multicast self, and send described multicast and join message, be sent to the root node of described multicast tree until hop-by-hop that described multicast is joined message.
The embodiment of the invention also provides a kind of root node of multicast tree, comprising:
The message receiver module is used to receive the multicast that the downstream node of described root node sends and joins message, and described multicast joins message and comprises operation, administers and maintains (OAM) configuration information;
The attribute configuration module is used for disposing according to described OAM configuration information the OAM attribute of described root node.
The embodiment of the invention also provides a kind of leaf node of multicast tree, comprising:
The nodal community configuration module is used for according to the operation of disposing on described leaf node, administers and maintains the OAM attribute that (OAM) configuration information disposes described leaf node;
The message sending module is used for joining message to the upstream node transmission multicast of described leaf node, and described multicast joins message and comprises described OAM configuration information.
Pass through the embodiment of the invention, the intermediate node of multicast tree receives after multicast that the downstream node of this intermediate node sends joins message, OAM configuration information in joining message according to this multicast disposes the OAM attribute of this intermediate node, sends this multicast to the upstream node of this intermediate node then and joins message; The root node of multicast tree receives after multicast joins message, and the OAM configuration information in joining message according to this multicast disposes the OAM attribute of this root node; Thereby realized the automatic configuration to the OAM attribute of node on the multicast tree, reduced the workload of artificial configuration, avoided and reduced mistake, operability is good.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do one to the accompanying drawing of required use in embodiment or the description of the Prior Art below introduces simply, apparently, accompanying drawing in describing below is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the flow chart of an embodiment of collocation method of operation management of the present invention and maintenance;
Fig. 2 is the flow chart of another embodiment of collocation method of operation management of the present invention and maintenance;
Fig. 3 is the flow chart of another embodiment of collocation method of operation management of the present invention and maintenance;
Fig. 4 is the schematic diagram that concerns of multicast tree OAM entity of the present invention;
Fig. 5 adds the schematic diagram of an embodiment of coding source address format of attribute for the present invention;
Fig. 6 adds the schematic diagram of an embodiment of attribute format for OAM of the present invention;
Fig. 7 is the schematic diagram of the embodiment of form of MIP configuration TLV of the present invention;
Fig. 8 is the schematic diagram of the embodiment of form of MEP_I configuration TLV of the present invention;
Fig. 9 is the schematic diagram of the embodiment of form of MEP_E configuration TLV of the present invention;
Figure 10 is the schematic diagram of an embodiment of form of OAM config option in the hello packet of the present invention;
Figure 11 is the structural representation of an embodiment of leaf node of multicast tree of the present invention;
Figure 12 is the structural representation of an embodiment of intermediate node of multicast tree of the present invention;
Figure 13 is the structural representation of another embodiment of intermediate node of multicast tree of the present invention;
Figure 14 is the structural representation of an embodiment of root node of multicast tree of the present invention;
Figure 15 is the structural representation of an embodiment of configuration-system of operation management of the present invention and maintenance.
Embodiment
For the purpose, technical scheme and the advantage that make the embodiment of the invention clearer, below in conjunction with the accompanying drawing in the embodiment of the invention, technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, the every other embodiment that those of ordinary skills are obtained under the prerequisite of not making creative work belongs to the scope of protection of the invention.
Fig. 1 is the flow chart of an embodiment of collocation method of operation management of the present invention and maintenance, and as shown in Figure 1, the collocation method of this operation management and maintenance can comprise:
Present embodiment disposes above-mentioned OAM configuration information at the leaf node of multicast tree in advance, particularly, can pass through command line interface (Command Line Interface; Hereinafter to be referred as: CLI), network management protocol or other control protocols dispose above-mentioned OAM configuration information at the leaf node of multicast tree in advance.
Certainly the embodiment of the invention is not limited in this, also can adopt other modes at the leaf node configuration OAM of multicast tree configuration information, and the embodiment of the invention does not limit this.
Particularly, according to the OAM attribute that disposes this leaf node at the OAM configuration information that disposes on the leaf node of multicast tree can for: leaf node according to above-mentioned OAM configuration information configuration OAM attribute on the incoming interface of this leaf node and/or outgoing interface, for example: can on the incoming interface of this leaf node and/or outgoing interface, the configuring maintenance group of entities go out end points (Maintenance Entity Group End PointEgress; Hereinafter to be referred as: MEP_E) enable, perhaps MEP_E goes to enable; Promptly can be on the incoming interface and/or outgoing interface of leaf node with the OAM attribute configuration, the function of support can enable for the packet loss measurement, and delay measurements enables, or the OAM(Operation Administration Maintenance) of other kinds.
In the present embodiment, after OAM attribute, can dynamically follow the tracks of the variation of multicast tree topology, need to set up the related of the OAM attribute of configuration and multicast tree state for making at the OAM attribute of leaf node configuration according to OAM configuration information configuration leaf node.When the multicast state of leaf node because of the variation of multicast tree topology when deleted, the OAM attribute that is configured to the incoming interface of this leaf node and outgoing interface is also deleted, avoids useless OAM attribute residual on no artis.
Particularly, to the upstream node of this leaf node send multicast join message can for: the leaf node of multicast tree can periodically send to the upstream node of this leaf node or send this multicast as required and join message.
In the foregoing description, the leaf node of multicast tree disposes the OAM attribute of this leaf node according to the OAM configuration information, and send the multicast that carries this OAM configuration information to the upstream node of this leaf node and join message, so that the upstream node of this leaf node is according to the OAM attribute of this OAM configuration information configuration self, thereby realized automatic configuration to the OAM attribute of node on the multicast tree, reduced the workload of artificial configuration, avoided and reduced mistake, operability is good.
Fig. 2 is the flow chart of another embodiment of collocation method of operation management of the present invention and maintenance, and as shown in Figure 2, the collocation method of this operation management and maintenance can comprise:
The multicast that step 201, the intermediate node of multicast tree receive the downstream node transmission of this intermediate node joins message, and this multicast joins message and comprises the OAM configuration information.
In the present embodiment, the downstream node of above-mentioned intermediate node can be the upstream node of leaf node and/or this leaf node.
Particularly, intermediate node can be according to this OAM configuration information configuration OAM attribute on the incoming interface of this intermediate node and/or outgoing interface, for example: can be on the incoming interface of this intermediate node and/or outgoing interface configuring maintenance group of entities intermediate point (Maintenance Entity Group Intermediate Point; Hereinafter to be referred as: MIP) enable, perhaps MIP goes to enable; Can be on the incoming interface and/or outgoing interface of intermediate node with the OAM attribute configuration, the function of support can enable for the packet loss measurement, and delay measurements enables, or the OAM(Operation Administration Maintenance) of other kinds.
Particularly, in the present embodiment, the multicast upstream node that sends to this intermediate node that joins message can periodically be sent or send to as required the upstream node of this intermediate node for: intermediate node can join message this multicast.
In a kind of implementation of present embodiment, intermediate node can comprise an incoming interface and at least two outgoing interfaces, the OAM configuration information that receives when at least two outgoing interfaces is not simultaneously, this intermediate node can dispose different OAM attributes at least respectively according to the OAM configuration information that above-mentioned at least two outgoing interfaces receive on above-mentioned two outgoing interfaces, the OAM configuration information that above-mentioned at least two outgoing interfaces are received carries out fusion treatment again, if the OAM configuration information that above-mentioned at least two outgoing interfaces receive can merge, then on the incoming interface of this intermediate node, dispose the OAM attribute according to the OAM configuration information after the fusion treatment.At this moment, this intermediate node needs to comprise that the multicast of the OAM configuration information after the fusion treatment joins message sends to the upstream node of this intermediate node.Wherein, the OAM configuration information that at least two outgoing interfaces receive can merge can for: the OAM configuration information that at least two outgoing interfaces receive is contradiction not, and the OAM configuration information that intermediate node receives according at least two outgoing interfaces can form the OAM configuration information to the upstream node unanimity of this intermediate node.For instance, suppose that downstream node place that OAM configuration information that an outgoing interface of intermediate node receives links to each other with this outgoing interface for configuration transmits branch and enable for packet loss measurement attribute, be configured on incoming interface and the outgoing interface; And the OAM configuration information that another outgoing interface of this intermediate node receives enables the delay measurements attribute for the downstream node place forwarding branch that configuration links to each other with this outgoing interface, also is configured on incoming interface and the outgoing interface; At this moment, the OAM configuration information that two outgoing interfaces of this intermediate node receive can merge, after the OAM configuration information that this intermediate node receives two outgoing interfaces of this intermediate node carried out fusion treatment, the OAM configuration information of acquisition was for measuring attribute to packet loss and the delay measurements attribute enables.
In the another kind of implementation of present embodiment, this multicast joins message except that the OAM configuration information, can also comprise other adding attributes except that above-mentioned OAM configuration information, then this intermediate node can carry out fusion treatment to this OAM configuration information and other adding attributes except that above-mentioned OAM configuration information earlier, disposes the attribute of this intermediate node then according to the result of fusion treatment.
In addition, after intermediate node disposes the OAM attribute of this intermediate node according to the OAM configuration information, can dynamically follow the tracks of the variation of multicast tree topology, need to set up the related of the OAM attribute of configuration and multicast tree state for making at the OAM attribute of intermediate node configuration.When the multicast state of intermediate node because of the variation of multicast tree topology when deleted, the OAM attribute that is configured to the incoming interface of this leaf node and outgoing interface is also deleted, avoids useless OAM attribute residual on no artis.
In the foregoing description, the intermediate node of multicast tree receives after multicast that the downstream node of this intermediate node sends joins message, OAM configuration information in joining message according to this multicast disposes the OAM attribute of this intermediate node, and sends this multicast to the upstream node of this intermediate node and join message; Thereby realized the automatic configuration to the OAM attribute of node on the multicast tree, reduced the workload of artificial configuration, avoided and reduced mistake, operability is good.
Fig. 3 is the flow chart of another embodiment of collocation method of operation management of the present invention and maintenance, and as shown in Figure 3, the collocation method of this operation management and maintenance can comprise:
The multicast that step 301, the root node of multicast tree receive the downstream node transmission of this root node joins message, and this multicast joins message and comprises the OAM configuration information.
Particularly, this root node can be according to incoming interface and/or the outgoing interface configuration OAM attribute of above-mentioned OAM configuration information at this root node; For example: can go into end points (Maintenance Entity Group End Point Ingress in the incoming interface and/or the outgoing interface configuring maintenance group of entities of this root node; Hereinafter to be referred as: MEP_I) enable, perhaps MEP_I goes to enable; Can be on the incoming interface and/or outgoing interface of root node with the OAM attribute configuration, the function of support can enable for the packet loss measurement, and delay measurements enables, or the OAM(Operation Administration Maintenance) of other kinds.
In a kind of implementation of present embodiment, root node can comprise an incoming interface and at least two outgoing interfaces, the OAM configuration information that receives when at least two outgoing interfaces is not simultaneously, this root node can dispose different OAM attributes at least respectively according to the OAM configuration information that above-mentioned at least two outgoing interfaces receive on above-mentioned two outgoing interfaces, the OAM configuration information that above-mentioned at least two outgoing interfaces are received carries out fusion treatment again, if the OAM configuration information that above-mentioned at least two outgoing interfaces receive can merge, then on the incoming interface of this root node, dispose the OAM attribute according to the OAM configuration information after the fusion treatment.Wherein, determine that the OAM configuration information that at least two outgoing interfaces receive can merge and can not repeat them here with reference to the present invention's method that provides embodiment illustrated in fig. 2.
In the another kind of implementation of present embodiment, this multicast joins message except that the OAM configuration information, also comprise other adding attributes except that above-mentioned OAM configuration information, then this root node can carry out fusion treatment to this OAM configuration information and other adding attributes except that above-mentioned OAM configuration information earlier, disposes the attribute of this root node then according to the result of fusion treatment.
In the present embodiment, after OAM attribute, can dynamically follow the tracks of the variation of multicast tree topology, need to set up the related of the OAM attribute of configuration and multicast tree state for making at the OAM attribute of root node configuration according to OAM configuration information configuration root node.When the multicast state of root node because of the variation of multicast tree topology when deleted, the OAM attribute that is configured to the incoming interface of this root node and outgoing interface is also deleted, avoids useless OAM attribute residual on no artis.
In the foregoing description, the root node of multicast tree receives after multicast joins message, and the OAM configuration information in joining message according to this multicast disposes the OAM attribute of this root node; Thereby realized the automatic configuration to the OAM attribute of node on the multicast tree, reduced the workload of artificial configuration, avoided and reduced mistake, operability is good.
Fig. 1 of the present invention, Fig. 2 and embodiment illustrated in fig. 3 in MEP_I, MIP and MEP_E be 3 kinds of OAM entities, the OAM message sends at MEP_I usually, transmits through MIP, terminates at MEP_E.Fig. 4 is the schematic diagram that concerns of multicast tree OAM entity of the present invention, and as shown in Figure 4, multicast tree comprises MEP_I, MIP and MEP_E, and the network equipment (Network Equipment; Hereinafter to be referred as: NE).
Wherein, MEP_I is used to send the OAM message, and for example when packet loss was measured, MEP_I counted multicast traffic stream, and count value is write in the packet loss measured message of packet loss detection and send; And/or when delay measurements, MEP_I can beat time stamp to the delay measurements message and send;
The MEP_E OAM message that is used to terminate, for example when packet loss was measured, MEP_E can count data stream, obtained the number of dropped packets of MEP_I to MEP_E, calculated in a period of time MEP_I to the packet loss of MEP_E; And/or MEP_E can read the time stamp that carries in the delay measurements message when delay measurements, and the time value of this locality when the delay measurements message received in record is simultaneously calculated the time delay from MEP_I to MEP_E;
MIP is used to monitor the OAM message, and the OAM message is transmitted to downstream node, or the OAM message is carried out transparent transmission.For example measure and delay measurements for packet loss, the handling principle of MIP is identical with the handling principle of MEP_E, but calculating is packet loss and the time delay that MEP_I arrives this MIP.
MEP_I, MIP and MEP_E are all logic entity, can be positioned at incoming interface and/or the outgoing interface of NE.The enabling and go to enable of the OAM(Operation Administration Maintenance) of MEP_I, MIP and MEP_E can be passed through Extended Protocol independent multicast (Protocol Independent Multicast; Hereinafter to be referred as: PIM) agreement is configured.The benefit of expansion PIM agreement is can avoid loaded down with trivial details human configuration more for a long time at the multicast tree intermediate node, can not increase extra control aspect burden, can open up the variation of benefit by the self-adaptive multicast tree, and can utilize the reliability treatment mechanism of PIM agreement itself, guarantee the reliability of configuration.
The basic principle of PIM agreement is: multicast tree downstream node (comprising leaf node) upstream nodes (comprising root node) hop-by-hop sends PIM and joins message or the PIM prune packet.The multicast forwarding list item that upstream node can join message according to the PIM of downstream node and be building up to downstream node is deleted this multicast forwarding list item by the prune packet in overtime or downstream.Have the connection of the node of multicast forwarding list item according to from the root node to the leaf node all, constitute multicast tree.
The embodiment of the invention joins message to original PIM and expands, PIM after the expansion join message be called the expansion PIM join message, Fig. 1 of the present invention, Fig. 2 and embodiment illustrated in fig. 3 in multicast join message can for the expansion PIM join message, certainly the embodiment of the invention is not limited in this, multicast joins message and also can be joining message in any multicast routing protocol, the embodiment of the invention does not limit this, but in the description of following examples of the present invention, joining message with this multicast serves as that to join message be that example describes to expansion PIM.
The embodiment of the invention is carried the OAM configuration information by the new adding attribute of definition in expansion PIM joins message, and finishes some transmits the configuration of the OAM attribute of branch on multicast tree or the multicast tree.
Above-mentioned expansion PIM joins message, and can periodically send, and also can send as required, adopts which kind of mode to send to depend on the configuration on the leaf node of the implementation of PIM agreement itself and/or multicast tree, and the embodiment of the invention does not limit this.
Set up multicast tree characteristics from bottom to top according to the PIM agreement, the manager can dispose the OAM configuration information of the forwarding branch from root node to this leaf node being prevaricated enforcement at the leaf node of multicast tree, and this OAM configuration information can be for enabling the performance monitoring from root node to all intermediate nodes certain leaf node; And according to the OAM attribute of this OAM configuration information configuration leaf node.Then, during this OAM configuration information is carried at expansion PIM joins message, and the expansion PIM that will carry the OAM configuration information joins message from this leaf node hop-by-hop to the root node transmission, promptly expands PIM and joins message and transmit successively from the downstream node to the upstream node, ends at root node.OAM configuration information during each hop node joins message according to this expansion PIM disposes the OAM attribute of this hop node, if failure occurs in the configuration of certain node, and can be to webmaster or downstream node feedback configuration failure information.
When the OAM attribute of the node of multicast tree being configured by expansion PIM agreement, usually require the different identical OAM configuration informations of leaf node configuration, particularly, intermediate node with at least two outgoing interfaces, OAM configuration information in the expansion PIM that the upstream node of this intermediate node sends joins message is identical with the OAM configuration information of a plurality of downstream nodes of this intermediate node, and at this moment this intermediate node only needs this OAM configuration information is got final product by the upstream node transmission of expanding PIM and joining message to this intermediate node.
But, if the OAM configuration information that the configuration of different leaf nodes is different, then has the OAM configuration information difference that the different outgoing interfaces of the intermediate node of at least two outgoing interfaces receive, this intermediate node can dispose different OAM attributes at least respectively according to the different OAM configuration informations that at least two outgoing interfaces receive on above-mentioned two outgoing interfaces, and then the different OAM configuration informations that above-mentioned at least two outgoing interfaces receive are carried out fusion treatment, the OAM configuration information after the upstream node of this intermediate node transmits fusion treatment then.For instance, downstream node 1 wishes that this downstream node 1 place forwarding branch of configuration enables for packet loss measurement attribute, be configured on incoming interface and the outgoing interface, and downstream node 2 wishes that this downstream node 2 places forwarding branch of configuration enables the delay measurements attribute, also be configured on incoming interface and the outgoing interface, then intermediate node receives after the OAM configuration information of downstream node 1 and downstream node 2 transmissions, the outgoing interface of the corresponding downstream node 1 of this intermediate node can be configured to packet loss is measured attribute enables, and the outgoing interface of corresponding downstream node 2 is configured to the delay measurements attribute is enabled, then the OAM configuration information that receives is carried out fusion treatment, be configured to packet loss measurement attribute and delay measurements attribute are enabled according to the incoming interface of the OAM configuration information after the fusion treatment with this intermediate node.In the embodiment of the invention, if join message to the diffusion of unwanted branch for fear of expansion PIM, also the outgoing interface of downstream node 2 can be configured to blocked state, the expansion PIM that carries the OAM configuration information that incoming interface and outgoing interface enable the delay measurements attribute be joined message send from the incoming interface upstream nodes.
In the embodiment of the invention, the OAM configuration information carries in expansion PIM joins message, and from leaf node, the hop-by-hop upstream nodes sends.If intermediate node receives the different OAM configuration informations that different downstream nodes send, then the expansion PIM that sends of this intermediate node upstream nodes joins message and carries the configuration information of OAM after the fusion treatment.If the OAM configuration information of the different downstream nodes of intermediate node can't merge, then this intermediate node abandons disposing the OAM attribute of the OAM configuration information correspondence that can't merge, and sends failure to the downstream node or the relevant OAM configuration information of webmaster report of this intermediate node.For the processing burden that reduces the PIM agreement with avoid mistake to produce, can on different leaf nodes, dispose identical OAM configuration information as far as possible.Wherein, the OAM configuration information of the different downstream nodes of intermediate node can't merge can be the OAM configuration information contradiction of the different downstream nodes of intermediate node, and intermediate node can't form OAM configuration information to the upstream node unanimity of this intermediate node according to the OAM configuration information of different downstream nodes.For instance, this downstream node 1 place forwarding branch of downstream node 1 hope configuration of supposing intermediate node enables for packet loss measurement attribute, be configured on incoming interface and the outgoing interface, and the downstream node 2 of this intermediate node wishes that measurement is blocked state to this downstream node 2 places forwarding branch of configuration to packet loss, also be configured on incoming interface and the outgoing interface, at this moment because downstream node 1 wishes that the packet loss measured message can send to the outgoing interface that this downstream node 1 connects from the incoming interface of this intermediate node, and downstream node 2 wishes that obstruction packet loss measured message enters from the incoming interface of this intermediate node, therefore, at this moment the OAM configuration information of the downstream node 1 of this intermediate node and downstream node 2 can't merge.
In the embodiment of the invention, MEP_E and MEP_I can be configured in respectively on the leaf node and root node of multicast tree, MIP is configured on the leaf node and the intermediate node between the root node of multicast tree, to realize configuration to a whole multicast tree or a multicast forwarding branch, but in the embodiment of the invention, MEP_E and MEP_I are not limited to be configured at the leaf node of multicast tree and root node, also MEP_I can be configured on the non-root node, and MEP_E is configured on the non-leaf node.In this case, the OAM message still inserts from MEP_I, to the MEP_E termination; And expansion PIM joins message and still is sent to root node from the leaf node hop-by-hop, does not influence the realization of the embodiment of the invention.If expansion PIM agreement supports subtree and part to transmit the configuration of branch, also need in joining message, carry expansion PIM the interface IP address of MEP_I to be configured and MEP_E.
Depend on different application scenarioss, the expansion PIM different OAM configuration information of portability that joins message is an example with the OAM configuration information of the intermediate node of multicast tree, can dispose for MIP, MIP enables or MIP goes to enable etc.And, incoming interface and/or outgoing interface that the OAM attribute of configure intermediate nodes can be chosen in intermediate node carry out, the OAM(Operation Administration Maintenance) of supporting can enable and/or delay measurements enables for the packet loss measurement, or the OAM(Operation Administration Maintenance) of other kinds enable/go enable etc., do not repeat them here.
Below mainly be example, the configuration mode of OAM attribute is introduced with the intermediate node, similar in the mode of configuration OAM attribute on the root node with the mode that on intermediate node, disposes the OAM attribute, do not repeat them here.
The expansion PIM form that the form that carries the OAM configuration information can adopt PIM to join message that joins message, but need the new attribute field of definition.Fig. 5 adds the schematic diagram of an embodiment of coding source address format of attribute for the present invention.Below each field among Fig. 5 is introduced.
Address family: internet protocol version four (Internet Protocol version 4; Hereinafter to be referred as: IPv4) or IPv 6 (Internet Protocol version 6; Hereinafter to be referred as: IPv6);
Type of coding: be made as 1, the adding attribute is carried in expression;
The S bit: being made as what showed support at 1 o'clock is sparse mode independent multicast agreement (ProtocolIndependent Multicast-Sparse Mode; Hereinafter to be referred as: PIM-SM);
W bit: PIM join message or the PIM prune packet in be used for the bit of identification sources group or shared group;
R bit: when the W bit is made as 1, also be made as 1;
Mask-length: the mask-length of source subnet;
Source address: multicast source address;
The F bit: the transitive property bit, show the processing when this node is not supported this attribute, be made as and showed that continuing upstream nodes E-Packeted at 1 o'clock, be made as and showed in 0 o'clock and need dropping packets;
The E bit: the attribute end bit illustrates that this attribute is last attribute field that carry this coding source address;
Attribute type: the type of attribute;
Length: the length of value field;
Value: the codomain of this attribute.
Expansion PIM joins message needs the new attribute type of definition, and Fig. 6 is the schematic diagram of an embodiment of OAM adding attribute format of the present invention, among Fig. 6, and F, E and length field described as defined above; Below other fields are introduced.
OAM attribute type: define new numerical value, by (the The InternetAssigned Numbers Authority of the Internet digital distribution mechanism; Hereinafter to be referred as: IANA) distribute, illustrate that this attribute is the attribute that is used for the OAM configuration parameter;
Version number: OAM version number;
ME_ID: a sign of maintenance group under sign MEP_I, MIP and the MEP_E, unique in a domain maintenance management;
MIP Configuration Type length value (Type Length Value; Hereinafter to be referred as: TLV), MEP_I configuration TLV and MEP_E configuration TLV: deploy content, adopt length-type-value structure; For example: type may be defined as:
0 * 01:MIP disposes TLV;
0 * 02:MEP_I disposes TLV;
0 * 03:MEP_E disposes TLV.
Fig. 7 is the schematic diagram of the embodiment of form of MIP configuration TLV of the present invention, and the implication of each field is as follows among Fig. 7:
Type: 01;
Length: the length of the codomain field that begins later from length field;
Attribute field: each indicates and has disposed which kind of OAM(Operation Administration Maintenance), and for example: L may be defined as packet loss and measures, and D may be defined as delay measurements, the fixed-site of every kind of OAM(Operation Administration Maintenance) in attribute field;
The functional configuration type: may be defined as configuration MIP (0 * 01), configure MIP (0 * 02), MIP and enable (0 * 03), MIP and remove to enable (0 * 04), MIP and block (0 * 05), dispose+enable MIP (0 * 06), dispose+go and enable MIP (0 * 07), and configuration+obstruction MIP (0 * 08) or the like;
The functional configuration position: in incoming interface support (0 * 01), in outgoing interface support (0 * 02), and simultaneously in incoming interface and outgoing interface support (0 * 03) or the like.
Fig. 8 is the schematic diagram of the embodiment of form of MEP_I configuration TLV of the present invention, and the implication of each field is as follows among Fig. 8:
Type: 0 * 02;
Length: the length of the codomain field that begins later from length field;
Attribute field: each indicates and has disposed which kind of OAM(Operation Administration Maintenance), and for example: L may be defined as packet loss and measures, and D may be defined as delay measurements, the fixed-site of every kind of OAM(Operation Administration Maintenance) in attribute field;
The configuration interface address: use when non-whole tree and non-whole path configurations, node is after receiving that expansion PIM joins message, and whether the determining interface address is this node address, if then finish the configuration to node, and end the OAM message is upstream continued to transmit;
The functional configuration position: this functional configuration is at the incoming interface (0 * 01) or the outgoing interface (0 * 02) of this node;
Functional configuration type: configuration (0 * 01), enable (0 * 02), configure (0 * 03), go to enable (0 * 04), dispose+enable (0 * 06), dispose+go and enable (0 * 07), and only carry configuration parameter (0 * 08) etc.; When value is 0 * 06, suppose that MEP_I enables, then only transmit configuration parameter to MEP_I;
The feature operation type: configuration cycle property ground sends (0 * 01) or sends (0 * 02) OAM configuration information as required; This field is used by MEP_I;
Function OAM message sends the cycle: unit is a millisecond, the transmission cycle when the OAM message cycle sends, use by MEP_I, and invalid when being set to 0 * ffffffff.
Function OAM message sends zero-time and function OAM message sends the concluding time: the period that decision OAM message sends, and invalid when being set to 0 * ffffffffff, can use NTP (Network Time Protocol) (NetworkTime Protocol; Hereinafter to be referred as: NTP) markers, use by MEP_I.
Fig. 9 is the schematic diagram of the embodiment of form of MEP_E configuration TLV of the present invention, and the implication of each field is as follows among Fig. 9:
Type: 0 * 03;
Length: the length of the codomain field that begins later from length field;
Attribute field: each indicates and has disposed which kind of OAM(Operation Administration Maintenance), and for example: L may be defined as packet loss and measures, and D may be defined as delay measurements, the fixed-site of every kind of OAM(Operation Administration Maintenance) in attribute field;
Configuration interface address: only when MEP_E is configured on the non-leaf node, use, do not set under the default situations, adopt the carrying node of root node as MEP_E; MEP_E is after receiving expansion PIM joins message, and whether the determining interface address is this node address, if finish the configuration to the MEP-E of this node, and the expansion PIM that will carry the OAM configuration information joins message and continues the upstream nodes transmission.
Functional configuration position: incoming interface on the leaf node (0 * 01) or outgoing interface (0 * 02);
Functional configuration type: configuration (0 * 01), configure (0 * 02), enable (0 * 03), go to enable (0 * 04), dispose+enable (0 * 06), dispose+go and enable (0 * 07) etc.
In the embodiment of the invention, expansion PIM agreement also supports other PIM except that the OAM configuration information to add the processing of attribute, for instance, other PIM adding attributes except that the OAM configuration information can comprise: the topological identity property and/or the reverse forward-path vector attribute that identify many topology informations.Can realize the transmission of many topology informations can realizing the setting and the transmission of reverse forward-path vector on the edge device by reverse forward-path vector attribute by the topological identity property that identifies many topology informations.The topological identity property that identifies many topology informations is used for making up different virtual topologies at same physical network, and reverse forward-path vector attribute is used for setting up multicast tree between two border networks equipment.
Join message when middle when OAM configuration information and above-mentioned two attributes are included in same expansion PIM simultaneously, intermediate node or root node need carry out fusion treatment to these attributes.For example, when being present in an expansion PIM simultaneously, the sign topological identity property of many topology informations and OAM configuration information join message when middle, intermediate node or root node can be with the node in the virtual topology that is identified being carried out the OAM configuration, to enable or to go to enable the OAM(Operation Administration Maintenance) of this virtual topology multicast tree and multicast forwarding branch.For another example, when being present in an expansion PIM simultaneously, reverse forward-path vector attribute and OAM configuration information join message when middle, intermediate node or root node can be with the core network node between two edge devices being carried out the OAM configuration, to enable or to go to enable the OAM(Operation Administration Maintenance) of this core network node.
If same node receives different attribute message from different downstream interfaces, for example: this node receives the OAM configuration information at interface 1, receive many topologys at interface 2 and add attribute etc., then this node need judge that can these attributes merge, if can't merge, then need different adding attributes is handled respectively.If different adding attributes causes contradiction or faulty operation to take place, then this node is not handled these and is added attribute, to downstream node or webmaster report an error.
If the part of nodes on the configuration path is not supported OAM(Operation Administration Maintenance), then send the F bit set in this expansion PIM can being joined message of node that expansion PIM joins message, the value that is about to the F bit is made as " 1 ", do not support the node of OAM configuration information to receive after the expansion PIM that sets the F bit joins message, do not dispose the OAM attribute of this section point, will expand PIM and join message and continue the upstream nodes transmission.
In the embodiment of the invention, can be between the multicast tree neighbor node by the expansion hello packet, carry new Hello option and carry out the negotiation of OAM allocative abilities, Figure 10 is the schematic diagram of an embodiment of form of OAM config option in the hello packet of the present invention, and the implication of each field is as follows among Figure 10:
Option type: define one and be different from other defined PIM Hello option values, for example value is 39;
Option: the length of option value field;
Option value: for example value 01 is common OAM configuration, and other values are still undefined.
In the embodiment of the invention, can determine whether neighbor node has the ability of using the PIM agreement to carry out the OAM configuration by transmitting hello packet between the multicast tree neighbor node.
The embodiment of the invention provides the collocation method of a kind of operation management and maintenance, by expansion PIM agreement, carry the OAM configuration information in expansion PIM joins message, finish the automatic configuration to the node on the multicast tree, the collocation method of above-mentioned operation management and maintenance has the following advantages:
(1) configuration node is few, is finished automatically by the PIM agreement, and operability is good, has reduced the workload of artificial configuration, avoids and has reduced mistake;
(2) expand existing P IM agreement, join message by expansion PIM and carry the OAM configuration information, can not increase the burden of control aspect, extensibility is good;
(3) PIM design of protocol itself has realized the reliable transfer mechanism to message, for example: by periodic refresh or by transmission control protocol (Transmission Control Protocol; Hereinafter to be referred as: TCP) mode such as carrying, realize that the configuration of OAM attribute has natural advantage;
(4) variation that makes the OAM configuration can follow the trail of multicast topology automatically has bigger flexibility.
The operation management that the embodiment of the invention provides and the collocation method of maintenance not only are applicable to sparse mode pim (PIM-Sparse Mode; Hereinafter to be referred as: PIM-SM) with PIM source-specific multicast (PIM-SourceSpecific Multicast; Hereinafter to be referred as: PIM-SSM), also be applicable to other agreements of PIM protocol suite, as bidirectional pim agreement etc.
The operation management that the embodiment of the invention provides and the collocation method of maintenance not only can be used for the IPv4 multicast network, can be used for the IPv6 multicast network equally.In the IPv6 multicast network, can adopt the multicast routing protocol in the IPv6 network, finish configuration to the OAM attribute of the node of IPv6 multicast tree.
In addition, the operation management that provides of the embodiment of the invention and the collocation method of maintenance can also be used for multiprotocol label switching point-to-multipoint (Multi-Protocol Label Switching Point to Multi-Point; Hereinafter to be referred as: MPLS P2MP) in the network, at this moment, can adopt the multicast routing protocol in the MPLS P2MP network, finish configuration the OAM attribute of the node of MPLS P2MP multicast tree.
One of ordinary skill in the art will appreciate that: all or part of step that realizes said method embodiment can be finished by the relevant hardware of program command, aforesaid program can be stored in the computer read/write memory medium, this program is carried out the step that comprises said method embodiment when carrying out; And aforesaid storage medium comprises: various media that can be program code stored such as ROM, RAM, magnetic disc or CD.
Figure 11 is the structural representation of an embodiment of leaf node of multicast tree of the present invention, leaf node in the present embodiment can be realized the flow process that the present invention is embodiment illustrated in fig. 1, as shown in figure 11, this leaf node can comprise: nodal community configuration module 1101 and message sending module 1102;
Wherein, nodal community configuration module 1101 is used for disposing according to the OAM configuration information that disposes the OAM attribute of this leaf node on this leaf node; Particularly, nodal community configuration module 1101 can be according to this OAM configuration information configuration OAM attribute on the incoming interface of this leaf node and/or outgoing interface; For example: the incoming interface of this leaf node and/or outgoing interface can be configured to MEP_E and enable, perhaps MEP_E goes to enable, can be on the outgoing interface of leaf node with the OAM attribute configuration, and the function of support can enable for the packet loss measurement, delay measurements enables, or the OAM(Operation Administration Maintenance) of other kinds.
In addition, in a kind of implementation of present embodiment, this intermediate node can also comprise: module 1103 and/or removing module 1104 are set;
Wherein, module 1103 is set, is used to be provided with timer; At this moment, nodal community configuration module 1101 can also if obtain the OAM configuration information of renewal, then reconfigure the OAM attribute of this leaf node according to the OAM configuration information that upgrades in the effective time of the timer that module 1103 settings are set.
Removing module 1104 is used for after the timer expiry that module 1103 settings are set, if obtain the OAM configuration information of renewal, then deletes the OAM attribute that this leaf node has disposed.
The leaf node of above-mentioned multicast tree, nodal community configuration module 1101 disposes the OAM attribute of this leaf node according to the OAM configuration information, the multicast that message sending module 1102 carries this OAM configuration information to the upstream node transmission of this leaf node joins message, so that the upstream node of this leaf node is according to the OAM attribute of this OAM configuration information configuration self, thereby realized automatic configuration to the OAM attribute of node on the multicast tree, reduced the workload of artificial configuration, avoid and reduced mistake, operability is good.
Figure 12 is the structural representation of an embodiment of intermediate node of multicast tree of the present invention, intermediate node in the present embodiment can be realized the flow process that the present invention is embodiment illustrated in fig. 2, as shown in figure 12, this intermediate node can comprise: receiver module 1201, configuration module 1202 and sending module 1203;
Wherein, receiver module 1201 is used to receive the multicast that the downstream node of this intermediate node sends and joins message, and this multicast joins message and comprises the OAM configuration information, and the downstream node of this intermediate node comprises the upstream node of leaf node and/or this leaf node;
Sending module 1203, be used for multicast joined message and send to the upstream node of this intermediate node, so that the OAM attribute of the configuration of the OAM configuration information during the upstream node of this intermediate node joins message according to this multicast self, and send this multicast and join message, be sent to the root node of multicast tree until hop-by-hop that this multicast is joined message; Particularly, sending module 1203 can join message multicast and periodically send or send to as required the upstream node of this intermediate node.
In the intermediate node of above-mentioned multicast tree, receiver module 1201 receives after multicast that the downstream node of this intermediate node sends joins message, OAM configuration information during configuration module 1202 joins message according to this multicast disposes the OAM attribute of this intermediate node, and sending module 1203 sends this multicast to the upstream node of this intermediate node and joins message; Thereby realized the automatic configuration to the OAM attribute of node on the multicast tree, reduced the workload of artificial configuration, avoided and reduced mistake, operability is good.
Figure 13 is the structural representation of another embodiment of intermediate node of multicast tree of the present invention, compare with the intermediate node of multicast tree shown in Figure 12, difference is, in the intermediate node of multicast tree shown in Figure 13, configuration module 1202 can comprise: fusion treatment submodule 12021 and attribute configuration submodule 12022;
Wherein, attribute configuration submodule 12022, be used for comprising an incoming interface and at least two outgoing interfaces when this intermediate node, and the OAM configuration information that these at least two outgoing interfaces receive is not simultaneously, and the OAM configuration information that receives according at least two outgoing interfaces disposes different OAM attributes at least respectively on above-mentioned two outgoing interfaces;
At this moment, sending module 1203 multicast that specifically is used for comprising the OAM configuration information after fusion treatment submodule 12021 fusion treatment joins message and sends to the upstream node of this intermediate node.
In the present embodiment, fusion treatment submodule 12021 can also be worked as multicast and be joined message and also comprise when other PIM except that above-mentioned OAM configuration information add attributes, and OAM configuration information and other PIM adding attributes except that above-mentioned OAM configuration information are carried out fusion treatment; At this moment, attribute configuration submodule 12022 can also dispose the attribute of this intermediate node according to the result of fusion treatment submodule 12021 fusion treatment.
In the present embodiment, this intermediate node can also comprise: timer is provided with module 1204 and/or attribute removing module 1205;
Wherein, timer is provided with module 1204, is used to be provided with timer; At this moment, configuration module 1202 can also if receive the OAM configuration information of renewal, then reconfigure the OAM attribute of intermediate node according to the OAM configuration information that upgrades in timer is provided with the effective time of the timer that module 1204 is provided with.
Attribute removing module 1205 is used for if do not receive the OAM configuration information of renewal, then deleting the OAM attribute that this intermediate node has disposed after timer is provided with the timer expiry of module 1204 settings.
The intermediate node of above-mentioned multicast tree has been realized the automatic configuration to the OAM attribute of node on the multicast tree, has reduced the workload of artificial configuration, avoids and has reduced mistake, and operability is good.
Figure 14 is the structural representation of an embodiment of root node of multicast tree of the present invention, root node in the present embodiment can be realized the flow process that the present invention is embodiment illustrated in fig. 3, as shown in figure 14, the root node of this multicast tree can comprise: message receiver module 1401 and attribute configuration module 1402;
Wherein, message receiver module 1401 is used to receive the multicast that the downstream node of root node sends and joins message, and this multicast joins message and comprises the OAM configuration information;
In a kind of implementation of present embodiment, attribute configuration module 1402 can comprise: configuration submodule 14021 and processing sub 14022;
Wherein, configuration submodule 14021, be used for comprising an incoming interface and at least two outgoing interfaces when root node, and the OAM configuration information that at least two outgoing interfaces receive is not simultaneously, and the OAM configuration information that receives according at least two outgoing interfaces disposes different OAM attributes at least respectively on above-mentioned two outgoing interfaces;
In the present embodiment, processing sub 14022 can also be worked as multicast and join message and also comprise when other PIM except that the OAM configuration information add attributes, and this OAM configuration information and other PIM adding attributes except that the OAM configuration information are carried out fusion treatment; At this moment, configuration submodule 14021 can also dispose the attribute of this root node according to the result of processing sub 14022 fusion treatment.
In the another kind of implementation of present embodiment, this root node can also comprise: the node timer is provided with module 1403 and/or nodal community removing module 1404;
Wherein, the node timer is provided with module 1403, is used to be provided with timer; At this moment, attribute configuration module 1402 can also if receive the OAM configuration information of renewal, then reconfigure the OAM attribute of this root node according to the OAM configuration information that upgrades in the node timer is provided with the effective time of the timer that module 1403 is provided with.
Nodal community removing module 1404 is used for if do not receive the OAM configuration information of renewal, then deleting the OAM attribute that this root node has disposed after the node timer is provided with the timer expiry of module 1403 settings.
In the root node of above-mentioned multicast tree, message receiver module 1401 receives after multicast joins message, and the OAM configuration information during attribute configuration module 1402 joins message according to this multicast disposes the OAM attribute of this root node; Thereby realized the automatic configuration to the OAM attribute of node on the multicast tree, reduced the workload of artificial configuration, avoided and reduced mistake, operability is good.
Figure 15 is the structural representation of an embodiment of configuration-system of operation management of the present invention and maintenance, and as shown in figure 15, the configuration-system of this operation management and maintenance can comprise: the leaf node 1501 of multicast tree, intermediate node 1502 and root node 1503;
Wherein, leaf node 1501, be used for disposing according to the OAM configuration information that disposes the OAM attribute of this leaf node 1501 on this leaf node, and join message to the upstream node transmission multicast of this leaf node, this multicast joins message and comprises above-mentioned OAM configuration information; Particularly, leaf node 1501 can be realized by the leaf node of the present invention's multicast tree shown in Figure 11;
The operation management that present embodiment provides and the configuration-system of maintenance constitute a multicast tree in logic, for the multicast tree of setting up by the different agreement of PIM protocol suite, the equipment that the root node of multicast tree, intermediate node and leaf node are corresponding different.
For example: for the multicast tree of setting up by PIM-SSM, the root node of this multicast tree can be source Designated Router (the Designated Router that is connected with multicast source; Hereinafter to be referred as: DR), the leaf node of multicast tree can be the recipient DR that is connected with the recipient, and intermediate node can be the router between source DR and the recipient DR.
For the multicast tree of setting up by PIM-SM, this multicast tree comprises three kinds of states: shared tree state, shared tree and source tree coexisting state, and source tree state.In these three kinds of states, when the recipient wishes to add multicast group, set up from recipient DR to Rendezvous Point (Rendezvous Point; Hereinafter to be referred as: shared tree RP); When having flux of multicast to arrive the RP of multicast tree simultaneously, set up source tree simultaneously from RP to source DR; When the flow to the recipient surpasses predetermined threshold value, set up source tree from recipient DR to source DR.At the shared tree state, the root node of multicast tree can be RP, and leaf node can be recipient DR, and intermediate node can be the router between RP and the recipient DR.At shared tree and source tree coexisting state, multicast tree is divided into two sections, and first section is shared tree, and second section is the source tree; Wherein, the root node of first section shared tree is RP, and leaf node is recipient DR, and intermediate node is the router between RP and the recipient DR; The root node of second section source tree is source DR, and leaf node is RP, and intermediate node is the router between source DR and the RP.In the source tree state, the root node of multicast tree is source DR, and leaf node is recipient DR, and intermediate node is the router between source DR and the recipient DR.
The source tree state of setting up for the multicast tree of setting up by PIM-SSM, by PIM-SM or the multicast tree of shared tree state, multicast join message from leaf node to the transmission of root node hop-by-hop, finish the configuration to multicast tree; For the multicast tree of shared tree of setting up by PIM-SM and source tree coexisting state, multicast joins message and is delivered to RP at shared tree from recipient DR hop-by-hop, and tree is delivered to source DR from the RP hop-by-hop in the source, finishes the configuration to source tree and shared tree respectively.
In the configuration-system of above-mentioned operation management and maintenance, the leaf node 1501 of multicast tree disposes according to the OAM configuration information after the OAM attribute of this leaf node, and the multicast that carries this OAM configuration information to the upstream node transmission of this leaf node 1501 joins message; The intermediate node 1502 of multicast tree receives after multicast that the downstream node of this intermediate node 1502 sends joins message, OAM configuration information in joining message according to this multicast disposes the OAM attribute of this intermediate node 1502, sends this multicast to the upstream node of this intermediate node 1502 then and joins message; The root node 1503 of multicast tree receives after multicast joins message, and the OAM configuration information in joining message according to this multicast disposes the OAM attribute of this root node 1503; Thereby realized the automatic configuration to the OAM attribute of node on the multicast tree, reduced the workload of artificial configuration, avoided and reduced mistake, operability is good.
Multicast among Figure 11 of the present invention～embodiment illustrated in fig. 15 joins message and can join message for expansion PIM, certainly the embodiment of the invention is not limited in this, multicast joins message and also can be joining message in any multicast routing protocol, the embodiment of the invention does not limit this, but the embodiment of the invention to join message with this multicast serve as that to join message be that example describes to expansion PIM.
It will be appreciated by those skilled in the art that accompanying drawing is the schematic diagram of a preferred embodiment, module in the accompanying drawing or flow process might not be that enforcement the present invention is necessary.
It will be appreciated by those skilled in the art that the module in the device among the embodiment can be distributed in the device of embodiment according to the embodiment description, also can carry out respective change and be arranged in the one or more devices that are different from present embodiment.The module of the foregoing description can be merged into a module, also can further split into a plurality of submodules.
It should be noted that at last: above embodiment only in order to technical scheme of the present invention to be described, is not intended to limit; Although with reference to previous embodiment the present invention is had been described in detail, those of ordinary skill in the art is to be understood that: it still can be made amendment to the technical scheme that aforementioned each embodiment put down in writing, and perhaps part technical characterictic wherein is equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution break away from the spirit and scope of various embodiments of the present invention technical scheme.
Claims (19)
1. the collocation method of operation management and maintenance is characterized in that, comprising:
The intermediate node of multicast tree receives the multicast that the downstream node of described intermediate node sends and joins message, and described multicast joins message and comprises operation, administers and maintains (OAM) configuration information;
Described intermediate node disposes the OAM attribute of described intermediate node according to described OAM configuration information, and described multicast joined message send to the upstream node of described intermediate node, so that the OAM attribute of the configuration of the OAM configuration information during the upstream node of described intermediate node joins message according to described multicast self, and send described multicast and join message, be sent to the root node of described multicast tree until hop-by-hop that described multicast is joined message.
2. method according to claim 1 is characterized in that, described intermediate node comprises according to the OAM attribute that described OAM configuration information disposes described intermediate node:
Described intermediate node is according to described OAM configuration information configuration OAM attribute on the incoming interface of described intermediate node and/or outgoing interface.
3. according to any described method of claim 1-2, it is characterized in that, described intermediate node comprises an incoming interface and at least two outgoing interfaces, the OAM configuration information that receives when described at least two outgoing interfaces not simultaneously, described intermediate node comprises according to the OAM attribute that described OAM configuration information disposes described intermediate node:
Described intermediate node disposes different OAM attributes at least respectively according to the OAM configuration information that described at least two outgoing interfaces receive on described two outgoing interfaces;
Described intermediate node carries out fusion treatment to the OAM configuration information that described at least two outgoing interfaces receive, if the OAM configuration information that described at least two outgoing interfaces receive can merge, then on the incoming interface of described intermediate node, dispose the OAM attribute according to the OAM configuration information after the fusion treatment;
Described the described multicast upstream node that sends to described intermediate node that joins message is comprised:
Described intermediate node will comprise that the multicast of the OAM configuration information after the described fusion treatment joins message and send to the upstream node of described intermediate node.
4. according to any described method of claim 1-2, it is characterized in that described multicast joins message and comprises that also except that described OAM configuration information other add attributes;
Described method also comprises:
Described intermediate node adds attributes to described OAM configuration information and described except that described OAM configuration information other and carries out fusion treatment, and disposes the attribute of described intermediate node according to the result of fusion treatment.
5. the collocation method of operation management and maintenance is characterized in that, comprising:
The root node of multicast tree receives the multicast that the downstream node of described root node sends and joins message, and described multicast joins message and comprises operation, administers and maintains (OAM) configuration information;
Described root node disposes the OAM attribute of described root node according to described OAM configuration information.
6. method according to claim 5 is characterized in that, described root node comprises according to the OAM attribute that described OAM configuration information disposes described root node:
Described root node is according to described OAM configuration information configuration OAM attribute on the incoming interface of described root node and/or outgoing interface.
7. according to claim 5 or 6 described methods, it is characterized in that, described root node comprises an incoming interface and at least two outgoing interfaces, the OAM configuration information that receives when described at least two outgoing interfaces not simultaneously, described root node comprises according to the OAM attribute that described OAM configuration information disposes described root node:
Described root node disposes different OAM attributes at least respectively according to the OAM configuration information that described at least two outgoing interfaces receive on described two outgoing interfaces;
Described root node carries out fusion treatment to the OAM configuration information that described at least two outgoing interfaces receive, if the OAM configuration information that described at least two outgoing interfaces receive can merge, then on the incoming interface of described root node, dispose the OAM attribute according to the OAM configuration information after the fusion treatment.
8. according to claim 5 or 6 described methods, it is characterized in that described multicast joins message and comprises that also except that described OAM configuration information other add attributes;
Described method also comprises:
Described root node adds attributes to described OAM configuration information and described except that described OAM configuration information other and carries out fusion treatment, and disposes the attribute of described root node according to the result of fusion treatment.
9. the intermediate node of a multicast tree is characterized in that, comprising:
Receiver module is used to receive the multicast that the downstream node of described intermediate node sends and joins message, and described multicast joins message and comprises operation, administers and maintains (OAM) configuration information;
Configuration module is used for disposing according to described OAM configuration information the OAM attribute of described intermediate node;
Sending module, be used for described multicast joined message and send to the upstream node of described intermediate node, so that the OAM attribute of the configuration of the OAM configuration information during the upstream node of described intermediate node joins message according to described multicast self, and send described multicast and join message, be sent to the root node of described multicast tree until hop-by-hop that described multicast is joined message.
10. intermediate node according to claim 9 is characterized in that, described configuration module specifically is used for according to described OAM configuration information configuration OAM attribute on the incoming interface of described intermediate node and/or outgoing interface.
11., it is characterized in that described configuration module comprises according to any described intermediate node of claim 9-10:
The attribute configuration submodule, be used for comprising an incoming interface and at least two outgoing interfaces when described intermediate node, and the OAM configuration information that described at least two outgoing interfaces receive is not simultaneously, and the OAM configuration information that receives according to described at least two outgoing interfaces disposes different OAM attributes at least respectively on described two outgoing interfaces;
The fusion treatment submodule is used for the OAM configuration information that described at least two outgoing interfaces receive is carried out fusion treatment;
Described attribute configuration submodule also is used for disposing the OAM attribute according to the OAM configuration information after the described fusion treatment submodule fusion treatment on the incoming interface of described intermediate node when OAM configuration information that described at least two outgoing interfaces receive can merge.
12. intermediate node according to claim 11 is characterized in that, the multicast that described sending module specifically is used for comprising the OAM configuration information after the described fusion treatment submodule fusion treatment joins message and sends to the upstream node of described intermediate node.
13. intermediate node according to claim 11, it is characterized in that, described fusion treatment submodule also is used for joining message when comprising that also except that described OAM configuration information other add attributes when described multicast, and described OAM configuration information and described other adding attributes except that described OAM configuration information are carried out fusion treatment;
Described attribute configuration submodule also is used for disposing according to the result of described fusion treatment submodule fusion treatment the attribute of described intermediate node.
14. the root node of a multicast tree is characterized in that, comprising:
The message receiver module is used to receive the multicast that the downstream node of described root node sends and joins message, and described multicast joins message and comprises operation, administers and maintains (OAM) configuration information;
The attribute configuration module is used for disposing according to described OAM configuration information the OAM attribute of described root node.
15. root node according to claim 14 is characterized in that, described attribute configuration module specifically is used for according to described OAM configuration information configuration OAM attribute on the incoming interface of described root node and/or outgoing interface.
16., it is characterized in that described attribute configuration module comprises according to claim 14 or 15 described root nodes:
The configuration submodule, be used for comprising an incoming interface and at least two outgoing interfaces when described root node, and the OAM configuration information that described at least two outgoing interfaces receive is not simultaneously, and the OAM configuration information that receives according to described at least two outgoing interfaces disposes different OAM attributes at least respectively on described two outgoing interfaces;
Processing sub is used for the OAM configuration information that described at least two outgoing interfaces receive is carried out fusion treatment;
Described configuration submodule also is used for disposing the OAM attribute according to the OAM configuration information after the described processing sub fusion treatment on the incoming interface of described root node when OAM configuration information that described at least two outgoing interfaces receive can merge.
17. root node according to claim 16, it is characterized in that, described processing sub also is used for joining message when comprising that also except that described OAM configuration information other add attributes when described multicast, and described OAM configuration information and described other adding attributes except that described OAM configuration information are carried out fusion treatment;
Described configuration submodule also is used for disposing according to the result of described processing sub fusion treatment the attribute of described root node.
18. the leaf node of a multicast tree is characterized in that, comprising:
The nodal community configuration module is used for according to the operation of disposing on described leaf node, administers and maintains the OAM attribute that (OAM) configuration information disposes described leaf node;
The message sending module is used for joining message to the upstream node transmission multicast of described leaf node, and described multicast joins message and comprises described OAM configuration information.
19. leaf node according to claim 18 is characterized in that, described nodal community configuration module specifically is used for according to described OAM configuration information configuration OAM attribute on the incoming interface of described leaf node and/or outgoing interface.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010213835.7A CN102299815B (en) | 2010-06-22 | 2010-06-22 | Configuration method and node of OAM (operation, administration and maintenance) |
| PCT/CN2011/073729 WO2011160498A1 (en) | 2010-06-22 | 2011-05-06 | Configuration method and node for operation administration and maintenace |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010213835.7A CN102299815B (en) | 2010-06-22 | 2010-06-22 | Configuration method and node of OAM (operation, administration and maintenance) |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102299815A true CN102299815A (en) | 2011-12-28 |
| CN102299815B CN102299815B (en) | 2014-04-30 |
Family
ID=45360002
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010213835.7A Expired - Fee Related CN102299815B (en) | 2010-06-22 | 2010-06-22 | Configuration method and node of OAM (operation, administration and maintenance) |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102299815B (en) |
| WO (1) | WO2011160498A1 (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102739448A (en) * | 2012-06-28 | 2012-10-17 | 华为技术有限公司 | Method, device and system for transmitting messages |
| CN102868569A (en) * | 2012-06-30 | 2013-01-09 | 华为技术有限公司 | Method, node and system for detecting performance of three-layer virtual private network |
| CN103152205A (en) * | 2013-03-22 | 2013-06-12 | 烽火通信科技股份有限公司 | Stream-index-based operation administration and maintenance (OAM) processing method and device |
| CN103475588A (en) * | 2013-09-10 | 2013-12-25 | 神州数码网络(北京)有限公司 | Sending process method and device and receiving process method and device of OAM messages |
| CN104348678A (en) * | 2013-08-05 | 2015-02-11 | 华为技术有限公司 | Method, device and system for measuring performance of Ethernet |
| CN104429022A (en) * | 2012-07-13 | 2015-03-18 | 瑞典爱立信有限公司 | Connectivity fault management in communication network |
| CN104734876A (en) * | 2013-12-24 | 2015-06-24 | 中兴通讯股份有限公司 | Ethernet OAM configuration achieving method and device |
| CN105323096A (en) * | 2014-07-30 | 2016-02-10 | 中国移动通信集团公司 | Network function operation and maintenance method and operation and maintenance system |
| CN105656705A (en) * | 2014-11-12 | 2016-06-08 | 中兴通讯股份有限公司 | Method and device for detecting multicast function of access equipment |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105827529B (en) | 2016-05-10 | 2019-02-26 | 华为技术有限公司 | A kind of path establishment method and controller |
| CN108536447B (en) * | 2018-04-11 | 2021-07-16 | 上海掌门科技有限公司 | Operation and maintenance management method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101102253A (en) * | 2007-08-13 | 2008-01-09 | 杭州华三通信技术有限公司 | Method, branch node and center node for transmitting multicast in IPsec tunnel |
| CN101212326A (en) * | 2006-12-29 | 2008-07-02 | 上海贝尔阿尔卡特股份有限公司 | Method for configuring nodes in any multicast group and auxiliary method and device |
| CN101651552A (en) * | 2009-09-09 | 2010-02-17 | 华为技术有限公司 | Node configuration method and network equipment |
-
2010
- 2010-06-22 CN CN201010213835.7A patent/CN102299815B/en not_active Expired - Fee Related
-
2011
- 2011-05-06 WO PCT/CN2011/073729 patent/WO2011160498A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101212326A (en) * | 2006-12-29 | 2008-07-02 | 上海贝尔阿尔卡特股份有限公司 | Method for configuring nodes in any multicast group and auxiliary method and device |
| CN101102253A (en) * | 2007-08-13 | 2008-01-09 | 杭州华三通信技术有限公司 | Method, branch node and center node for transmitting multicast in IPsec tunnel |
| CN101651552A (en) * | 2009-09-09 | 2010-02-17 | 华为技术有限公司 | Node configuration method and network equipment |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102739448A (en) * | 2012-06-28 | 2012-10-17 | 华为技术有限公司 | Method, device and system for transmitting messages |
| US9774494B2 (en) | 2012-06-30 | 2017-09-26 | Huawei Technologies Co., Ltd. | Method, node, and system for detecting performance of layer 3 virtual private network |
| CN102868569A (en) * | 2012-06-30 | 2013-01-09 | 华为技术有限公司 | Method, node and system for detecting performance of three-layer virtual private network |
| CN102868569B (en) * | 2012-06-30 | 2015-12-09 | 华为技术有限公司 | The method for testing performance of Layer3 Virtual Private Network, node and system |
| CN104429022A (en) * | 2012-07-13 | 2015-03-18 | 瑞典爱立信有限公司 | Connectivity fault management in communication network |
| CN104429022B (en) * | 2012-07-13 | 2018-10-26 | 瑞典爱立信有限公司 | Connectivity Fault Management in communication network |
| CN103152205A (en) * | 2013-03-22 | 2013-06-12 | 烽火通信科技股份有限公司 | Stream-index-based operation administration and maintenance (OAM) processing method and device |
| CN103152205B (en) * | 2013-03-22 | 2016-02-10 | 烽火通信科技股份有限公司 | Based on OAM processing method and the device of stream index |
| CN104348678A (en) * | 2013-08-05 | 2015-02-11 | 华为技术有限公司 | Method, device and system for measuring performance of Ethernet |
| CN104348678B (en) * | 2013-08-05 | 2018-10-30 | 华为技术有限公司 | Ethernet performance measurement method, apparatus and system |
| CN103475588A (en) * | 2013-09-10 | 2013-12-25 | 神州数码网络(北京)有限公司 | Sending process method and device and receiving process method and device of OAM messages |
| CN104734876A (en) * | 2013-12-24 | 2015-06-24 | 中兴通讯股份有限公司 | Ethernet OAM configuration achieving method and device |
| CN105323096A (en) * | 2014-07-30 | 2016-02-10 | 中国移动通信集团公司 | Network function operation and maintenance method and operation and maintenance system |
| CN105323096B (en) * | 2014-07-30 | 2018-11-23 | 中国移动通信集团公司 | A kind of the O&M method and operational system of network function |
| CN105656705A (en) * | 2014-11-12 | 2016-06-08 | 中兴通讯股份有限公司 | Method and device for detecting multicast function of access equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102299815B (en) | 2014-04-30 |
| WO2011160498A1 (en) | 2011-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102299815B (en) | Configuration method and node of OAM (operation, administration and maintenance) | |
| CN101385275B (en) | Rerouting multicast traffic in response to detecting imminent network disruption | |
| CN105723657B (en) | Switch, controller, system and link quality detection method | |
| US8155028B2 (en) | Method and apparatus for providing full logical connectivity in MPLS networks | |
| CN102316016B (en) | Method and device for forwarding multicasting flow | |
| US8576702B2 (en) | Receiving multicast traffic at non-designated routers | |
| JPWO2007086157A1 (en) | Network system | |
| JP2003258903A (en) | Communication line monitor system | |
| CN100438456C (en) | Hop-by-hop transferred distributed flow media transmission performance test method and device | |
| US8036106B1 (en) | Distributed control packet transmission | |
| CN101227310B (en) | System, apparatus and method for obtaining multicast topology information | |
| CN102195857A (en) | Network topology structure and node information gathering method | |
| WO2018176496A1 (en) | Iptv service quality detection method, device and system | |
| CN110351141B (en) | Flexe interface management method, device and network element | |
| CN104734876A (en) | Ethernet OAM configuration achieving method and device | |
| US7987259B2 (en) | Method and system for providing ad-splicer redundancy in a cable/MSO network | |
| Wang et al. | A multi-domain SDN scalability architecture implementation based on the coordinate controller | |
| CN101909006A (en) | BFD (Bidirectional Forwarding Detection) message sending and receiving methods as well as device and communication system thereof | |
| KR102547701B1 (en) | Network topology discovery method, device, and system | |
| CN102630377B (en) | Method, apparatus and system for processing quality parameters of multicast streams | |
| US8144574B1 (en) | Distributed control packet processing | |
| JP2011188046A (en) | Packet communication system and method for controlling packet communication apparatus | |
| KR20080035388A (en) | Methods and system for checking connectivity of lable swtiched path in gmpls based network | |
| CN116112423A (en) | Path determination method, device and equipment | |
| WO2022121638A1 (en) | Packet processing method and device |
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: 20140430 Termination date: 20190622 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |