CN103609066A - Method and node for querying operation administration maintenance configuration information - Google Patents

Method and node for querying operation administration maintenance configuration information Download PDF

Info

Publication number
CN103609066A
CN103609066A CN201180000326.9A CN201180000326A CN103609066A CN 103609066 A CN103609066 A CN 103609066A CN 201180000326 A CN201180000326 A CN 201180000326A CN 103609066 A CN103609066 A CN 103609066A
Authority
CN
China
Prior art keywords
node
request message
oam
configuration informations
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201180000326.9A
Other languages
Chinese (zh)
Other versions
CN103609066B (en
Inventor
刘晖
郑莲淑
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN103609066A publication Critical patent/CN103609066A/en
Application granted granted Critical
Publication of CN103609066B publication Critical patent/CN103609066B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • H04L41/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • 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
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information

Landscapes

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

Abstract

A method and node for querying Operation Administration Maintenance (OAM) configuration information are provided in the present application. The method includes the steps that: a node acquires a first request message, which contains the type of the OAM configuration information to be queried; the node stores the OAM configuration information which corresponds to the type of the OAM configuration information into the first request message to obtain a second request message; whether the node is a root node is judged; if the node is not a root node, it forwards the second request message to an upper node; if the node is a root node, it generates a response message containing the queried OAM configuration information on the basis of the second request message, and then delivers the response message.

Description

Method and node for querying operation administration maintenance configuration information
Operate, manage, safeguarding method and the node technology field of configuration information inquiry
The present invention relates to data communication field, more particularly to operation, management, maintenance（OAM, Operation Administration Maintenance) configuration information inquiry method and node.
Background technology
Video traffic is one of important service that following Operator Specific Service increases.Operator needs to provide a user the service for meeting user quality demand, improves user satisfaction, increases number of users and avoids customer loss, improves operation management ability.The OAM of multicast network can have found trouble point or the performance bottleneck point of network by active probe or monitoring, before failure generation, can detect the deterioration of network performance, take appropriate measures to avoid the generation of failure；, can quick response, time used in reduction fault location, the corresponding protection mechanism of triggering, it is possible to optimize the utilization of Internet resources after breaking down.
In the prior art, the inquiry of the OAM configuration informations of each node can be by the way of single-point inquiry, it is necessary to which the single inquiry of node one by one, operates numerous Suo, underaction.
The content of the invention
One aspect of the present invention provides the method that OAM configuration informations are inquired about, the inquiry of the OAM configuration informations of each node in multicast tree or multicast forwarding path, numerous Suo operations that single-point is inquired about can effectively be avoided, so that inquiry is convenient and swift, the inquiry of the OAM configuration informations of node on multicast tree or multicast forwarding path can be made more flexible, another aspect of the present invention provides the node that the inquiry of OAM configuration informations can be achieved.
The method of OAM configuration informations inquiry includes：Node obtains the type that the OAM configuration informations that need to be inquired about are included in the first request message, the first request message；OAM configuration informations corresponding with the type of OAM configuration informations in node are saved in the first request message, the second request message is obtained；Whether decision node is root node；If node is not root node, the second request message is forwarded to upper hop node；If node is root node, the response message for including the OAM configuration informations inquired about is generated according to the second request message, the blunt text of response is sent.
The node includes：Acquiring unit, for obtaining in the first request message, the first request message comprising the operation that need to be inquired about, the type for managing, safeguarding OAM configuration informations；Storage unit, for OAM configuration informations corresponding with the type of OAM configuration informations in node to be saved in the first request message, obtains Two request messages；Whether the first judging unit, be root node for decision node；Retransmission unit, for when node is not root node, forwarding the second request message to upper hop node；Response message unit, for when node being root node, the response message for including the OAM configuration informations inquired about being generated according to the second request message, response message is sent.
As can be seen from the above technical solutions, many aspects of the invention have advantages below：
Pass through the request message according to the type comprising the OAM configuration informations that need to be inquired about, OAM configuration informations corresponding with type in node are saved in request message, during so that request message being forwarded in multicast tree or multicast forwarding path, the OAM configuration informations of reached node can be inquired, avoid numerous Suo of single-point inquiry mode, improve the efficiency of OAM configuration informations inquiry, it is adaptable to the inquiry of the OAM configuration informations of the node in multicast tree or multicast forwarding path.
Brief description of the drawings
Fig. 1 is multicast tree OAM entity relationship schematic diagrames of the embodiment of the present invention；
Fig. 2 is a schematic diagram of the method for OAM configuration informations inquiry in the embodiment of the present invention；Fig. 3 is another schematic diagram of the method for OAM configuration informations inquiry in the embodiment of the present invention；Fig. 4 is a schematic diagram of interior joint of the embodiment of the present invention；
Fig. 5 is another schematic diagram of interior joint of the embodiment of the present invention.
Embodiment
The embodiments of the invention provide the method for OAM configuration informations inquiry and node, OAM configuration informations for inquiring about each node on multicast tree or multicast forwarding path, it is to avoid numerous Suo of single-point inquiry mode improve efficiency and the flexibility of inquiry.
The technical scheme of embodiment, will introduce multicast tree OAM entity relationships in the embodiment of the present invention, refers to Fig. 1 for a better understanding of the present invention, be the OAM entity relationship schematic diagrames in the embodiment of the present invention, wherein, Maintenance Entity end points incoming interface（MEP-I, Maintenance Entity Group End Point Ingress) entity, Maintenance Entity end points outgoing interface（MEP-E, Maintenance Entity Group End Point Egress) entity, Maintenance Entity intermediate point（MIP, Maintenance Entity Group Intermediate Point) entity is 3 kinds of OAM entities, and MEP-I, MEP-E, MIP are logic entity, are configurable on network element（NE, Net Element) interface（Incoming interface and/or outgoing interface) on, and Element management system（EMS, Element Maintenance System) specific OAM configuration informations can be configured on these logic entities. In embodiments of the present invention, signified node is network element（NE, Net Element) or other equipment, in actual applications, the routing direction of OAM message refers to the direction of arrow in Fig. 1.
In embodiments of the present invention, when setting MEP-I entities on the interface of node, then the interface of MEP-I entities can be set to initiate OAM operations from the node, for example when Jin Hang Lost bags are measured, the node will be counted to multicast traffic stream, and by count value write-in with the Lost bag measured messages that Lost bags are detected, and send the Lost bag measured messages；When being provided with MEP-E entities on the interface of node, the node set MEP-E entities interface can terminate OAM operation, for example carry out latency measurement when, node will obtain time stamp from the latency measurement message received, calculation delay, completes latency measurement；When setting MIP entities on the interface of node, the interface of the setting MIP entities of the node will be used to E-Packet, or carry out transparent transmission to OAM texts.
Referring to Fig. 2, a schematic diagram of the method inquired about for OAM of embodiment of the present invention configuration informations, including：
201st, node obtains the first request message；
When network manager or operating personnel need the OAM configuration informations of each node in multicast tree or multicast forwarding path, node on path to be checked will get the request message inquired about for OAM configuration informations, wherein, the type for the OAM configuration informations that need to be inquired about is included in request message.In embodiments of the present invention, node obtains the type that the OAM configuration informations that need to be inquired about are included in the first request message, first request message.
202nd, OAM configuration informations corresponding with the type of OAM configuration informations in node are saved in the first request message, obtain the second request message；
It should be noted that, in embodiments of the present invention, the request message that node is got can be described as the first request message of the node, the request message for saving the OAM configuration informations of the node can be described as the second request message of the node, and it is to preferably distinguish the two states of the request message in node to describe request message using first and second.
OAM configuration informations corresponding with the type of the OAM configuration informations of the need inquiry included in the first request message in node are saved in the first request message by node, obtain the second request message of the OAM configuration informations comprising the node.
In embodiments of the present invention, the content included according to OAM configuration informations can be classified OAM configuration informations, the types of OAM configuration informations may include it is following any one：OAM entity configurations, The configured part attribute status of OAM entities, the configured all properties state of OAM entities, OAM entity configurations and routing state information, the configured part attribute status of OAM entities and routing state information, the configured all properties state of OAM entities and routing state information.
In embodiments of the present invention, OAM configuration informations can include OAM entity configurations, OAM entity attributes and OAM entity attribute states etc..
In embodiments of the present invention, the type of OAM configuration informations that can be in request message obtains corresponding OAM configuration informations, for example：
When inquiring about OAM entity configurations, then the OAM entity configurations on node outgoing interface and incoming interface are obtained；
When inquiring about the configured part attribute status of OAM entities, then configured certain of OAM entities on node or certain several OAM entity attribute and corresponding OAM entity attributes state are obtained；
When the configured all properties state of inquiry OAM entities, then the physically configured all OAM entity attributes of node OAM and corresponding OAM entity attributes state are obtained；
When inquiring about OAM entity configurations and routing state information, then node outgoing interface and OAM entity configurations and the routing state information of node on incoming interface are obtained；
When inquiring about the configured part attribute status of OAM entities and routing state information, then obtain configured certain of OAM entities on node or certain several OAM entity attribute and corresponding OAM entity attributes state, and node routing state information；
When inquiring about the configured all properties state of OAM entities and routing state information, then obtain the physically configured all OAM entity attributes of node OAM and corresponding OAM entity attributes state, and node routing state information.
Wherein, OAM entity configurations refer to the type of the OAM entities configured on the incoming interface or outgoing interface of node, for example, MEP-I entities, or MEP-E entities or MIP entities；
OAM entity attributes refer to the OAM attributes physically configured in the OAM of node, and OAM attributes can include the measurement of Lost bags, delay measurements, measurement of handling up, loopback, detection of connectivity, alarm instruction, pretection switch etc. to wrap；
OAM entity attribute states refer to the existence in the OAM OAM entity attributes physically configured, it can include enabling, go to enable, obstruction etc., for example, the OAM entity attribute Wei Lost bags measurement that some interface of node is set, when node is from the interface Dao Lost bag measured messages, if OAM entities belong to Character state is enables, and node is by the normal process Lost bag measured messages；If when OAM entity attributes state is goes to enable, node is by the transparent transmission Lost bag measured messages；If OAM entity attributes state is obstruction, node, which will suspend, handles the Lost bag measured messages, while stopping Fa Song Lost bag measured messages to downstream node；
Routing state information includes incoming interface address, outgoing interface address, the Routing Protocol of operation, incoming interface is transferred to message amount, and outgoing interface produces message amount etc..
203rd, whether decision node is root node, if not root node, then perform step 204, if root node, then performs step 205;
In embodiments of the present invention, node will determine that whether this node is root node.
It should be noted that, in embodiments of the present invention, node judges whether this node is that the mode of root node has a variety of, for example, node can judge whether this node is the multicast tree of inquiry or the root node of multicast forwarding path by the multicast routing protocol of operation, when multicast tree is source tree, node can judge whether this node is root node according to the multicast tree or the source address of multicast forwarding path included in the request message received, in actual applications, can determine according to specific circumstances node judge this node whether be root node mode, do not limit herein.
204th, the second request message is forwarded to upper hop node；
When node is not root node, node will forward the second request message to upper hop node（Previous hop), wherein, upper hop node refers to along multicast tree or multicast forwarding path, and with OAM message send opposite direction on, be connected with this node from root node closer to node.
205th, the response message for including the OAM configuration informations inquired about is generated according to the second request message, the blunt text of response is sent.
When node is root node, root node will generate the response message of the OAM configuration informations comprising each node in the multicast tree or multicast forwarding path inquired about according to the second request message, send the response message of generation.
In embodiments of the present invention, each node in multicast tree or multicast forwarding path is by the way that this node OAM configuration informations corresponding with the OAM configuration information types in the request message got are saved in request message, and forward the request message for the OAM configuration informations for saving this node, and after request message reaches root node, root node generates and sends response message, network manager or operating personnel are enabled effectively to get the OAM configuration informations of each node on multicast tree or multicast forwarding path, avoid numerous Suo operations of single-point inquiry, improve the efficiency of OAM configuration informations inquiry. It should be noted that being used for the message of OAM configuration queryings in embodiments of the present invention（Such as query message, request message or response message）It can be the message of the Mtrace after extending, it can also be the message under the agreement for realizing the inquiry of OAM configuration informations newly defined, in actual applications, the inquiry using the message of the Mtrace after extension or the protocol realization OAM configuration informations of the OAM configuration informations inquiry newly defined can be determined as needed, do not limited herein.
In following inventive embodiments, in order to be better understood from technology, the technical scheme of the embodiment of the present invention will be described by taking the inquiry that the message of the Mtrace after using extension realizes OAM configuration informations as an example, refer to Fig. 3, another schematic diagram for the method inquired about for OAM configuration informations in the embodiment of the present invention, including：301st, node obtains the first request message；
In embodiments of the present invention, there are two kinds of situations in multicast tree to be checked or the approach of node the first request message of acquisition on multicast forwarding path：Receive the first request message of the Mtrace after the extension of downstream node transmission, or the first request message of the Mtrace after extension is generated according to the query message of the Mtrace after the extension received, wherein, the type of OAM configuration informations and the response data block for preserving OAM configuration informations need to be inquired about by being included in the first request message.
Mtrace is the common tool that route exploration is carried out to multicast network, the routing state information for inquiring about built multicast tree each node from some leaf node to the multicast forwarding path of some root node, and Mtrace operation principle is：Arbitrary node in multicast tree or outside multicast tree to the leaf node on multicast forwarding path to be checked by sending query message, query message is reached after leaf node, leaf node will generate Mtrace request message, and the routing state information of the leaf node is saved in the corresponding response data block of request message, and the request message for the routing state information for saving leaf node is forwarded to upper hop node, the routing state information of this node is being saved in the request message received after corresponding response data block by upper hop node, upper hop node continues to forward the request message for the routing state information for having preserved this node, it will be stopped forwarding after request message reaches the root node of multicast forwarding path, and the routing state information of each node reached on multicast forwarding path is included in the request message on root node.Existing Mtrace also supports the exception handling when the route exploration failure of node, for example, when the OAM configuration statuses and routing state of node, which collect processing, occurs abnormal, the transmission of interrupt requests message upstream nodes is sent response message by node to the node where response address in advance.
In embodiments of the present invention, by using the Mtrace after extension, i.e., increase the field inquired about for OAM configuration informations in Mtrace message, realize the inquiry of OAM configuration informations on multicast forwarding path, Therefore, when network manager or operating personnel need to inquire about the OAM configuration informations of multicast tree or multicast forwarding path, leaf node in multicast tree to be checked or multicast forwarding path will receive the inquiry text of the Mtrace after extension, and leaf node will generate the request message of the type comprising the OAM configuration informations that need to be inquired about according to inquiry text.
For the Mtrace messages being better understood from after extension, refer to following table, the Mtrace messages after extension to be：
Group address
Source address
Destination address
Response address
Respond the type that TTL inquires about ID OAM configuration informations
MEG ID
L D reserved fields
Response data block
The message content of Mtrace after extension can use the structure of type-length-value, type refers to the particular type of message, the type of Mtrace messages can be query message, or request message, or response message, length refers to the length of message codomain, value then includes the public head and response data block of Mtrace messages, wherein, public head includes type, the length of message, hop count and group address, source address, destination address, response address, response TTL, inquiry identity（ID, Identity), the type of OAM configuration informations, Maintenance Entity identity (MEG-ID, Maintenance Entity Group Identity) etc., hop count refers to the maximum hop count that message can be inquired about, group address refers to the multicast tree of inquiry or the group address of multicast forwarding path, source address refers to multicast tree or the source address of multicast forwarding path, destination address refers to the address of multicast receivers, response address is the address of node for responding and being sent to needed for blunt text, respond life span (TTL, Time To Live) refer to the maximum hop count that response message is sent, inquiry ID refers to the ID of mark this time inquiry, the type of OAM configuration informations refers to the type of the OAM configuration informations of needs inquiry, MEG-ID refers to a mark for identifying the maintenance group of the group object, and the mark is unique in domain maintenance management, it should be noted that, forwarding code can also be included in message, code is forwarded to be used for the state of routing state information inquiry of identification request message place node, the routing state information of node is understood according to the value of forwarding code Whether inquiry breaks down.
In embodiments of the present invention, the form for being used to preserve the response data block of OAM configuration informations in Mtrace after extension is relevant with the specific type for the OAM configuration informations that needs are inquired about, different types correspond to the form of different response data blocks, wherein, the type of OAM configuration informations includes but is not limited to：OAM entity configurations, the configured part attribute status of OAM entities, the configured all properties state of OAM entities, OAM entity configurations and routing state information, the configured part attribute status of OAM entities and routing state information, the configured all properties state of OAM entities and routing state information.
302nd, OAM configuration informations corresponding with the type of OAM configuration informations in node are packaged；In embodiments of the present invention, OAM configuration informations corresponding with the type in node are packaged by node by the type for the OAM configuration informations inquired about according to the need included in the first request message.It can be specifically the first request message that node parsing is received, obtain OAM configuration informations corresponding with the type of the OAM configuration informations in the first request message, and the OAM configuration informations are packaged into the preservable form of response data block in the first request message so that the OAM configuration informations can be stored in the first request message.
It should be noted that in embodiments of the present invention, before step 302 is performed, node also will determine that whether the inquiry of OAM configuration information of the request message on node breaks down, wherein, the situation of failure includes but is not limited to：Node does not support OAM configuration informations to inquire about, and either node routing information mistake or node, which are managed, forbids upper hop node to forward request message.In embodiments of the present invention, if node judges that the first request message breaks down in the inquiry of the OAM configuration informations of this node, response message will be generated according to the first request message, the response message of generation is sent to the node corresponding to the response address included in response message, wherein, the OAM configuration informations for each node inquired about are included in response message, if node judges that the inquiry of OAM configuration information of first request message on this node is not broken down, the content that will be continued executing with step 302.
303rd, the information after encapsulation is stored in the response data block of the first request message, obtains the second request message；
After being packaged to information, the information after encapsulation is stored in the response data block of the first request message by node, obtains the second request message.It should be noted that for the type of different OAM configuration informations, the form and length of the response data block included in the first request message may also be differed.
In order to be better understood from technology, by the response to the type for preserving different OAM configuration informations The form of data block is introduced respectively.
If network manager or operating personnel need to inquire about the OAM entity configurations of each node on multicast tree or multicast forwarding path, inquire about the type of the OAM entities configured on the outgoing interface and incoming interface of each node, the response data block that being used in request message preserves OAM entity configuration information can be comprising inquiry arrival time, incoming interface address, outgoing interface address, incoming interface configuration entity, outgoing interface configuration entity, answer code etc., the form of the response data block may be referred to following table：
Inquire about arrival time
Incoming interface address
Outgoing interface address
Incoming interface configuration entity outgoing interface configuration entity answer code
In upper table, inquiry arrival time refers to that request message reaches the time of node；Incoming interface address/outgoing interface address refers to incoming interface address/outgoing interface address of the route for multicast forwarding list item of this node；Incoming interface configuration entity/outgoing interface configuration entity refers to the OAM entities configured on entry/exit interface, and length refers to the length of the response data block.Wherein, the state of the OAM configuration informations inquiry of node where answer code is used for identification request message, for example, the state of inquiry can be normal, either interface error or fatal error etc..It is preferred that, it is similar due to forwarding code to be defined with the form of the Mtrace answer codes defined, same set of coding can be only used when in use, or defines distinctive answer code.
If the part attribute status configured to OAM entities is inquired about, physically configured certain of each node OAM or certain several OAM entity attribute and corresponding OAM entity attributes state are inquired about, then the form for the response data block for being used to preserving OAM entity attributes in request message refers to following table：
Inquire about arrival time
Incoming interface address
Outgoing interface address
Incoming interface configuration entity outgoing interface configuration entity answer code
L D reserved fields
1st effective sub- TLV of attribute status
The 2nd sub- TLV of effective sub- n-th effective attribute status of TLV of attribute status L D reserved fields
1st effective sub- TLV of attribute status
The 2nd sub- TLV of effective sub- n-th effective attribute status of TLV of attribute status
In embodiments of the present invention, OAM entity attributes refer to the OAM attributes that the OAM of node is physically configured, therefore the corresponding response data block format of OAM entity attributes includes the form and the form of attribute status block of the above-mentioned corresponding response data block of OAM entity configuration information, when the interface of node is configured with OAM entities, the response data block in Mtrace messages after extension can include attribute status block.
Attribute status block includes attribute identification field and attribute status subtype length value (TLV, Type
Length Value) field, attribute identification field is used to show whether the OAM attributes belonging to the field to need inquiry, if attribute identification field is 1, then support the inquiry of corresponding attribute, if attribute-bit is 0, the inquiry of corresponding attribute is not supported then, it refer to upper table, wherein L and D field are attribute identification field, L Wei Lost bags measurement mark, show that request message will inquire about Lost bags Shang multicast forwarding tree or multicast forwarding path and measure OAM configuration attribute states when the value of the field is 1, D identifies for delay measurements, show the delay measurements OAM configuration attribute states that request message will be inquired about on multicast tree or multicast forwarding path when the value of the field is 1.Behind attribute identification field according to field in all effective attributes（I.e. corresponding attribute identification field is set to 1 attribute）Order include the state subgroup TLV of all effective attributes, as sub- TLV fields of attribute status, it is preferred that, when the value of attribute identification field is 0, though illustrate to be configured with OAM entities on the interface of node, but any OAM attributes are not supported, and attribute status block can not include the sub- TLV fields of attribute status.
It should be noted that the reserved field included in response data block for preserving OAM entity attributes can be used for the setting of other types of flag bit, and the value that reserved field is set before being not used is 0.
It should be noted that, in embodiments of the present invention, the form that each effective sub- TLV of attribute status in the sub- TLV fields of attribute status can be worth using the length one of type one, type is used to distinguish different OAM entity attributes, length is the length of sub- TLV value, it is worth for corresponding OAM entity attributes state, the content that the type of different attribute state is included in attribute status field can also be different, do not limit herein.
The configured all OAM entity attributes of OAM entities inquired about on each node if the configured all properties state of the OAM entities of query node and corresponding OAM entity attributes state, then for preserving The form of the response data block of the configured all properties state of OAM entities refers to be previously used for preserving the form of the response data block of the configured part attribute status of OAM entities.
If desired OAM entity configurations of query node and during routing state information, then the form that the response data block for being used for the OAM entity configurations and routing state information for preserving node is included in request message is referred to down：
Inquire about arrival time
Incoming interface address
Outgoing interface address
Incoming interface entity configuration outgoing interface entity configuration answer code
Incoming interface incoming message quantity
Outgoing interface outgoing message quantity
This source-group to message total
Mask forwarding code in Routing Protocol forwarding TLV MBZ S sources in embodiments of the present invention, is used for the response data block for preserving routing state information for preserving the response data block of OAM entity configurations and routing state information and including in the response data block and Mtrace that are used for preserving OAM entity configurations.
It should be noted that, in embodiments of the present invention, if desired the configured part attribute status of the OAM entities of query node and during routing state information, then the response data block of the OAM configuration informations in request message for preserving the type can be used for the field for preserving routing state information in the upper increase for being used to preserve the response data block of the configured part attribute status of OAM entities introduced, similar, if desired the configured all properties state of the OAM entities of query node and during routing state information, then in request message for the response data block of the OAM configuration informations of the type form can be introduced for preserve the configured all properties state of OAM entities response data block on increase the field for preserving routing state information, here is omitted for the specific form of response data block.
It should be noted that the form of above-mentioned all response data blocks can not limited as parameter format, in actual applications according to being configured to the content and form of response data block the need for specific herein.
It should be noted that in embodiments of the present invention can also realizing the inquiries of OAM configuration informations by way of defining the vlan query protocol VLAN of new OAM configuration informations, in actual applications, can determine as needed be The inquiry for the protocol realization OAM configuration informations inquired about using the OAM configuration informations still newly defined of the Mtrace after extension, is not limited herein.
304th, whether decision node is root node, if node is not root node, performs step 305, if node is root node, performs step 306;
In embodiments of the present invention, after request message reaches node, node will determine that whether this node is root node.
305th, the second request message is forwarded to upper hop node；
When the node for getting request message is not root node, node will forward the request message to upper hop node.It should be noted that upper hop node is after the request message of forwarding is received, the method that upper hop node will also perform description of the embodiment of the present invention.
306th, the response message for including the OAM configuration informations inquired about is generated according to the second request message；When request message has reached root node, root node will generate according to request message and include what is inquired about
The blunt text of response of OAM configuration informations.
The 307th, the response message of generation is sent to the node corresponding to the response address included in response message.After response message generation, the response message of generation is sent to the node corresponding to the response address included in response message by root node, wherein, the node corresponding to response address is transmission query message to the node in the multicast tree of leaf node or outside multicast tree.
In embodiments of the present invention, by using the request message in the Mtrace of extension, forwarded between upper each node of multicast tree or multicast forwarding path to be checked, node receives after request message and the corresponding OAM configuration informations of this node is saved in request message, after request message reaches root node, root node will terminate the inquiry operation of OAM configuration informations, and the node corresponding to the response message generated according to request message is sent into response address, due to including the OAM configuration informations of each node in multicast tree or multicast forwarding path in response message, network manager or operating personnel can effectively get the OAM configuration informations of each node on multicast tree or multicast forwarding path, avoid numerous Suo of single-point inquiry, underaction, improve the efficiency of OAM configuration informations inquiry, suitable for the inquiry of multicast tree and the OAM configuration informations of multicast forwarding path.
Referring to Fig. 4, be a schematic diagram of interior joint of the embodiment of the present invention, including：
Acquiring unit 401, for obtaining in the first request message, the first request message comprising the operation that need to be inquired about, the type for managing, safeguarding OAM configuration informations； Storage unit 402, for OAM configuration informations corresponding with the type of OAM configuration informations in node to be saved in the first request message, obtains the second request message；
Whether the first judging unit 403, be root node for decision node；
Retransmission unit 404, for when node is not root node, forwarding the second request message to upper hop node；
Response message unit 405, for when node is root node, the blunt text of response for including the OAM configuration informations inquired about to be generated according to the second request message, sends the blunt text of response.
In embodiments of the present invention, the acquiring unit 401 of node is got after the first request message, OAM configuration informations corresponding with the type of the OAM configuration informations in the first request message in node are saved in the first request message by storage unit 402, obtain the second request message, then, first judging unit 403 will determine that whether this node is root node, when this node is not root node, retransmission unit 404 will forward the second request message to upper hop node, when this node is root node, response message unit 405 will generate the response message for including the OAM configuration informations inquired about according to the second request message, and send response message.
In order to be better understood from the technology of the present invention, referring to Fig. 5, be another schematic diagram of interior joint of the embodiment of the present invention, including：
The acquiring unit 401 of embodiment description as shown in Figure 4, storage unit 402, the first judging unit 403, retransmission unit 404, response message unit 405, and it is similar to the content of the embodiment description shown in Fig. 4, here is omitted.
Wherein, acquiring unit 401 includes：
First receiving unit 501, the query message for receiving the Mtrace after extension；
The response data block for being used for preserving OAM configuration informations is also included in request message generation unit 502, the first request message for generating the Mtrace after extension according to the query message of the Mtrace after extension, the first request message；
Or,
Second receiving unit 503, the first request message for receiving the Mtrace after extension.
And in embodiments of the present invention, the node can also include：
Second judging unit 504, for judging whether the inquiry of OAM configuration information of first request message on node breaks down；
Exception processing unit 505, for when OAM configuration information of first request message on the node Inquiry when breaking down, then response message is generated according to request message, sends response message, the OAM configuration informations inquired about are included in response message.
In embodiments of the present invention, when the OAM configuration informations for each node for needing to inquire about on multicast tree or multicast forwarding path, first receiving unit 501 of the leaf node in corresponding multicast tree or multicast forwarding path will receive the query message of the Mtrace after extension, generate the request message of the type comprising the OAM configuration informations that need to be inquired about according to the query message of the Mtrace after extension by request message generation unit 502 again, then, second judging unit 504 judges whether the inquiry of OAM configuration information of the request message of the Mtrace after extension on node breaks down, when the inquiry of OAM configuration informations is broken down, exception processing unit 505 will stop forwarding request message, send the response message generated according to request message.When the inquiry of the OAM configuration informations of request message is not broken down, the storage unit 402 of node is according to the types of the OAM configuration informations included in request message, corresponding OAM configuration informations in node are saved in request message, and whether be that root node judges to node by the first judging unit 403, because the node is not root node, retransmission unit 404 will forward request message to upper hop node, second receiving unit 503 of upper hop node will receive request message, whether the inquiry for judging the OAM configuration informations of request message on this node by the second judging unit 504 of upper hop node again breaks down, if the inquiry of the OAM configuration informations of request message is broken down, request message is stopped forwarding by the exception processing unit 505 of the node, send the response message generated according to request message.When the inquiry of the OAM configuration informations of request message is not broken down, storage unit 402 is according to the types of the OAM configuration informations included in request message, corresponding OAM configuration informations in node are saved in request message, whether the first judging unit 403 of upper hop node is that root node judges to node, when upper hop node is not root node, retransmission unit 404 will continue to forward request message, when upper hop node is root node, response message generation unit 405 in root node will generate the response message for including OAM configuration informations according to request message, and the node corresponding to as response unit 506 response message of generation being sent into the response address included in response message.
It should be noted that the embodiment of the method shown in Fig. 2 and Fig. 3 can be realized using the device embodiment shown in Fig. 4 or Fig. 5.
In embodiments of the present invention, forwarded by using for the request message hop-by-hop that OAM configuration informations are inquired about in multicast tree or multicast forwarding path, after node receives request message, OAM configuration informations corresponding with the type of OAM configuration informations in this node are saved in request message, and forwarded Save the request message of the OAM configuration informations of this node, until when reaching root node or inquiry failure, node will generate response message according to request message, and send response message, so that the inquiry operation simple and flexible of OAM configuration informations, it is adaptable to the inquiry to the OAM configuration informations of whole multicast tree node.
One of ordinary skill in the art will appreciate that realizing that all or part of step in above-described embodiment method can be by program to instruct the hardware of correlation to complete, described program can be stored in a kind of computer-readable recording medium, storage medium mentioned above can be read-only storage, disk or CD etc..
The method and node inquired about above OAM configuration informations provided by the present invention are described in detail, for those of ordinary skill in the art, thought according to the embodiment of the present invention, it will change in specific embodiments and applications, in summary, this specification content should not be construed as limiting the invention.

Claims (10)

  1. Claim
    1st, a kind of method operate, manage, safeguarding the inquiry of 0AM configuration informations, it is characterised in that including：
    Node obtains the type that the OAM configuration informations that need to be inquired about are included in the first request message, first request message；
    OAM configuration informations corresponding with the type of the OAM configuration informations in the node are saved in first request message, the second request message is obtained；
    Whether judge the node is root node；
    If the node is not root node, second request message is forwarded to upper hop node；If the node is root node, the response message for including the OAM configuration informations inquired about is generated according to second request message, the response message is sent.
    2nd, according to the method described in claim 1, it is characterised in that
    The type of the OAM configuration informations include it is following any one：OAM entity configurations, the configured part attribute status of OAM entities, the configured all properties state of OAM entities, OAM entity configurations and routing state information, the configured part attribute status of OAM entities and routing state information, the configured all properties state of OAM entities and routing state information.
    3rd, method according to claim 1 or 2, it is characterised in that the node, which obtains the first request message, to be included：
    Node receives the blunt text of inquiry of the Mtrace after extension；
    The response data block for also being included in the first request message of the Mtrace after extension, first request message and being used for preserving the OAM configuration informations is generated according to the query message of the Mtrace after the extension；Or,
    Node receives the response data block for also being included in the first request message of the Mtrace after the extension, first request message and being used for preserving the OAM configuration informations.
    4th, the method according to claim any one of 1-3, it is characterised in that described that OAM configuration informations corresponding with the type of the OAM configuration informations in the node are saved in first request message, obtaining the second request message includes：
    OAM configuration informations corresponding with the type of the OAM configuration informations in the node are packaged； In the response data block that information after encapsulation is stored in first request message, the blunt text of second request is obtained.
    5th, the method according to claim any one of 1-4, it is characterised in that the node also includes after obtaining request message：
    Judge whether the inquiry of OAM configuration information of first request message on the node breaks down；
    If breaking down, response message is generated according to first request message, sent in the response message, the response message comprising the OAM configuration informations inquired about；
    If not breaking down, continue executing with it is described OAM configuration informations corresponding with the type of the OAM configuration informations in the node are saved in first request message, the step of obtaining the second request message.
    6th, the method according to claim any one of 1-5, it is characterised in that the transmission response message includes：
    The response message of generation is sent to the node corresponding to the response address included in the response message.
    7th, a kind of node, it is characterised in that including：
    Acquiring unit, for obtaining in the first request message, first request message comprising the operation that need to be inquired about, the type for managing, safeguarding OAM configuration informations；
    Storage unit, for OAM configuration informations corresponding with the type of the OAM configuration informations in the node to be saved in first request message, obtains the second request message；
    First judging unit, for judging whether the node is root node；
    Retransmission unit, for when the node is not root node, forwarding second request message to upper hop node；
    Response message unit, for when the node is root node, the blunt text of response for including the OAM configuration informations inquired about to be generated according to second request message, sends the blunt text of response.
    8th, node according to claim 7, it is characterised in that the acquiring unit includes：First receiving unit, the query message for receiving the Mtrace after extension；
    Also being included in request message generation unit, the first request message for generating the Mtrace after extension according to the query message of the Mtrace after the extension, first request message is used to preserve the OAM The response data block of configuration information.
    9th, node according to claim 8, it is characterised in that the acquiring unit also includes：The response data block for being used for preserving the OAM configuration informations is also included in second receiving unit, the first request message for receiving the Mtrace after the extension, first request message.
    10th, the node according to claim any one of 7-9, it is characterised in that the node also includes：Second judging unit, for judging whether the inquiry of OAM configuration information of first request message on the node breaks down；
    Exception processing unit, when inquiry for the OAM configuration informations when first request message on the node is broken down, response message is then generated according to the request message, sent in the response message, the response message comprising the OAM configuration informations inquired about.
CN201180000326.9A 2011-04-28 2011-04-28 Method and node for querying operation administration maintenance configuration information Expired - Fee Related CN103609066B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/073433 WO2012145903A1 (en) 2011-04-28 2011-04-28 Method and node for querying operation administration maintenance configuration information

Publications (2)

Publication Number Publication Date
CN103609066A true CN103609066A (en) 2014-02-26
CN103609066B CN103609066B (en) 2017-04-26

Family

ID=47071558

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201180000326.9A Expired - Fee Related CN103609066B (en) 2011-04-28 2011-04-28 Method and node for querying operation administration maintenance configuration information

Country Status (2)

Country Link
CN (1) CN103609066B (en)
WO (1) WO2012145903A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11177976B2 (en) 2017-05-18 2021-11-16 Xi'an Zhongxing New Software Co., Ltd. Method and device for automatically implementing IOAM encapsulation and storage medium

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108964943B (en) * 2017-05-18 2022-01-28 中兴通讯股份有限公司 Method and device for realizing IOAM packaging

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159688A (en) * 2007-11-08 2008-04-09 华为技术有限公司 Multicast routing track method and router
CN101741592A (en) * 2008-11-13 2010-06-16 华为技术有限公司 Method, device and system for managing GPON branch in multi-service transmitting network
CN101789900A (en) * 2009-11-19 2010-07-28 福建星网锐捷网络有限公司 Multicast forwarding route query method, intermediate node and management node
CN101904184A (en) * 2007-10-12 2010-12-01 北方电讯网络有限公司 Automatic mep provisioning in a link state controlled Ethernet network
CN101980473A (en) * 2010-10-09 2011-02-23 中兴通讯股份有限公司 Multicast path tracking method and system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101904184A (en) * 2007-10-12 2010-12-01 北方电讯网络有限公司 Automatic mep provisioning in a link state controlled Ethernet network
CN101159688A (en) * 2007-11-08 2008-04-09 华为技术有限公司 Multicast routing track method and router
CN101741592A (en) * 2008-11-13 2010-06-16 华为技术有限公司 Method, device and system for managing GPON branch in multi-service transmitting network
CN101789900A (en) * 2009-11-19 2010-07-28 福建星网锐捷网络有限公司 Multicast forwarding route query method, intermediate node and management node
CN101980473A (en) * 2010-10-09 2011-02-23 中兴通讯股份有限公司 Multicast path tracking method and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
杨敏等: "基于Mtrace的Ipv6组播监听的实现", 《现代电子技术》 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11177976B2 (en) 2017-05-18 2021-11-16 Xi'an Zhongxing New Software Co., Ltd. Method and device for automatically implementing IOAM encapsulation and storage medium

Also Published As

Publication number Publication date
CN103609066B (en) 2017-04-26
WO2012145903A1 (en) 2012-11-01

Similar Documents

Publication Publication Date Title
KR102569305B1 (en) Data message detection method, device and system
CN100454853C (en) Method for service channel detection and system for providing the same
JP4840236B2 (en) Network system and node device
JP5462954B2 (en) Packet loss detection method and apparatus, and router
US7660236B2 (en) System and method of multi-nodal APS control protocol signaling
WO2013046496A1 (en) Communication system, sending device, communication device, failure notification method and non-temporary computer-readable medium storing program
WO2018210213A1 (en) Method and device for implementing ioam packaging and storage medium
US20090282291A1 (en) Internal maintenance association end point (mep) for sharing state information
CN101815006B (en) aggregation control method of links passing through provider network and system
CN1514585A (en) Method used for detecting conncetion failure, system and network entity
WO2014019348A1 (en) Method, device and system for operation, management and maintenance of oam configuration
CN105281931A (en) Error code detection method, device and system of POTN
CN102195822A (en) Fault detection method and business provider edge (PE) equipment
CN102868569A (en) Method, node and system for detecting performance of three-layer virtual private network
WO2016062165A1 (en) Method and apparatus for implementing operations, administration and maintenance function
JP4861293B2 (en) COMMUNICATION DEVICE, COMMUNICATION METHOD, AND COMMUNICATION PROGRAM
WO2011137807A1 (en) Monitoring method for ip bearing network based on service and device for monitoring quality of ip service
CN108259442B (en) Slow protocol message processing method and related device
KR101566139B1 (en) Pseudowire extended group messaging in a packet switched network
CN103609066A (en) Method and node for querying operation administration maintenance configuration information
WO2013075476A1 (en) Ethernet link detection method and device
CN110380966A (en) A kind of method and its relevant device finding forward-path
WO2014008809A1 (en) Frame loss detection method and system
KR20140138816A (en) Pseudowire groups in a packet switched network
WO2016101582A1 (en) Method for configuring and implementing operations, administration and maintenance function, and forwarding device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20170426

Termination date: 20190428

CF01 Termination of patent right due to non-payment of annual fee