CN102769540B - A kind of overall label management method and equipment - Google Patents
A kind of overall label management method and equipment Download PDFInfo
- Publication number
- CN102769540B CN102769540B CN201210232800.7A CN201210232800A CN102769540B CN 102769540 B CN102769540 B CN 102769540B CN 201210232800 A CN201210232800 A CN 201210232800A CN 102769540 B CN102769540 B CN 102769540B
- Authority
- CN
- China
- Prior art keywords
- client device
- label
- lae
- overall
- fec
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Abstract
The invention discloses a kind of overall label management method and equipment, by applying technical scheme of the present invention, distribution and the management of overall label is realized by arranging LAE in systems in which, the each client device in system is made to process operation accordingly according to unified overall label, each client device can by sending label distribution request message or label releasing request message to LAE, realize distribution or the release of overall label, thus, the equipment complexity avoiding each client device to need to set up respectively independently tag control system increasing, unify system-wide label scheduling, improve the efficiency of respective handling.
Description
Technical field
The present invention relates to communication technical field, particularly the overall label management method of one and equipment.
Background technology
Existing MPLS (Multi-ProtocolLabelSwitching, multiprotocol label switching) in system, label only has local meaning, label represent what meaning, corresponding be which FEC (ForwardingEquivalenceClasse, forwarding equivalence class), only have the equipment distributing it just to know.
This promotes the generation of tag distribution protocol, the core of this quasi-protocol, exactly for FEC distributes a local label, and it is advertised to miscellaneous equipment, to form LSP (LabelSwitchedPaths, label forwarding path).Common tag distribution protocol has LDP (LabelDistributionProtocol, tag distribution protocol), BGP (BorderGatewayProtocol, Border Gateway Protocol), RSVP (ResourceReservationProtocol, RSVP) etc.
Conventional scene is that set up the LSP based on route, now IPv4 route is exactly FEC in IPv4 (InternetProtocolversion4, Internet protocol edition 4) network.Therefore, in a network except will Routing Protocol be run, make all network equipments all learn beyond IPv4 route, also need to run tag distribution protocol LDP, the LSP based on label forwarding could be set up.
As shown in Figure 1, be a kind of in prior art schematic diagram of concrete IPv4 network LSP foundation.This is that a LDP agreement carries out distributing label for route 10.6.0.1/32 and setting up the process of LSP, does not comprise the process that Routing Protocol runs in this figure.
Visible, each equipment will distribute a label for route 10.6.0.1/32, and by the LabelMapping message upstream devices advertise of the binding relationship of label and FEC by LDP.If upstream equipment has learnt this route of 10.6.0.1/32 by Routing Protocol, corresponding LSP will be set up.
For example, for B equipment, it can receive the LabelMapping message of C equipment and D equipment, uses which label as the outgoing label of LSP, will see the situation of route 10.6.0.1/32.If this route is preferably by C device forwards, so the form of LSP should be as shown in table 1:
The LSP form that one kind, table 1 is concrete
| InLable | OutLabel | NextHop |
| 100 | 150 | C |
If this route is preferably by D device forwards, so the form of LSP should be as shown in table 2:
The LSP form that one kind, table 2 is concrete
| InLable | OutLabel | NextHop |
| 100 | 120 | D |
Realizing in process of the present invention, inventor finds that prior art at least exists following problem:
Because label only has local significance, therefore each equipment needs a set of tag control system, adds equipment complexity.
Because label only has local significance, independent tag distribution protocol is therefore needed to notice the binding relationship of local FEC and label.
Using route as in the network of FEC, need tag distribution protocol and Routing Protocol with the use of, add the complexity that equipment realizes.
Because a FEC is on the different nodes of forward-path, the label of use is different, causes pretection switch and realizes more difficult.
Summary of the invention
The invention provides a kind of overall label management method and equipment, solve in prior art the operating process complexity only can applied local label and bring, the problem of inconvenience management.
For achieving the above object, one aspect of the present invention provides a kind of overall label management method, and be applied in the system comprising label distribution unit LA E and multiple client device, described method at least comprises the following steps:
When described LAE receives the label distribution request message that a client device sent by label distribution protocol LAP, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and during the information of corresponding forwarding equivalence class FEC, described LAE is that described FEC distributes overall label, and be carried in label distribution response message, send to described client device;
When described LAE receives the label releasing request message of a client device transmission, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and during overall label information to be released, described LAE is that described FEC discharges corresponding overall label, and notifies that described client device discharges result accordingly by label release response message;
Wherein, it be the corresponding relation of the overall label of all FEC distribution that described LAE preserves current, and the corresponding relation of each application in each FEC and each client device.
On the other hand, present invention also offers a kind of LAE, be applied in the system comprising LAE and multiple client device, described LAE at least comprises:
Receiver module, for receiving label distribution request message or the label releasing request message of client device transmission;
Distribution module, for receiving the label distribution request message that a client device sends when described receiver module, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and during the information of corresponding FEC, for described FEC distributes overall label;
Memory module, for preserving the corresponding relation of the current overall label distributed for all FEC of described distribution module, and the corresponding relation of each application in each FEC and each client device;
Release module, for receiving the label releasing request message that a client device sends when described receiver module, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and during overall label information to be released, for described FEC discharges corresponding overall label, and notify that described memory module deletes the described overall label stored, and the corresponding relation of described overall label and described FEC;
Sending module, for being after described FEC distributes overall label in described distribution module, described overall label is carried in label distribution response message, send to described client device, or after described release module is interpreted as the corresponding overall label of described FEC release, notify that described client device discharges result accordingly by label release response message.
On the other hand, present invention also offers a kind of overall label management method, be applied in the system comprising LAE and multiple client device, described method at least comprises the following steps:
When client device needs to distribute overall label, described client device sends label distribution request message to described LAE, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and the information of corresponding forwarding equivalence class FEC, and receive the label distribution response message comprising distributed overall label that described LAE returns;
When client device needs to discharge overall label, described client device sends label releasing request message to described LAE, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and overall label information to be released, and receive the label release response message comprising corresponding release result that described LAE returns.
On the other hand, present invention also offers a kind of client device, be applied in the system comprising LAE and multiple client device, described client device at least comprises:
Sending module, for when described client device needs to distribute overall label, label distribution request message is sent to described LAE, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and the information of corresponding forwarding equivalence class FEC, or when client device needs to discharge overall label, label releasing request message is sent to described LAE, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and overall label information to be released,
Receiver module, for receiving the label distribution response message comprising distributed overall label that described LAE returns, or receives the label release response message comprising corresponding release result that described LAE returns.
Compared with prior art, technical scheme proposed by the invention has the following advantages:
By applying technical scheme of the present invention, distribution and the management of overall label is realized by arranging LAE in systems in which, the each client device in system is made to process operation accordingly according to unified overall label, each client device can by sending label distribution request message or label releasing request message to LAE, realize distribution or the release of overall label, thus, the equipment complexity avoiding each client device to need to set up respectively independently tag control system increasing, unify system-wide label scheduling, improve the efficiency of respective handling.
Accompanying drawing explanation
Fig. 1 is the schematic diagram that IPv4 network LSP of the prior art sets up;
Fig. 2 is the schematic flow sheet of a kind of overall label management method proposed by the invention;
Fig. 3 is the schematic flow sheet of a kind of overall label management method proposed by the invention;
LAP protocol stack schematic diagram under a kind of embody rule scene that Fig. 4 proposes for the embodiment of the present invention;
The schematic flow sheet of the overall label management method under a kind of embody rule scene that Fig. 5 proposes for the embodiment of the present invention;
The schematic flow sheet of the overall label management method under a kind of embody rule scene that Fig. 6 proposes for the embodiment of the present invention;
Fig. 7 A and Fig. 7 B is respectively the application scenarios schematic diagram before and after a kind of overall label management method that proposes of the application embodiment of the present invention;
The structural representation of a kind of LEA that Fig. 8 proposes for the embodiment of the present invention;
The structural representation of a kind of client device that Fig. 9 proposes for the embodiment of the present invention.
Embodiment
As stated in the Background Art, for existing tag control process, because label only has local significance, therefore each equipment needs a set of tag control system, add equipment complexity, and need independent tag distribution protocol to notice the binding relationship of local FEC and label.
Using route as in the network of FEC, need tag distribution protocol and Routing Protocol with the use of, add the complexity that equipment realizes.Because a FEC is on the different nodes of forward-path, the label of use is different, causes pretection switch and realizes more difficult.
In order to solve such problem, the present invention proposes a kind of overall label distribution method, LAE (LabelAllocationElement is increased in MPLS system, label distribution unit), overall label is distributed for each client device by it, make a FEC can use unique label on its forward-path, the complexity of simplified apparatus design and network operation.
As shown in Figure 2, be the schematic flow sheet of a kind of overall label management method proposed by the invention, the method is applied in the system comprising LAE and multiple client device, specifically comprises the following steps:
Step S201, described LAE receive the label distribution request message that a client device sends.
Wherein, comprise the identification information of described client device in described label distribution request message, the identification information of the application on described client device, and the information of corresponding forwarding equivalence class FEC.
Step S202, described LAE are that described FEC distributes overall label, and are carried in label distribution response message, send to described client device.
Wherein, it be the corresponding relation of the overall label of all FEC distribution that described LAE preserves current, and the corresponding relation of each application in each FEC and each client device.
Step S203, described LAE receive the label releasing request message that a client device sends.
Wherein, comprise the identification information of described client device in described label releasing request message, the identification information of the application on described client device, needs the information of the FEC discharging overall label, and overall label information to be released.
Step S204, described LAE are that described FEC discharges corresponding overall label, and notify that described client device discharges result accordingly by label release response message.
It should be noted that, said process be LAE to the distribution of overall label and dispose procedure, in concrete process scene, client device can carry out the inquiry of overall label information directly to LAE, corresponding processing procedure is as follows:
When described LAE receives the tag queries request message of a client device transmission, and in described tag queries request message, comprise the identification information of described client device, during the identification information of the application on described client device, the all overall label information that each FEC of described LAE inquiry corresponding to described application distributes, and be carried in tag queries response message, send to described client device.
Wherein, described tag queries response message comprises end identification information, for identifying in current tag queries response message all overall label information whether being included as each FEC corresponding to described application and having distributed.
Further, the corresponding relation in order to ensure the LAE in system and client device is in state of activation, and the embodiment of the present invention further introduces following protection mechanism, to ensure the validity of overall label.
Described LAE is mutual respectively by keep-alive message, carries out keep-alive checking with each client device in described system.
When described LAE determines that a client device is no longer present in described system, described LAE is released to the whole overall label that each FEC corresponding to all application on described client device distributes.
Corresponding, in client device side, need to carry out corresponding message transmission and reception, thus obtain or discharge corresponding overall label.
As shown in Figure 3, be the schematic flow sheet of a kind of overall label management method proposed by the invention, the method is applied in the system comprising LAE and multiple client device, specifically comprises the following steps:
Step S301, client device determine that current needs distributes overall label.
Step S302, described client device send label distribution request message to described LAE.
Wherein, comprise the identification information of described client device in described label distribution request message, the identification information of the application on described client device, and the information of corresponding forwarding equivalence class FEC.
Step S303, client device receive the label distribution response message comprising distributed overall label that described LAE returns.
After this step completes, the further processing procedure of client device to overall label comprises following two kinds of modes:
Mode one, when described system adopts initiating equipment to distribute the label distribution rule of overall label, described client device is at the described overall label of this locality application, and upstream each client device sends the message of carrying described overall label, hop-by-hop reports described overall label.
Mode two, described system adopt other equipment queries obtain overall label label distribution rule time, described client device is at the described overall label of this locality application, and upstream each client device sends a notification message, inquire about corresponding overall label with each client device triggering upstream to described LAE.
In actual applications, concrete which kind of mode that adopts can set according to the actual needs, and such change can't affect protection scope of the present invention.
Step S304, client device determine that current needs discharges overall label.
Step S305, described client device send label releasing request message to described LAE.
Wherein, comprise the identification information of described client device in described label releasing request message, the identification information of the application on described client device, needs the information of the FEC discharging overall label, and overall label information to be released.
Step S306, client device receive the label release response message comprising corresponding release result that described LAE returns.
It should be noted that, said process be client device to the acquisition of overall label and dispose procedure, in concrete process scene, client device can carry out the inquiry of overall label information directly to LAE, corresponding processing procedure is as follows:
When client device completes GR (GracefulRestart, smooth restarting), or time the notification message that the client device receiving downstream sends (i.e. corresponding aforesaid mode two), described client device sends tag queries request message to described LAE, and in described tag queries request message, comprise the identification information of described client device, the identification information of the application on described client device, and the tag queries response message being included as all overall label information that each FEC corresponding to described application distributes receiving that described LAE returns.
Wherein, described tag queries response message comprises end identification information, for identifying in current tag queries response message all overall label information whether being included as each FEC corresponding to described application and having distributed.
Further, the corresponding relation in order to ensure the LAE in system and client device is in state of activation, and the embodiment of the present invention further introduces following protection mechanism, to ensure the validity of overall label.
Each client device is mutual respectively by keep-alive message, carries out keep-alive checking with described LAE;
When described client device determines that described LAE is no longer present in described system, described client device notifies self corresponding each application, stops using the whole overall label that described LAE distributes.
In order to realize the compatibility of local label and overall label, in concrete processing procedure, if when described client device needs transmission to carry the message of local label and overall label simultaneously, described client adds overall tag identifier in described message, if and carry local label and overall label in message received by described client device simultaneously, overall tag identifier is also comprised in described message, thus, mark overall label by overall tag identifier, thus dissimilar label is distinguished.
Compared with prior art, technical scheme proposed by the invention has the following advantages:
By applying technical scheme of the present invention, distribution and the management of overall label is realized by arranging LAE in systems in which, the each client device in system is made to process operation accordingly according to unified overall label, each client device can by sending label distribution request message or label releasing request message to LAE, realize distribution or the release of overall label, thus, the equipment complexity avoiding each client device to need to set up respectively independently tag control system increasing, unify system-wide label scheduling, improve the efficiency of respective handling.
In order to set forth technological thought of the present invention further, now in conjunction with concrete application scenarios, technical scheme of the present invention is described.
Embodiments provide a kind of method of carrying out label distribution and release in MPLS system, by presetting management attaching relation in FEC equipment, realizing the transmission of corresponding tag processes message and receiving process.
Based on such method, need in network to set up an overall label distribution unit (LAE), the function of label distribution is provided.LAE can provide on independent server, also can certain equipment in a network provide, as long as equipment all in network can have access to LAE.
All equipment, if need distributing labels, all needs by label distribution protocol (LAP) and LAE mutual, distributes and release label.Therefore, equipment needs the address all needing to configure LAE, to facilitate LAP mutual.
LAE plant maintenance overall situation Label space, comes Management label space according to the request of each equipment.And initiate the equipment of label distribution, i.e. the client device of LAE, all need unique RouterID, identify each client device for LAE.
In concrete application scenarios, LAE carries out overall label distribution, make a FEC can use unique label on its forward-path, facilitate transfer of data on the one hand, reduce the process complexity that a large amount of local label of respective handling logical process brings, on the other hand, identical overall label is not used to save a large amount of label resources by means of only each node on the forward-path of same FEC, and, the release of overall label can be carried out, thus realize recycling of label resources, solve the problem that overall label resources is limited, the global administration of LAE also can repeat or conflict by label in an efficient way.
And in the mode of FEC for overall label distribution foundation, LAE is avoided to determine the complex process that label distribution scope (network range namely representated by above-mentioned " overall situation ") is brought to effectively raise the efficiency that LAE distributes overall label by carrying out node recognition one by one.
As shown in Figure 4, be LAP protocol stack schematic diagram, a LAE can pass through LAP protocol stack, for multiple client provides overall tag control service; And on a client device, also can have multiple application distributing labels simultaneously, such as TE application, L2VPN application, L3VPN application etc.
When equipment needs distributing labels, need to send LAR (LabelAllocationRequest, label distribution request message) to LAE, this message mainly comprises following content:
Client RouterID;
The application ID of client;
FEC information.
If LAE is allocated successfully, then respond LAA (LabelAllocationAck, label distribution response message), this message mainly comprises following content:
Client RouterID;
The application ID of client;
FEC information;
Label/LabelRange。
When equipment needs to discharge label, need to send LFR (LabelFreeRequest, label releasing request message) to LAE, this message mainly comprises following content:
Client RouterID;
The application ID of client;
FEC information;
Label/LabelRange。
If LAE discharges successfully, then respond LFA (LabelFreeAck, label release response message), this message mainly comprises following content:
Client RouterID;
The application ID of client;
FEC information;
Label/LabelRange。
LAP needs to support batch label distribution and release function.If LAE does not reply, then client LAP should resend corresponding request message.
Keepalive mechanism is needed, to confirm whether the other side exists between LAE and its client.LAP protocol stack can detect by regularly sending KA (KeepAlive, keep-alive) message.
For LAE, if confirm that certain client is not present in, the label that so can be distributed all is regained; For client, if confirm that LAE is not present in, just need notice application module should not re-use and issue the label be assigned to.
The equipment of distributing labels, i.e. certain application in the client of LAE, makes to restart.In order to realize GR, LAP should be able to support client application after restart, inquires about all labels i.e. FEC of its correspondence that it distributed.Like this, the application in client, just can use original label to continue to forward after restart, and can not cause flow interrupt.
After client application is restarted, to its all labels i.e. FEC of its correspondence distributed of local LAP protocol stack requesting query, now LAP protocol stack will send GRR (GracefulRestartRequest to LAE, namely all FEC and corresponding label information is asked after GR) message, its main contents are as follows:
Client RouterID;
The application ID of client.
After LAE receives this message, GRA (GracefulRestartRequest will be passed through, namely LAE responds all FEC and corresponding label information to client) message responds the FEC information of this client, all labels that this user distributes and correspondence, and its main contents are as follows:
Client RouterID;
The application ID of client;
Whether terminate;
FEC1 information;
Label1/LabelRange1；
FECn information;
Labeln/LabelRangen。
Visible, multiple label and FEC information can be comprised in a GRA message; If a message cannot send all information, can also be sent by multiple message, " whether terminating " field of last message is set to "True", and all information is all inquired about complete.
Consider that network may have the situation that overall label and local label exist jointly exists, therefore needing can be compatible on MPLS message encapsulation format.
In order to realize this object, use special tag, the label identified thereafter is overall label, and this special tag is referred to as GLI (GlobalLabelIdentifier, overall label identifier).This label can be a Hold sticker, such as label 10.
The encapsulation format of an overall label packet:
| Link Header | GLI | Global Label | Payload |
Multilayer labels is all the encapsulation format of overall label:
| Link Header | GLI | Global Label | GLI | Global Label | Payload |
Local label and the simultaneous encapsulation format of overall label:
| Link Header | Local Label | GLI | Global Label | Payload |
Certainly, overall Label space only has the label of 1M can be used for distributing, and can use multiple GLI, identify multiple overall Label space if not enough.
This method needs to revise existing signaling protocol, specifically as shown in Figure 5.
With the citing of RSVP signaling protocol, as shown in Figure 5, RSVP signaling protocol is used to advise the LSP of LSR1 a to LSR6.
When original RSVP signaling protocol runs, when sending Resv message, each equipment can distribute local label for LSP, and is advertised to upstream.
After employing overall Label space, just distribute overall label by the tail node (LSR6) of LSP, then by Resv message, this overall label hop-by-hop is upstream noticed, upstream equipment does not just need reallocation label, but directly use the label carried in the Resv message of downstream, and this label is continued upstream to notify.Therefore need the form revising Resv message, illustrate that the current label carried is overall label.
Advise that each application uses this kind of mode to realize, as shown in Figure 6, this implementation method makes overall label not transmit in signaling protocol to concrete enforcement scene, but miscellaneous equipment goes inquiry.Still with RSVP citing, distribute overall label by tunnel tail node LSR6 to LAE, after distribution, upstream send Resv message, in this message, there is no overall label, but after upstream equipment receives Resv message, inquire about overall label corresponding to this tunnel to LAE.
As shown in Figure 7 A, common multicast L2VPN, all just L2VPN flux of multicast is copied into two PW on PE1, then recipient is transmitted to, this just means, and the link between PE1 and P has two parts of multicast data flows, and can not copy on the place (P equipment) that distance recipient is nearest, this is because the label of PW is local distribution, namely the label of PW1 and the label of PE2 are different, namely from PE1 to PE2 and PE3 L2VPN multicast message encapsulation be different.
But, as shown in Figure 7 B, after having had overall label, this problem just solves, namely PW1 and PW2 can distribute identical label, so just can accomplish from PE1 to PE2 and the L2VPN multicast message of PE3 is duplicate, so just can replicate on P equipment.Certain L2VPN multicast message needs the LSP of dependence P2MP forwarding to copy.
Compared with prior art, technical scheme proposed by the invention has the following advantages:
By applying technical scheme of the present invention, distribution and the management of overall label is realized by arranging LAE in systems in which, the each client device in system is made to process operation accordingly according to unified overall label, each client device can by sending label distribution request message or label releasing request message to LAE, realize distribution or the release of overall label, thus, the equipment complexity avoiding each client device to need to set up respectively independently tag control system increasing, unify system-wide label scheduling, improve the efficiency of respective handling.
In order to realize technical scheme of the present invention, the invention allows for a kind of LAE, being applied in the system comprising LAE and multiple client device, shown in its structural representation Fig. 8.
Receiver module 81, for receiving label distribution request message or the label releasing request message of client device transmission;
Distribution module 82, for receiving the label distribution request message that a client device sends when described receiver module 81, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and during the information of corresponding FEC, for described FEC distributes overall label;
Memory module 83, for preserving the corresponding relation of the current overall label distributed for all FEC of described distribution module 82, and the corresponding relation of each application in each FEC and each client device;
Release module 84, for receiving the label releasing request message that a client device sends when described receiver module 81, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and during overall label information to be released, for described FEC discharges corresponding overall label, and notify that described memory module 83 deletes the described overall label stored, and the corresponding relation of described overall label and described FEC;
Sending module 85, for in described distribution module 82 for after described FEC distributes overall label, described overall label is carried in label distribution response message, send to described client device, or after described release module 84 is interpreted as the corresponding overall label of described FEC release, notify that described client device discharges result accordingly by label release response message.
Further,
Described receiver module 81, also for receiving the tag queries request that client device sends;
Described sending module 85, also for receiving the tag queries request message that a client device sends when described receiver module 81, and in described tag queries request message, comprise the identification information of described client device, during the identification information of the application on described client device, the all overall label information that current each FEC corresponding to described application distributes is inquired about to described memory module 83, and be carried in tag queries response message, send to described client device;
Wherein, described tag queries response message comprises end identification information, for identifying in current tag queries response message all overall label information whether being included as each FEC corresponding to described application and having distributed.
Concrete,
Described receiver module 81, also for receiving the keep-alive message that each client device sends, or keep-alive response message;
Described sending module 85, also for sending keep-alive message to each client device, or after described receiver module receives keep-alive message, sends keep-alive response message to corresponding client device;
Described release module 84; also for not receiving the keep-alive response message corresponding to keep-alive message that described sending module 85 sends in time at described receiver module; and when determining that corresponding client device is no longer present in described system; be released to the whole overall label that each FEC corresponding to all application on described client device distributes; and notify that described memory module 83 deletes the described overall label stored, and the corresponding relation of described overall label and described FEC.
On the other hand, the embodiment of the present invention additionally provides a kind of client device, and be applied in the system comprising LAE and multiple client device, its structural representation as shown in Figure 9, specifically comprises:
Sending module 91, for when described client device needs to distribute overall label, label distribution request message is sent to described LAE, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and the information of corresponding forwarding equivalence class FEC, or when client device needs to discharge overall label, label releasing request message is sent to described LAE, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and overall label information to be released,
Receiver module 92, for receiving the label distribution response message comprising distributed overall label that described LAE returns, or receives the label release response message comprising corresponding release result that described LAE returns.
Further,
Described sending module 91, also for completing GR when described client device, or described receiver module 92 client device that receives downstream send notification message time, tag queries request message is sent to described LAE, and comprise the identification information of described client device in described tag queries request message, the identification information of the application on described client device;
Described receiver module 92, also for receiving the tag queries response message being included as all overall label information that each FEC corresponding to described application distributes that described LAE returns;
Wherein, described tag queries response message comprises end identification information, for identifying in current tag queries response message all overall label information whether being included as each FEC corresponding to described application and having distributed.
In actual applications, this client device also comprises notification module 93:
Described receiver module 92, also for receiving the keep-alive message that described LAE sends, or keep-alive response message;
Described sending module 91, also for sending keep-alive message to described LAE, or after described receiver module 92 receives keep-alive message, sends keep-alive response message to described LAE;
Described notification module 93; for not receiving the keep-alive response message corresponding to keep-alive message that described sending module 91 sends in time at described receiver module 92; and when determining that described LAE is no longer present in described system; notify that described client device is respectively applied accordingly, stop using the whole overall label that described LAE distributes.
Compared with prior art, technical scheme proposed by the invention has the following advantages:
By applying technical scheme of the present invention, distribution and the management of overall label is realized by arranging LAE in systems in which, the each client device in system is made to process operation accordingly according to unified overall label, each client device can by sending label distribution request message or label releasing request message to LAE, realize distribution or the release of overall label, thus, the equipment complexity avoiding each client device to need to set up respectively independently tag control system increasing, unify system-wide label scheduling, improve the efficiency of respective handling.
Through the above description of the embodiments, those skilled in the art can be well understood to the present invention can by hardware implementing, and the mode that also can add necessary general hardware platform by software realizes.Based on such understanding, technical scheme of the present invention can embody with the form of software product, it (can be CD-ROM that this software product can be stored in a non-volatile memory medium, USB flash disk, portable hard drive etc.) in, comprise some instructions and perform each method implementing described in scene of the present invention in order to make a computer equipment (can be personal computer, server, or the network equipment etc.).
It will be appreciated by those skilled in the art that accompanying drawing is a schematic diagram preferably implementing scene, the module in accompanying drawing or flow process might not be that enforcement the present invention is necessary.
It will be appreciated by those skilled in the art that the module in the device implemented in scene can carry out being distributed in the device of enforcement scene according to implementing scene description, also can carry out respective change and being arranged in the one or more devices being different from this enforcement scene.The module of above-mentioned enforcement scene can merge into a module, also can split into multiple submodule further.
The invention described above sequence number, just to describing, does not represent the quality implementing scene.
Be only several concrete enforcement scene of the present invention above, but the present invention is not limited thereto, the changes that any person skilled in the art can think of all should fall into protection scope of the present invention.
Claims (14)
1. an overall label management method, is characterized in that, be applied in the system comprising label distribution unit LA E and multiple client device, described method at least comprises the following steps:
When described LAE receives the label distribution request message of a client device transmission, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and during the information of corresponding forwarding equivalence class FEC, described LAE is that described FEC distributes overall label, and be carried in label distribution response message, send to described client device;
When described LAE receives the label releasing request message of a client device transmission, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and during overall label information to be released, described LAE is that described FEC discharges corresponding overall label, and notifies that described client device discharges result accordingly by label release response message;
Wherein, it be the corresponding relation of the overall label of all FEC distribution that described LAE preserves current, and the corresponding relation of each application in each FEC and each client device.
2. the method for claim 1, is characterized in that, also comprises:
When described LAE receives the tag queries request message of a client device transmission, and in described tag queries request message, comprise the identification information of described client device, during the identification information of the application on described client device, the all overall label information that each FEC of described LAE inquiry corresponding to described application distributes, and be carried in tag queries response message, send to described client device;
Wherein, described tag queries response message comprises end identification information, for identifying in current tag queries response message all overall label information whether being included as each FEC corresponding to described application and having distributed.
3. method as claimed in claim 1 or 2, is characterized in that, also comprise:
Described LAE is mutual respectively by keep-alive message, carries out keep-alive checking with each client device in described system;
When described LAE determines that a client device is no longer present in described system, described LAE is released to the whole overall label that each FEC corresponding to all application on described client device distributes.
4. a LAE, is characterized in that, be applied in the system comprising LAE and multiple client device, described LAE at least comprises:
Receiver module, for receiving label distribution request message or the label releasing request message of client device transmission;
Distribution module, for receiving the label distribution request message that a client device sends when described receiver module, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and during the information of corresponding FEC, for described FEC distributes overall label;
Memory module, for preserving the corresponding relation of the current overall label distributed for all FEC of described distribution module, and the corresponding relation of each application in each FEC and each client device;
Release module, for receiving the label releasing request message that a client device sends when described receiver module, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and during overall label information to be released, for described FEC discharges corresponding overall label, and notify that described memory module deletes the described overall label stored, and the corresponding relation of described overall label and described FEC;
Sending module, for being after described FEC distributes overall label in described distribution module, described overall label is carried in label distribution response message, send to described client device, or after described release module is the corresponding overall label of described FEC release, notify that described client device discharges result accordingly by label release response message.
5. LAE as claimed in claim 4, is characterized in that,
Described receiver module, also for receiving the tag queries request that client device sends;
Described sending module, also for receiving the tag queries request message that a client device sends when described receiver module, and in described tag queries request message, comprise the identification information of described client device, during the identification information of the application on described client device, to all overall label information that the current each FEC corresponding to described application of described memory module inquiry distributes, and be carried in tag queries response message, send to described client device;
Wherein, described tag queries response message comprises end identification information, for identifying in current tag queries response message all overall label information whether being included as each FEC corresponding to described application and having distributed.
6. the LAE as described in claim 4 or 5, is characterized in that,
Described receiver module, also for receiving the keep-alive message that each client device sends, or keep-alive response message;
Described sending module, also for sending keep-alive message to each client device, or after described receiver module receives keep-alive message, sends keep-alive response message to corresponding client device;
Described release module; also for not receiving the keep-alive response message corresponding to keep-alive message that described sending module sends in time at described receiver module; and when determining that corresponding client device is no longer present in described system; be released to the whole overall label that each FEC corresponding to all application on described client device distributes; and notify that described memory module deletes the described overall label stored, and the corresponding relation of described overall label and described FEC.
7. an overall label management method, is characterized in that, be applied in the system comprising LAE and multiple client device, described method at least comprises the following steps:
When client device needs to distribute overall label, described client device sends label distribution request message to described LAE, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and the information of corresponding forwarding equivalence class FEC, and receive the label distribution response message comprising distributed overall label that described LAE returns;
When client device needs to discharge overall label, described client device sends label releasing request message to described LAE, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and overall label information to be released, and receive the label release response message comprising corresponding release result that described LAE returns.
8. method as claimed in claim 7, is characterized in that, after what described client device received that described LAE returns comprise the label distribution response message of distributed overall label, also comprises:
When described system adopts initiating equipment to distribute the label distribution rule of overall label, described client device is at the described overall label of this locality application, and upstream each client device sends the message of carrying described overall label, and hop-by-hop reports described overall label; Or,
When described system adopts other equipment queries to obtain the label distribution rule of overall label, described client device is at the described overall label of this locality application, and upstream each client device sends a notification message, inquire about corresponding overall label with each client device triggering upstream to described LAE.
9. method as claimed in claim 8, is characterized in that, also comprise:
When client device finishing smooth restarts GR, or the client device receiving downstream send notification message time, described client device sends tag queries request message to described LAE, and in described tag queries request message, comprise the identification information of described client device, the identification information of the application on described client device, and the tag queries response message being included as all overall label information that each FEC corresponding to described application distributes receiving that described LAE returns;
Wherein, described tag queries response message comprises end identification information, for identifying in current tag queries response message all overall label information whether being included as each FEC corresponding to described application and having distributed.
10. as the method in claim 7 to 9 as described in any one, it is characterized in that, also comprise:
Each client device is mutual respectively by keep-alive message, carries out keep-alive checking with described LAE;
When described client device determines that described LAE is no longer present in described system, described client device notifies self corresponding each application, stops using the whole overall label that described LAE distributes.
11., as the method in claim 7 to 9 as described in any one, is characterized in that,
When described client device needs transmission to carry the message of local label and overall label simultaneously, described client adds overall tag identifier in described message;
When carrying local label and overall label in the message received by described client device simultaneously, in described message, also comprise overall tag identifier.
12. 1 kinds of client devices, is characterized in that, be applied in the system comprising LAE and multiple client device, described client device at least comprises:
Sending module, for when described client device needs to distribute overall label, label distribution request message is sent to described LAE, and in described label distribution request message, comprise the identification information of described client device, the identification information of the application on described client device, and the information of corresponding forwarding equivalence class FEC, or when client device needs to discharge overall label, label releasing request message is sent to described LAE, and in described label releasing request message, comprise the identification information of described client device, the identification information of the application on described client device, need the information of the FEC discharging overall label, and overall label information to be released,
Receiver module, for receiving the label distribution response message comprising distributed overall label that described LAE returns, or receives the label release response message comprising corresponding release result that described LAE returns.
13. client devices as claimed in claim 12, is characterized in that,
Described sending module, also for completing GR when described client device, or the described receiver module client device that receives downstream send notification message time, tag queries request message is sent to described LAE, and comprise the identification information of described client device in described tag queries request message, the identification information of the application on described client device;
Described receiver module, also for receiving the tag queries response message being included as all overall label information that each FEC corresponding to described application distributes that described LAE returns;
Wherein, described tag queries response message comprises end identification information, for identifying in current tag queries response message all overall label information whether being included as each FEC corresponding to described application and having distributed.
14. client devices as described in claim 12 or 13, is characterized in that, also comprise notification module:
Described receiver module, also for receiving the keep-alive message that described LAE sends, or keep-alive response message;
Described sending module, also for sending keep-alive message to described LAE, or after described receiver module receives keep-alive message, sends keep-alive response message to described LAE;
Described notification module; for not receiving the keep-alive response message corresponding to keep-alive message that described sending module sends in time at described receiver module; and when determining that described LAE is no longer present in described system; notify that described client device is respectively applied accordingly, stop using the whole overall label that described LAE distributes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210232800.7A CN102769540B (en) | 2012-07-06 | 2012-07-06 | A kind of overall label management method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210232800.7A CN102769540B (en) | 2012-07-06 | 2012-07-06 | A kind of overall label management method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102769540A CN102769540A (en) | 2012-11-07 |
| CN102769540B true CN102769540B (en) | 2015-12-16 |
Family
ID=47096799
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210232800.7A Active CN102769540B (en) | 2012-07-06 | 2012-07-06 | A kind of overall label management method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102769540B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104243362B (en) * | 2013-06-24 | 2018-07-20 | 新华三技术有限公司 | A kind of message forwarding method and device |
| CN106549870B (en) * | 2015-09-16 | 2019-11-15 | 华为技术有限公司 | The method and relevant apparatus distributed the method for global label, obtain global label |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101043464A (en) * | 2006-06-09 | 2007-09-26 | 华为技术有限公司 | Method and system for solving label interference |
-
2012
- 2012-07-06 CN CN201210232800.7A patent/CN102769540B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101043464A (en) * | 2006-06-09 | 2007-09-26 | 华为技术有限公司 | Method and system for solving label interference |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102769540A (en) | 2012-11-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7787380B1 (en) | Resource reservation protocol with traffic engineering point to multi-point label switched path hierarchy | |
| US20090219806A1 (en) | Method, apparatus, and system for protecting head node of point to multipoint label switched path | |
| WO2021135468A1 (en) | Segment identifier determining method and device | |
| RU2574812C9 (en) | Method and node for route detection in data network | |
| CN102025538A (en) | Method and device for realizing multicasting flow load sharing based on equal-cost multi-path (ECMP) routing | |
| US20080170496A1 (en) | Management of protection path bandwidth and changing of path bandwidth | |
| CN102694718A (en) | Virtual private LAN service (VPLS) rapid rerouting method and equipment thereof | |
| WO2017045561A1 (en) | Method for allocating global label, method for acquiring global label and related device | |
| US8971174B2 (en) | Restart method and node device | |
| CN103067286A (en) | Multicast data transmission method and equipment | |
| WO2007124628A1 (en) | Method for allocating label, for remising label, and label switch router | |
| US8724451B2 (en) | Method for protecting a pseudo-wire | |
| CN101719834B (en) | Method and system for realizing virtual private multicast service protection | |
| CN103297338B (en) | A kind of VPN route advertising method and equipment | |
| CN104144122A (en) | Method, device and system for establishing label switched path | |
| WO2019174454A1 (en) | Link recovery method and device, system, storage medium, and electronic device | |
| CN111682982B (en) | Path fault detection method, device, equipment, system and storage medium | |
| EP2648382A1 (en) | Method, device and system for establishing lsp | |
| CN102447611A (en) | Method and system for establishing bidirectional point-to-multipoint label switched path as well as method and system for removing bidirectional point-to-multipoint label switched path | |
| CN102025632A (en) | Label distribution method and system for data packets in MPLS network | |
| CN102769540B (en) | A kind of overall label management method and equipment | |
| CN102255798A (en) | Method and line card for synchronizing route forwarding table items | |
| CN103986654A (en) | LSP generating method and device | |
| CN102244615B (en) | Forwarding entry sending method, device and system as well as autonomous system border router | |
| CN103238299B (en) | Method, apparatus and system for establishment of label switching paths |
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 | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |