CN100525291C - Link management method - Google Patents
Link management method Download PDFInfo
- Publication number
- CN100525291C CN100525291C CNB2003101157469A CN200310115746A CN100525291C CN 100525291 C CN100525291 C CN 100525291C CN B2003101157469 A CNB2003101157469 A CN B2003101157469A CN 200310115746 A CN200310115746 A CN 200310115746A CN 100525291 C CN100525291 C CN 100525291C
- Authority
- CN
- China
- Prior art keywords
- message
- lmp
- node
- protocol
- predetermined protocol
- 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.)
- Expired - Fee Related
Links
Images
Abstract
The present invention discloses one kind of link management method for automatic exchange optical network. The automatic exchange optical network includes several nodes. The method includes the following steps: a) establishing the node adjoining relation; b) maintaining the node adjoining relation via transmitting the first message of preset protocol among nodes; and c) transmitting preset protocol message among node with adjoining relation in routing mode to manage the links. Compared with available technology, the present invention maintains the adjoining relation, rather than control passage, and has reduced message interaction, reduced system load and simple link management and maintenance.
Description
Technical field
The present invention relates to the optical communication technique field, refer to the link management method of a kind of ASON of being applicable to (ASON) especially.
Background technology
Optical-fiber network comprises SDH/Sonet (SDH (Synchronous Digital Hierarchy)/Synchronous Optical Network), wavelength network etc.Traditional optical-fiber network adopts permanent connected mode to realize communication based on centralized management between the node (or being called network element).Reason has obtained better effects because of its simplicity of design, cost be lower etc. at the development of optical network initial stage to adopt described permanent connected mode.But establishment, maintenance and the dismounting that permanent connected mode light connects all needs artificial or network management system is intervened, along with the continuous growth of data business volume, and requirement dynamic to optical network system, flexible configuration that this connected mode can not satisfy.
The key that addresses the above problem is to realize dynamic light exchange, and for this reason, ITU-T (International Telecommunication Association) has proposed ASON (or being called ASON) framework, and this framework increases a control plane in traditional optical-fiber network, and proposes the notion that exchange connects.According to this thought, the node of optical-fiber network at first obtains the annexation of this node and other optical nodes by the discovery technique of link part, issue this node and the Link State relevant by control plane again with this node, and the state publications of other nodes in the reception network, final each optical node all has a accurately " network map " of topology of network of describing, and comprises multiple information such as node, link, resource in " network map ".When customer equipment or system administration request were set up node and connected, the information of node utilization " network map " obtained a feasible path in conjunction with certain routing algorithm, and the node that drives on the path by signaling protocol is set up interconnection again.Connect dynamically at network and to set up, to remove or fault causes that respective nodes will in time be issued node, the link-state information of renewal when link circuit resource changes, realize the synchronous again of " network map ".
LMP (LMP Link Manager Protocol) then is the part of the GMPLS that satisfies ASON basic structure and demand (GMPLS) protocol family of IETF (the Internet engineering duty group) definition, be used for link management between adjacent node, the annexation of local node and other nodes finds that by operation LMP on node corresponding the annexation of discovery is called data link.
Usually, two internodal data link may be very many, if all spread out by control plane, corresponding quantities of messages can be very big.In order to reduce the message number of diffusion, the data link that needs to have same alike result is merged into a virtual logical links, routing algorithm need be known the relevant information of all links when calculating feasible path, comprise maximum bandwidth, available bandwidth of link etc., these attributes are called TE (traffic engineering) attribute of link, accordingly, this logical links just is TE Link.
When internodal data link was managed, LMP at first need set up syntople between the node at data link two ends.LMP sets up internodal syntople by set up the two-way control channel that reaches between described node.Described control channel can be the band inner control passage that is based upon on the data link overhead byte, also can be that the band that passes an IP network is controlled passage outward.
Do not limit the physics realization mode of control channel bottom in LMP, it and data link are separate, can be wavelength in the optical fiber, an ethernet link, and one is passed the IP tunnel of certain network or the overhead byte on the data link.May there be a plurality of control channels to enable between a pair of node simultaneously.The control channel parameter must consulted separately on the control channel separately.LMP safeguards the connectedness of each control channel by exchange Hello message separately on every control channel with this.
There are four LMP message to be used to safeguard independently control channel.These four message are: Config, ConfigAck, ConfigNack and Hello message.These four message must be transmitted on the control channel of appointment, every other LMP message can be between a pair of adjacent node transmission in many available control channel any one.In order to safeguard the syntople of LMP, need an available control channel between a pair of adjacent node at least.
To sum up, there is following shortcoming in prior art:
1, existing LMP link management method need be safeguarded all control channel separately, and mutual message is more, and system burden is heavier, the Operation and Maintenance complexity.In fact, what the LMP link management really need be safeguarded should be internodal syntople, does not need to safeguard all control channel.
2, when between two nodes many control channels being arranged, need on the control channel of appointment, transmit except above-mentioned four LMP message, every other LMP message will transmit on a control channel therein.This control channel is that LMP elects according to the rule of oneself.But LMP is for the bottom physics realization of control channel and unclear, and the master who elects is with control channel optimum control channel between two nodes not necessarily.
3, in order to safeguard control channel, four message that control channel is relevant need send on the control channel of appointment.Every other LMP message also will be transmitted on certain bar control channel that LMP oneself selects.That is to say that all LMP message all needs specified interface to send.When internodal control channel was passed certain network, specified interface sends unicast message may cause the route loopback.Though this problem can be avoided by set up a tunnel that passes network between node, this can increase extra work.
4, to send be not that the standard of ICP/IP protocol stack realizes to specified interface, realize that specified interface sends need expand the existing protocol stack.Need to consider interoperability between the expansion of each producer, go wrong when the butt joint of the equipment room of different vendor avoiding, be unfavorable for expansion in the future.
5, suppose to have only an available control channel between two nodes, and be that bar and data link are carried on the control channel on the same physical link, as shown in Figure 1, if the optical fiber at this control channel place breaks down, professional switching, because expense can't transparent transmission, this control channel is with unavailable.As shown in Figure 2, at this moment, service channel still is available, can not use but will have control channel between these two nodes.In this case, the LMP link management has also just lost the control and management capability to resource between node.
Summary of the invention
Need safeguard that in order to solve prior art LMP link management all control channels so that Operation and Maintenance than complicated problems, the invention provides a kind of link management method, can make link management simpler, effective.
According to link management method provided by the invention, be applied in the ASON, described ASON includes a plurality of nodes, and described node is supported LMP Link Manager Protocol LMP, and this method may further comprise the steps:
A. obtain a routable control interface address of adjacent node, set up internodal syntople; Described control interface address is received end node as the far-end control interface address of waiting to set up control channel;
B. according to described control interface address between node according to predetermined Routing Protocol, set up the control channel of physics, on the control channel of described physics, send out predetermined protocol first message mutually, by the syntople between the described predetermined protocol first message Maintenance Point that can reach between node; Described predetermined protocol first message is the LMP keep-alive message;
C. have between the node of syntople,,, on the control channel of physics, sending predetermined protocol message with link management by routing mode according to described control interface address; Described routing mode is for obtaining the control channel of physics according to predetermined Routing Protocol, described predetermined Routing Protocol is that OSPF ospf protocol or intermediate system are to middle system protocol Intermediate System to Intermediate System.
Wherein, step a sets up internodal syntople by automatic discovery adjacent node or manual configuration.
Concrete, described step a sets up internodal syntople by automatic discovery adjacent node and further comprises:
A1, local node multicast predetermined protocol second message to be obtaining the control interface address of adjacent node, and consult predetermined protocol first message with the adjacent node of described control interface address and send blanking time and time-out time;
A2, if consult to pass through, then return local node and consult acknowledge message, consult refuse information otherwise return local node.
In addition, described step a sets up syntople by human configuration and further comprises:
The artificial control interface address of setting the adjacent node of local node, and, send blanking time and time-out time to consult predetermined protocol first message with the adjacent node of described control interface address to adjacent node clean culture predetermined protocol second message of described control interface address;
If consult to pass through, then return local node and consult acknowledge message, consult refuse information otherwise return local node.
In addition, described step b further comprises:
According to sending predetermined protocol first message blanking time of consulting to pass through, do not confirm that then described syntople is unavailable if in consulting the time-out time that passes through, receive described predetermined protocol first message.
Best, send predetermined protocol second message, the negotiation acknowledge message of described predetermined protocol first message, clean culture and consult refuse information by routing mode.
Optionally, described predetermined protocol is LMP Link Manager Protocol (a LMP agreement), and described predetermined protocol second message is that LMP consults configuration messages, and described negotiation acknowledge message is that LMP consults acknowledge message, and described negotiation refuse information is that LMP consults refuse information.
Optionally, described predetermined protocol is LMP Link Manager Protocol (a LMP agreement), and described predetermined protocol second message is the LMP bootstrap message, and described negotiation acknowledge message is that LMP consults acknowledge message, and described negotiation refuse information is that LMP consults refuse information;
After described step a1 further is included in local node multicast LMP bootstrap message and obtains the control interface address of adjacent node; adjacent node clean culture LMP to described control interface address consults configuration messages, sends blanking time and time-out time to consult the LMP keep-alive message with the adjacent node of described control interface address.
Best, the LMP that sends described LMP keep-alive message, clean culture by routing mode consults configuration messages, LMP negotiation acknowledge message and LMP negotiation refuse information.
Compared with prior art, the present invention has the following advantages:
1, LMP link management of the present invention is by sending out keep-alive message mutually with the syntople between Maintenance Point between node; the transmission of message can be passed through route implementing; compared with prior art; owing to no longer safeguard control channel; only maintaining adjacent concerns; can reduce the mutual of message, the mitigation system burden, the link management Operation and Maintenance is simple.
2, except the Config message and the bootstrap message of multicast, other LMP agreement control messages all can send by the mode of route, needs the control channel of appointment to transmit with prior art and compares, and message of the present invention sends more flexible, is easier to realize.
3, when two internodal control channels are passed certain network,, the unicast message specified interface may cause the route loopback if sending.Original LMP link management method must be set up a tunnel earlier in order to address this problem on two internodal corresponding control interfaces.This just need additionally take certain resource, and has increased complexity.And the present invention does not need specified interface to send owing to send message by routing mode, will the problem of route loopback can not occur, built tunnel in addition just yet.
4, owing to need not expand the existing protocol stack, the LMP message can send by routing mode.And send message by route has been ripe standard, not as extra work, is easy to realize, helps further expanding in the future.
5, in having only an available band between two nodes during physical control channel; if the optical fiber generation MSP-ring at physical control channel place is switched; this physical control channel will be no longer available; because the present invention adopts routing mode to send message; Routing Protocol can find rapidly that link is unavailable, and reselects an available path arrival adjacent node.This process is transparent to LMP.As long as Hello message can correctly arrive in the regular hour, LMP knows that not the physical control channel of bottom changes.
Description of drawings
Fig. 1 is the professional schematic diagram of the normal MSP-ring of prior art;
Fig. 2 is the professional schematic diagram of the MSP-ring after Fig. 1 service channel is switched;
Fig. 3 is the flow chart of link management method specific embodiment of the present invention;
Fig. 4 is link management method of the present invention is set up internodal syntople by automatic discovery adjacent node a flow chart;
Fig. 5 is the adjacent node schematic diagram that prior art has band inner control passage;
Fig. 6 is the schematic diagram that node A shown in Fig. 5 and Node B are consulted;
Fig. 7 is the adjacent node schematic diagram that prior art has the outer control of band passage;
Fig. 8 is a flow chart of setting up internodal syntople by artificial setting adjacent node address.
Embodiment
In this embodiment, the indication predetermined protocol is the LMP agreement, and indication predetermined protocol message is the LMP protocol message, distinguishes mutually with the control channel of prior art LMP protocol logic, following control channel refers to the control channel of physics, i.e. the actual transmission passage of interactive link administrative messag between node.Link management method of the present invention is realized based on the LMP agreement, unlike the prior art, and the LMP link management control channel of maintenance and management itself no longer among the present invention, but the syntople between Maintenance Point only.
With reference to shown in Figure 3, describe with the specific embodiment that is applied in the ASON, described ASON includes a plurality of nodes, communicates with data link between node, as the background technology introduction, has also introduced control plane etc. in the optical-fiber network automatically.So that keep normal communication, link management method specific embodiment of the present invention mainly may further comprise the steps for the link between management node:
Step 1 is set up internodal syntople.
Between the node of two support LMP functions, can set up syntople, but not all neighbours can constitute syntople, generally can set up internodal syntople by dual mode: find adjacent node or human configuration automatically.Prior art is by setting up between node the two-way logical channel control that reaches to set up internodal syntople.The notion of logical channel control has weakened among the present invention, only be concerned about promptly between node that message whether can intercommunication, and needn't be concerned about how message transmits, when setting up syntople, a control interface address that only need obtain adjacent node, the message transmission effect of control channel then can send realization by press routing mode.
Above-mentionedly set up internodal syntople, also needed to keep internodal syntople.Such as background technology part introduction, by sending out mutually Hello message verifying whether described logical channel control is available on the two-way logical channel control of setting up between node that reaches, and then then definite internodal syntople is unavailable when logical channel controls all between node is all unavailable in the prior art.This method is narrated as the front, when link management, owing to need safeguard all logical channel controls, has many shortcomings.Can be by at the syntople of mutually sending out between node Hello message described and coming between Maintenance Point in the present embodiment, promptly as long as can communicate news between two nodes, think that then internodal syntople can use, and needn't be concerned about have several logical channel controls to use between node, described predetermined protocol first message (being Hello message) can send by routing mode.
Have between the node of syntople, during link management except between Maintenance Point the Hello message of syntople, other LMP protocol messages that are used for link management also can send by routing mode, it is the LMP protocol message that needs to select certain logical channel control and specified interface transmission in the original link management according to the LMP agreement, can send by routing mode in the present invention, also the route that can obtain according to predetermined Routing Protocol transmits the LMP protocol message, described predetermined Routing Protocol can adopt OSPF (OSPF Routing Protocol) or intermediate system to middle system protocol (Intermediate System-Intermediate System), also can adopt other Routing Protocols according to actual conditions.
Describe how to set up internodal syntople below in detail, see that first automatic discovery adjacent node sets up the process of internodal syntople.When the control channel that transmits the link administrative messag between two nodes is carried on the identical physical link with data link, can adopt automatic discovery adjacent node to obtain NODE_ID of adjacent node (node identification) and control interface address, with reference to figure 4, described automatic discovery adjacent node is set up internodal syntople and is comprised following flow process:
Concrete, second message of predetermined protocol described in the step 41 can be LMP configuration messages (Config message), described negotiation acknowledge message can be LMP and consults acknowledge message (ConfigAck message), described negotiation refuse information can be LMP and consults refuse information (ConfigNack message), after the adjacent node address was obtained in multicast, described LMP consulted acknowledge message, LMP consults refuse information and sends by routing mode.In addition, according to the mode of LMP protocol description, find the address of adjacent node automatically by the described Config message of multicast, the form of described Config message is as follows:
<Config?Message>::＝<Common?Header><MESSAGE_ID>
<LOCAL_NODE_ID>
<CONFIG>
The specific definition of various piece is as follows in the Config message:
＜Common Header 〉: universal information head object, all LMP message (except the TEST message that will send on the specific data link) all have this universal information head object.This object has been specified the type of message of current message, information such as length.
＜MESSAGE_ID 〉: message identifier object, this object are used to identify a message, will be with the value that goes up in this object when the recipient sends corresponding response message.
＜LOCAL_NODE_ID 〉: local node sign object is used to identify the node ID that produces this message.
＜CONFIG 〉: comprised the blanking time and the time-out time of Hello message in this object, these two values need two nodes to hold consultation.
In addition, because the LMP link management logical channel control of maintenance and management no longer among the present invention itself, therefore the CCID that defines in the LMP draft agreement (32 unique nonzero integers in the range of nodes, its unique sign sends the logical channel control of this message) will no longer need in the present invention.
Concrete automatic discovery adjacent node sets up that the process of syntople is exemplified below between node:
With reference to shown in Figure 5, there are three data link to link to each other between two nodes (node A, Node B) that Fig. 5 describes, these three data link are merged into a TE Link.Set up the control channel of a physics therein on the overhead byte of a data link, this control channel is band inner control passage.Since when control channel is carried on the identical physical link with data link, can be by exchanging NODE_ID and the control interface address that Config message is obtained the adjacent node of control channel far-end dynamically, i.e. adjacent node address.
In these cases, node A at first is carried on multicast Config message on the control channel of same physical link in local all and data link, wherein the source address of the Config message of node A transmission is the local node control interface address of clean culture, and destination address is multicast address (as 224.0.0.1).After Node B is received Config message, just can obtain the control interface address (i.e. source address in the Config message of Jie Shouing) of adjacent node, the NODE-ID (being the sign of node A) that in taking out Config message, carries, and this NODE-ID checked, if this NODE-ID is identical with local NODE-ID, just abandon this message.If this is a newfound adjacent node, whether the Node B basis accepts the parameter in the Config message, to message of node A response, if accept, then responds a ConfigAck message, otherwise responds a ConfigNack message.In addition,, and responded ConfigAck message, then directly to ConfigNack message of node A response to the other side if Node B has had been found that this NODE-ID.The adjacent node control interface address that has obtained into is just filled out in the purpose IP address of ConfigAck message and ConfigNack message, and source address is the control interface address of local node.
Wherein the form of ConfigAck message is as follows:
<ConfigAck?Message>::＝<Common?Header><LOCAL_NODE_ID>
<MES?SAGE_ID_ACK><REMOTE_NODE
_ID>
Described ConfigAck message specific definition is as follows:
＜Common Header〉and＜LOCAL_NODE_ID content described with the front.
＜MESSAGE_ID_ACK 〉: the acknowledge message object, be used to identify the message that is identified, this value is from being identified message＜MESSAGE_ID〉copy comes out the object.
＜REMOTE_NODE_ID 〉: distant-end node sign object is used to identify distant-end node.
And the form of ConfigNack message is as follows:
<ConfigNack?Message>::＝<Common?Header>
<LOCAL_NODE_ID>
<MESSAGE_ID_ACK>
REMOTE_NODE_ID><CONFIG>
The object front of using in the ConfigNack message was all introduced.In Node B not when the blanking time in the Config message that sends of recipient node A and time-out time, just can be to ConfigNack message of node A response.The value of carrying in the Config object of wherein said ConfigNack message is that Node B is wished the blanking time and the time-out time that adopt.
Fig. 6 shows the negotiations process of node A and Node B, if Node B is agreed the blanking time and the time-out time that carry in the described Config message, just to ConfigAck message of node A response; Otherwise just respond a ConfigNack message.If the NODE_ID that carries in this Config message of receiving of Node B is an adjacent node NODE_ID who has been found that, and has responded ConfigAck message to the other side, just respond one not with the ConfigNack message of Config object.After node A receives ConfigAck or ConfigNack message, just can obtain NODE_ID and the control interface address of control channel distant-end node B.
Above-mentionedly find automatically that with multicast Config message syntople describes, find automatically when specifically implementing that adjacent node can also realize by multicast LMP bootstrap message on data link according to the mode of describing in [LMP-BOOTSTRAP].
Concrete described LMP bootstrap message (Bootstrap message), its form is as follows:
<Bootstrap?Message>::＝<Common?Header><LOCAL_INTERFACE_ID>
<LOCAL_NODE_ID>[<LOCAL_CONTROL_ADDRESS>...]
In the described message＜Common Header〉and＜LOCAL_NODE_ID〉definition of object is the same,＜LOCAL_INTERFACE_ID〉object is the interface identifier of local data-link, be used to identify a data LI(link interface) of local node,＜LOCAL_CONTROL_ADDRESS〉object then is local node control interface address, is used to identify set up a required control interface of control channel.
If above-mentioned Bootstrap message does not comprise＜LOCAL_CONTROL_ADDRESS 〉, so＜and LOCAL_NODE_ID〉message content that comprises of object must be a routable address (being that this address can arrive by common route), this address is set up control channel with the side of being received as the far-end control interface address of control channel.The process of setting up control channel is consistent by the process that multicast LMP consults configuration messages (Config message) realization with the front; promptly obtain adjacent node control interface address by multicast Bootstrap message; can consult the LMP keep-alive message by clean culture Config message and adjacent node then and send blanking time and time-out time; pass through if consult; then return local node LMP and consult acknowledge message, consult refuse information otherwise return local node LMP.Because routable adjacent node address has been obtained in multicast, the Config message of described clean culture, LMP consult acknowledge message and LMP negotiation refuse information all can send by routing mode.In addition, in single Bootstrap message, can comprise a plurality of＜LOCAL_CONTROL_ADDRESS 〉, also promptly can arrive the other side by a plurality of purpose control interfaces address.
The following describes the process of setting up syntople by human configuration.
Figure 7 shows that a band controls passage outward, the control channel shown in Fig. 7 is passed an IP network.For the outer control of band passage, need set up internodal syntople by human configuration adjacent node address.With reference to figure 8, human configuration is set up internodal syntople and be may further comprise the steps:
The artificial adjacent node address of setting local node of step 81, described adjacent node address is the NODE_ID and the control interface address of adjacent node, then can be with this control interface address as destination address to described node clean culture predetermined protocol second message, send blanking time and time-out time to consult predetermined protocol first message with described node;
Step 82 judges whether to consult to pass through; If consult to pass through, enter step 83, return local node and consult acknowledge message, otherwise, enter step 84, return local node and consult refuse information.
Predetermined protocol second message of above-mentioned clean culture is LMP configuration messages (being Config message), message format as hereinbefore, it is identical that the process of setting up control channel and front are described, and repeats no more here.
After having set up internodal syntople, after promptly two nodes were consulted to pass through, according to the blanking time of consulting to pass through, two adjacent nodes began regularly to send keep-alive message (being Hello message) to the other side, tell the other side that oneself also lives.If in consulting the time-out time that passes through, do not receive the other side's Hello message, think that then internodal syntople is unavailable.
In all message of above-mentioned LMP, the required Config message of syntople needs the multicast transmission between node except setting up, between the node behind the tool syntople, the LMP protocol message all can send to adjacent node by routing mode, no longer specifies on certain bar control channel to send.
Adopt technique scheme of the present invention, when two nodes have only been set up a control channel, and when being band inner control passage, if the business on the data link at control channel place is switched, when this control channel is unavailable, can reselect a path that arrives adjacent node by route and transmit LMP link management message, this process is transparent to LMP, promptly for the LMP link management, as long as Hello message can correctly arrive within a certain period of time, the LMP link management does not know that the physics realization of bottom changes, and helps expansion in the future.
And for the outer control of band passage, if sending, the unicast message specified interface may cause the route loopback, among the present invention, the message of clean culture does not need specified interface to send, as long as the adjacent node control interface address of setting is a routable address, message just can send to adjacent node by route, do not need between two internodal corresponding control interfaces, to set up the tunnel, therefore, just do not need additionally to take resource yet, realize simple.
To sum up, the LMP link management among the present invention is the control channel of maintenance itself no longer, only the syntople between Maintenance Point, reduced message interaction, reduced the burden of system, simultaneously, except the Config message of multicast, other LMP message can send by routing mode, need not expand the existing protocol stack, and send the standard that message has been a maturation, as extra work by route, alleviate the burden that realizes, helped further expanding of future.
It is above-mentioned that only the present invention will be described with preferred embodiment, non-so promptly limit to interest field of the present invention, therefore, under the situation that does not break away from inventive concept, the equivalence that all utilizations specification of the present invention and accompanying drawing content are done changes, and all reason is with being contained in the claim scope of the present invention.
Claims (9)
1, a kind of link management method is applied in the ASON, and described ASON includes a plurality of nodes, and described node is supported LMP Link Manager Protocol LMP, it is characterized in that, said method comprising the steps of:
A. obtain a routable control interface address of adjacent node, set up internodal syntople; Described control interface address is received end node as the far-end control interface address of waiting to set up control channel;
B. according to described control interface address between node according to predetermined Routing Protocol, set up the control channel of physics, on the control channel of described physics, send out predetermined protocol first message mutually, by the syntople between the described predetermined protocol first message Maintenance Point that can reach between node; Described predetermined protocol first message is the LMP keep-alive message;
C. have between the node of syntople,,, on the control channel of physics, sending predetermined protocol message with link management by routing mode according to described control interface address; Described routing mode is for obtaining the control channel of physics according to predetermined Routing Protocol, described predetermined Routing Protocol is that OSPF ospf protocol or intermediate system are to middle system protocol Intermediate System to Intermediate System.
According to the described link management method of claim 1, it is characterized in that 2, step a sets up internodal syntople by automatic discovery adjacent node or manual configuration.
According to the described link management method of claim 2, it is characterized in that 3, described step a sets up internodal syntople by automatic discovery adjacent node and further comprises:
A1. local node multicast predetermined protocol second message to be obtaining the control interface address of adjacent node, and consults predetermined protocol first message with the adjacent node of described control interface address and send blanking time and time-out time;
A2. if consult to pass through, then return local node and consult acknowledge message, consult refuse information otherwise return local node.
According to the described link management method of claim 2, it is characterized in that 4, described step a sets up syntople by human configuration and further comprises:
The artificial control interface address of setting the adjacent node of local node, and, send blanking time and time-out time to consult predetermined protocol first message with the adjacent node of described control interface address to adjacent node clean culture predetermined protocol second message of described control interface address;
If consult to pass through, then return local node and consult acknowledge message, consult refuse information otherwise return local node.
5, according to claim 3 or 4 described link management methods, it is characterized in that described step b further comprises:
According to sending predetermined protocol first message blanking time of consulting to pass through, do not confirm that then described syntople is unavailable if in consulting the time-out time that passes through, receive described predetermined protocol first message.
6, according to the described link management method of claim 5, it is characterized in that, send predetermined protocol second message, the negotiation acknowledge message of described predetermined protocol first message, clean culture and consult refuse information by routing mode.
7, according to the described link management method of claim 6, it is characterized in that, described predetermined protocol is a LMP Link Manager Protocol LMP agreement, described predetermined protocol second message is that LMP consults configuration messages, described negotiation acknowledge message is that LMP consults acknowledge message, and described negotiation refuse information is that LMP consults refuse information.
8, according to the described link management method of claim 3, it is characterized in that, described predetermined protocol is a LMP Link Manager Protocol LMP agreement, described predetermined protocol second message is the LMP bootstrap message, described negotiation acknowledge message is that LMP consults acknowledge message, and described negotiation refuse information is that LMP consults refuse information;
After described step a1 further is included in local node multicast LMP bootstrap message and obtains the control interface address of adjacent node; adjacent node clean culture LMP to described control interface address consults configuration messages, sends blanking time and time-out time to consult the LMP keep-alive message with the adjacent node of described control interface address.
9, described according to Claim 8 link management method is characterized in that, the LMP that sends described LMP keep-alive message, clean culture by routing mode consults configuration messages, LMP negotiation acknowledge message and LMP negotiation refuse information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2003101157469A CN100525291C (en) | 2003-11-28 | 2003-11-28 | Link management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2003101157469A CN100525291C (en) | 2003-11-28 | 2003-11-28 | Link management method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1622547A CN1622547A (en) | 2005-06-01 |
| CN100525291C true CN100525291C (en) | 2009-08-05 |
Family
ID=34760539
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2003101157469A Expired - Fee Related CN100525291C (en) | 2003-11-28 | 2003-11-28 | Link management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100525291C (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9602343B1 (en) | 2013-12-30 | 2017-03-21 | Google Inc. | System and method for establishing connection with network controller |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101030967B (en) * | 2006-03-01 | 2011-11-30 | 中兴通讯股份有限公司 | Method for inspecting and maintaining network controlling channel accessibility |
| CN101176280B (en) * | 2006-04-12 | 2012-06-13 | 中兴通讯股份有限公司 | Automatic discovering method for automatic exchange optical network controlling entity topology |
| CN101047700B (en) | 2006-05-01 | 2010-05-12 | 华为技术有限公司 | Method and device for raising reliability of LMP control channel |
| CN101174974B (en) * | 2006-11-01 | 2010-05-12 | 中兴通讯股份有限公司 | Node maintenance message processing method for O-UNI system |
| CN101217338B (en) * | 2007-01-06 | 2012-04-25 | 华为技术有限公司 | Detection message transmitting method, network element device |
| CN101026559B (en) * | 2007-01-23 | 2010-07-28 | 华为技术有限公司 | Communication establishing method and router |
| CN104869066A (en) * | 2014-02-21 | 2015-08-26 | 中兴通讯股份有限公司 | Dynamic connection updating method and device |
| CN105530117A (en) * | 2014-10-24 | 2016-04-27 | 中兴通讯股份有限公司 | Method, device and system for updating protocol state of control channel |
| CN105553864B (en) * | 2014-10-31 | 2020-04-28 | 中兴通讯股份有限公司 | Method and device for reducing message quantity in LMP |
| CN113067736B (en) * | 2021-03-31 | 2022-06-17 | 烽火通信科技股份有限公司 | Method and device for controlling plane link display |
-
2003
- 2003-11-28 CN CNB2003101157469A patent/CN100525291C/en not_active Expired - Fee Related
Non-Patent Citations (4)
| Title |
|---|
| Link Management Protocol(LMP) draft-ietf-ccamp-lmp-07.txt. Jonathan P.Lang et al.Network Working Group Internet Draft. 2002 |
| Link Management Protocol(LMP) draft-ietf-ccamp-lmp-07.txt. Jonathan P.Lang et al.Network Working Group Internet Draft. 2002 * |
| 自动交换光网络中LMP的应用. 刘翔宇.全国第十一次光纤通信暨第十二届集成光学学术会议（OFCIO’2003）论文集. 2003 |
| 自动交换光网络中LMP的应用. 刘翔宇.全国第十一次光纤通信暨第十二届集成光学学术会议（OFCIO’2003）论文集. 2003 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9602343B1 (en) | 2013-12-30 | 2017-03-21 | Google Inc. | System and method for establishing connection with network controller |
| US10075335B1 (en) | 2013-12-30 | 2018-09-11 | Google Llc | System and method for establishing connection with network controller |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1622547A (en) | 2005-06-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8463123B2 (en) | Optical switch and protocols for use therewith | |
| US7633938B2 (en) | Transfer system | |
| US7733812B2 (en) | Method for enabling multipoint network services over a ring topology network | |
| US8295204B2 (en) | Method and system for dynamic assignment of network addresses in a communications network | |
| WO2007134551A1 (en) | Mathod and node device of reserving network resources | |
| US8699342B2 (en) | Transmission device | |
| CN103731373B (en) | The method of adjustment of bandwidth resources, apparatus and system | |
| CN100525291C (en) | Link management method | |
| US20090103533A1 (en) | Method, system and node apparatus for establishing identifier mapping relationship | |
| WO2005011302A1 (en) | A method of transformation between permanent connection and switched connection in optical network | |
| US20130004170A1 (en) | OSS Support for Control Plane Technology | |
| CN100384155C (en) | Client layer chain-link automatic finding method and apparatus | |
| CN107615721A (en) | Transmitting software defines network (SDN) logical links polymerization (LAG) member's signaling | |
| WO2005083913A1 (en) | A processing method for multiplexing segment ring link in automatic exchange optical network | |
| WO2006022074A1 (en) | Communication network, communication apparatus, communication control method and communication control program | |
| CN107483141B (en) | Ethernet link method for building up and controller | |
| CN102318293B (en) | Method, advice and system of establishing LSP | |
| CN100359877C (en) | Discovery of link type | |
| CN101978629A (en) | System and method for implementing an automatic discovery function in a dwdm network | |
| US6934284B1 (en) | Methods for establishing control signaling at link start-up | |
| CN109005473B (en) | Method, device and system for cooperatively selecting path | |
| US7042882B2 (en) | Layer-structured path setup method and node apparatus for implementing same | |
| US7110364B1 (en) | Optical link adjacency discovery protocol and an optical network therefor | |
| CN101166112A (en) | Simplified message processing method for O-UNI system | |
| CN101166110A (en) | Message processing method in link maintenance of O-UNI system |
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: 20090805 Termination date: 20161128 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |