CN1581870A - Method for improving robustness of group-playing PIM-SM protocol network - Google Patents
Method for improving robustness of group-playing PIM-SM protocol network Download PDFInfo
- Publication number
- CN1581870A CN1581870A CN 03149999 CN03149999A CN1581870A CN 1581870 A CN1581870 A CN 1581870A CN 03149999 CN03149999 CN 03149999 CN 03149999 A CN03149999 A CN 03149999A CN 1581870 A CN1581870 A CN 1581870A
- Authority
- CN
- China
- Prior art keywords
- time
- meeting point
- bsr
- message
- seconds
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The method includes following steps: (1) in case of need of sending message of bootable router, bootable router takes out time-out duration of own meeting point; (2) bootable router compares the said time-out duration with a preset time; (3) when the said time-out duration is larger than or equal to the preset time, the bootable router sets up the time-out duration of meeting point in message to be sent as holding time of meeting point; (4) when the said time-out duration is smaller than the preset time, the bootable router sets up the time-out duration of meeting point in message to be sent as time-out duration of local meeting point. The invention guarantees consistent of information of meeting points in whole network effectively so as to raise robustness of network in multicast PIM-SM protocol.
Description
Invention field
The present invention relates generally to the network communications technology, thus particularly a kind of by the be consistent method of the robustness that improves multicast PIM-SM protocol network of the meeting point information that in network multicast communication, makes multicast PIM-SM agreement.
Background technology
Traditional internet, applications all is with point-to-point IP transmission (unicast technique), and the IP of point-to-multipoint transmission (broadcast technology) is only limited to the local area network (LAN) internal application, and multicasting technology then is to realize the IP transmission technology of point to multiple spot in wide area network.
The eighties in 20th century, the doctor Steve Deering of Stanford University begun three layers of multicasting technology research and with delivered its thesis for the doctorate---" multicast in a kind of datagram network " in December, 1991, multicast group managing I GMP agreement and the multicast path basis by the DVMRP agreement has been described in this paper, success multicasting technology is advanced to the IP layer.Exploration about the IP multicasting technology is being carried out always, and on doctor's Deering basis, people have finished PIM multicast routing protocols such as (Protocol Independent Multicast agreements) successively, thereby push multicast protocol to whole the Internet.The basic thought of multicast route technology is in the duplicated multicast data just now from the nearest ground of recipient, so network bandwidth in the time of can saving the transmission of a large amount of repeating datas greatly, thereby increasing people believes, in broadband internet is from now on used, multicasting technology will become one of primary circuit routing agreement of multimedia data communication.
The PIM agreement is present widely used multicast routing protocol, and wherein the PIM-SM agreement is the wherein main agreement of using.Fig. 1 adopts the multicast packet of PIM-SM agreement to send schematic diagram.As shown in Figure 1, the PIM-SM agreement can adopt shared tree to carry out transmitting multicast data, in a shared tree, a central point is arranged, and is responsible for sending multicast data message to all recipients of a multicast group.When multicast source sends data, data at first will send to this central point (diagram router B) by first hop router (diagram router-A) that links to each other with multicast source, then by this central point to other recipients along shared tree multicast data forwarding message, this central point is called meeting point (Rendezvous Point is called for short RP).In the network a plurality of RP can be arranged, be called candidate RP.But in a pim-sm domain, multicast group only and unique RP correspondence.After this RP lost efficacy for a certain reason, select new RP automatically by the RP election mechanism and be this group service.
The process that sends data to RP from the multicast packet source is called registration process the PIM-SM agreement, because registration process is that clean culture sends to this central point in the protocol massages by data message is encapsulated in, thereby can not carry out hardware and transmit, so forward efficiency is lower, thereby when reality was used, people wished that this process is short more good more.When the multicast registration message that has encapsulated multicast packet arrives RP, RP can send to the router that links to each other with multicast source and join message, the shortest path multicast transmit tree of establishment from first hop router of multicast source to RP, in case this forwarding tree is set up successfully, data arrive RP along this forwarding tree, and RP can send stopped registration messages and finish the multicast registration state to first hop router of multicast source.
In the PIM-SM agreement, the obtaining and distribute by BSR message and candidate RP notification packet and undertaken of RP information, BSR is the english abbreviation of BootStrap Router, it is a kind of router that defines in the PIM-SM agreement, is used for diffusion and safeguard RP information.The BSR message is the message that BSR sends, include all the RP information in the whole pim-sm domain in this message, all-router in pim-sm domain all receives the RP information in this message, and utilize this information to finish the renewal of self RP collection, the RP notification packet is the protocol massages that candidate rp router sends, candidate rp router regularly sends to BSR to RP information, is broadcast to whole pim-sm domain by BSR then, and this process sees that Fig. 2 illustrates.
When RP finishes disaster recovery functionality by the mode of automatic election, can cause multicast path by concussion, a RP often provides service for a plurality of groups, when RP switches, the multicast source of all relevant groups all can be initiated new registration process to new RP, and the front said that the efficient of this registration process was lower, if can not finish registration process as soon as possible, will seriously reduce systematic function.At present the PIM-SM protocol definition under the situation of system stability, guarantee the mechanism of each router RP information unanimity, but it can't guarantee also to make when RP switches the RP information on each router to guarantee unanimity, can't guarantee that especially the information on the non-BSR router of BSR and other is consistent.
Below with reference to Fig. 3 the situation that causes the RP information inconsistency is carried out brief description.The schematic diagram of Fig. 3 is used to illustrate the situation that causes the RP information inconsistency.In network shown in Figure 2 was formed, router C was BSR, and router B and C are candidate RP, and for multicast group G, elected RP is router C.Finish registration process by multicast source S to router C at first, so that multicast packet is normally transmitted.When router C owing to breaking down or network blockage when being cancelled elected RP qualification, can know at first that as the router C of BSR own RP change in information and RP information are overtime, router C can be automatically changeb to the RP of multicast group G the nearer router B apart from multicast group G like this, but the RP information on this moment router-A and the B still is C.If this moment, multicast source S continued to send multicast packet to multicast group G, then logon message can be sent to router C through router-A and B, but because C has not been RP, so it does not handle logon message.Owing to can not receive the stopped registration messages that router C responds, router-A can continue to send a large amount of PIM-SM Login messages to router C.Through behind the certain hour, because the BSR message from router C that router-A is received does not comprise the RP information of router C, so the RP information of the router C in the router-A is overtime, the RP of multicast group G correspondence recomputates.Therefore, after overtime, the RP information of A, B, three routers of C could be consistent, and A sends logon message to B then, and B responds stopped registration messages, and the multicast route recovery is normal.By top description as can be seen, after router C went up the RP change, router-A is finally finished the study that changes back RP information needed a period of time, and during this period of time, the RP information between each router and the BSR router is inconsistent.
In the PIM-SM agreement, spell out, " comprise the time that RP exists in the BSR message; each router is collected RP information from the BSR message after; must be updated to local RP time-out time to RP time-out time value in the BSR message ", but agreement is stipulated again, " after router receives the BSR message,, then to delete this RP information " if do not comprise local RP information in the BSR message.In fact, the latter is defined in the concussion that will cause RP when BSR switches, and does not therefore realize this regulation in actual applications mostly.Like this, in order to reduce the concussion of RP, mainly should consider from the time-out time aspect of RP.
There is a kind of method can be used for reducing the concussion of RP in the prior art.This method central idea is that RP time-out time in the BSR message and the local RP time-out time on the BSR are consistent, and its specific practice is that the time-out time of the local RP on the BSR is write in the BSR message.So just can guarantee to make the all-router RP information in the pim-sm domain to be consistent substantially substantially.But because the RP maintenance information on the BSR relies on the RP notification packet to refresh, if the BSR router sends the BSR message after receiving the RP announcement again, wherein the default value of the retention time of RP is about 150 seconds, if but the time cooperation is bad.Just receive the RP notification packet after sending the BSR message, the retention time so wherein is 90 seconds, that is to say, this RP information the retention time on other routers between 90 to 150 seconds.Because the BSR message is default is message of transmission in per 60 seconds, if the situation of BSR message dropping takes place like this, other routers will wait 120 seconds and just can receive second BSR message, so this scheme is too responsive to losing of BSR message, originally be for solving the scheme of the inconsistent proposition of RP, cause the RP concussion on the contrary, thereby this scheme there is bigger limitation.
Consider worst case, below just existing method each step and state are done an explanation according to the time:
1. relative time is 0 second
BSR receives the notification packet of RP, and the last RP time-out time of BSR is 150 seconds.
2. relative time is 60 seconds
BSR sends the BSR message, and the RP time-out time on the current BSR is 90 seconds, so the time-out time of RP is 90 seconds in the BSR message that sends.
Other routers are received the BSR message, and the corresponding RP time-out time of acquiring is set to 90 seconds.
3. relative time 60+1 second
BSR receives the RP notification packet, and the RP time-out time reset to 150 seconds.
4. relative time is 120 seconds
BSR sends the BSR message, and the time-out time of RP is 90 seconds, and other routers are not when receiving the BSR message, and the RP time-out time has become 30 seconds, receive the BSR message after, the RP time-out time reset to 90 seconds.
When please noting for the 4th step, when other routers are not received the BSR message, the RP time-out time has become 30 seconds, if a BSR packet loss is arranged, can be after 60 seconds when then other routers are received next BSR message, RP on it is just overtime like this, and this thus scheme is very responsive to losing of BSR message.
Summary of the invention
The present invention makes at existing the problems referred to above in the prior art, a kind of method that can improve the robustness of multicast PIM-SM protocol network that provides is provided, this method guarantees the unanimity of RP information by dynamic adjustment transmitting time, thereby guaranteed the unanimity of each router RP information when RP switches, guaranteed to make router that the BSR message lost not too that sensitivity can't cause the concussion of RP information simultaneously.
To achieve these goals, the invention provides a kind of method that improves the robustness of multicast PIM-SM protocol network, this method may further comprise the steps: 1) when needs send bootstrap router message, BootStrap Router takes out the meeting point time-out time of self; 2) BootStrap Router compared the meeting point time-out time and a scheduled time of described taking-up; 3) when the meeting point of described taking-up time-out time during more than or equal to described scheduled time, the meeting point time-out time in the BootStrap Router bootstrap router message to be sent is set to the meeting point retention time; And 4) when the meeting point of described taking-up time-out time during less than described scheduled time, the meeting point time-out time in the BootStrap Router bootstrap router message to be sent is set to the local meeting point time-out time on the meeting point.
In said method, the described scheduled time can obtain by following formula:
The scheduled time=second transmission blanking time+n of RP notification packet,
Wherein the value of n should be 1---between (the RP notification packet sends blanking time/2)
In this case, described RP message sends between blanking time and preferably calculates as follows:
The RP message sends the retention time ÷ 2.5 of blanking time=RP
In said method, described n value preferably is taken as 10.
In addition, in said method, the value of retention time of described RP is preferably 150 seconds.
Beneficial effect of the present invention is, it is simple, can overcome the multicast route oscillation that the BSR message dropping causes in the existing scheme, effectively guaranteed the unanimity of the whole network RP information again, improved the robustness of multicast PIM-SM protocol network, the part of failing to relate in the multicast PIM-SM agreement has been done preferably replenished.
Description of drawings
By the explanatory note of making below in conjunction with accompanying drawing, it is clearer that above-mentioned purpose of the present invention, advantage and feature will become, in following accompanying drawing:
Fig. 1 is that PIM-SM protocol groups multicast data is transmitted schematic diagram along shared tree;
Fig. 2 is the schematic diagram that adopts the pim-sm domain of PIM-SM agreement;
The schematic diagram of Fig. 3 is used to illustrate the situation that causes the RP information inconsistency;
Fig. 4 is the flow chart of the method that is consistent according to the described meeting point information that makes multicast PIM-SM agreement of the embodiment of the invention.
Embodiment
Fig. 4 is the flow chart of the method that is consistent according to the described meeting point information that makes multicast PIM-SM agreement of the embodiment of the invention, as shown in Figure 4, when the BSR router sends the BSR message, the time-out time of the RP of first taking-up own, and according to formula
The second transmission of time threshold=RP notification packet blanking time+n
Wherein the value of n should be 1---between (the RP notification packet sends blanking time/2)
Computing time threshold value, in actual the use, if network performance is fine, operation PIM-SM router is few, the n value can be got a little bit smaller, otherwise can get more greatly.
In the present embodiment, for ease of handling, preferably getting the n value is 10 seconds.
In the present embodiment, the retention time of getting RP is 150 seconds, and the transmission of RP notification packet is calculated blanking time as follows:
The retention time ÷ 2.5 of the transmission blanking time=RP of RP notification packet
Wherein 150 seconds and 2.5 all is the recommendation of PIM-SM agreement, also can adopt other numerical value under the prerequisite of agreement spirit.
Like this, just having obtained the time threshold values is 70 seconds.If the time-out time of the last RP of BSR is greater than this threshold value, retention time of getting RP of the time-out time in the RP message then, otherwise the time-out time in the RP message is got the current time-out time of RP, set the RP time-out time after, send the BSR message.
Further supposition BSR sent a message in per 60 seconds.
Consider worst case, below with regard to this method according to the time each the step and state do an explanation:
1. relative time is 0 second
BSR receives the notification packet of RP, and the last RP time-out time of BSR is 150 seconds.
2. relative time is 60 seconds
BSR sends the BSR message, and the RP time-out time on the current BSR is 90 seconds, and time threshold is (150 ÷ 2.5+10=70) 70 seconds, so the time-out time of RP is 150 seconds retention times of RP in the BSR message that sends.
Other routers are received the BSR message, and the corresponding RP time-out time of acquiring is set to 150 seconds.
3. relative time 60+1 second
BSR receives the RP notification packet, and the RP time-out time reset to 150 seconds.
4. relative time is 120 seconds
BSR sends the BSR message, and the time-out time of RP is 90 seconds, and other routers are not when receiving the BSR message, and the RP time-out time became (150-60=90) 90 seconds, receive the BSR message after, the RP time-out time reset to 150 seconds.
Contrast original scheme, as can be seen, in step 4, if BSR message dropping, RP time-out time on other routers continued to reduce from 90 seconds, can wait until that next BSR message sends over the time-out time that refreshes RP again after 60 seconds, that is to say that this scheme can be tolerated losing of a BSR message in the worst case.
From another aspect, when RP is overtime, the RP of other routers is overtime also to carry out together with the step, because the RP time-out time on the BSR is less than 70 seconds the time, the RP time-out time that sends in the BSR message is that BSR goes up the actual time-out time of RP, so can guarantee the router RP information unanimity in the pim-sm domain.
Step then,
5. relative time 120+1 second
BSR does not receive the notification packet of RP, and the RP time-out time on it is 90 seconds.
6. relative time is 180 seconds
The last RP notification packet of still not receiving of BSR, the RP time-out time on it is 30 seconds, and like this, the BSR message will send, and the time-out time of RP is less than threshold value, and then the time-out time of RP is the time-out time 30 seconds that BSR goes up RP in the message.Other routers are received this message, and the RP time-out time of oneself is set to 30 seconds.
7. relative time is 210 seconds
The last RP of BSR is overtime, and RP is also overtime on other routers, all-router RP information unanimity.
Below, the situation when n is got endpoint value is analyzed.
In the time of n=1, promptly in this example when BSR goes up the RP time-out time less than 61 seconds, the RP time-out time is the RP time-out time on the BSR in the BSR message.
1. relative time is 0 second
BSR receives the notification packet of RP, and the last RP time-out time of BSR is 150 seconds.
2. relative time is 60 seconds
BSR sends the BSR message, and the time-out time of RP is 90 seconds, and greater than threshold value 61 seconds, so the time-out time of RP is 150 seconds in the message, other routers were received this BSR message, and the RP time-out time of self is set to 150 seconds.
3. relative time 60+1 second
BSR receives new RP notification packet, and the RP time-out time is re-set as 150 seconds
As long as RP and BSR are normal, then step 2,3 will repeat always.RP time-out time on other routers changed between 90 to 150 seconds always, and is visible so long as not continuous BSR message dropping, just can not cause that RP's on other routers is overtime.
Consider the processing under the overtime situation of RP below, promptly candidate RP no longer sends the RP notification packet.
Connect face step 2:
4. relative time is 120 seconds
The last RP time-out time of BSR is 90 seconds, sends the BSR message, and the RP time-out time is 150 seconds.
5. relative time is 180 seconds
The last RP time-out time of BSR is 30 seconds, less than time threshold, sends the BSR message, and the RP time-out time is the actual time-out time 30 seconds that BSR goes up RP.
6. relative time is 210 seconds
RP on BSR and other routers is simultaneously overtime, and the RP information of each router is consistent
Therefore in this case, get endpoint value 1 and can guarantee the stationary problem of losing tolerance and solution RP to the BSR message, consider another situation now again, promptly the RP time-out time is in 61 seconds on BSR, the situation of transmission BSR message:
1. when the last RP time-out time of BSR is 61 seconds, send the BSR message, because be not lower than time threshold, the RP time-out time is 150 seconds in the message, and other routers RP time-out time that receives the BSR message was changed to 150 seconds.
2.60 after second, next BSR message will send, this is that the last RP time-out time of BSR is 1 second, is lower than time threshold, and the RP time-out time in the message is 1 second, and after other routers were received this message, the time-out time of RP changed 1 second into.
3.1 after second, the RP on the RP on the BSR and other routers is overtime.
Therefore under endpoint value is 1 situation, ideally can both guarantee on each router RP synchronously with to the discontinuous tolerance of losing of BSR message, but consider network delay and device processes the time-delay can't be quantitative, when the step 2 of latter event sends the BSR message, RP own that might be is overtime, just may not comprise the RP information that this is overtime in the BSR message like this, thereby the time-out time of RP other routers in the correct surely multicast domain that is published to PIM-SM that differed in 1 second, so should this boundary value of careful use.
When n=(transmission blanking time/2 of RP notification packet) time, when promptly n was 30 seconds in this example, time threshold was the process under 90 seconds the situation:
1. relative time is 0 second
BSR receives the notification packet of RP, and the last RP time-out time of BSR is 150 seconds.
2. relative time is 60 seconds
BSR sends the BSR message, and the time-out time of RP is 90 seconds, is not less than threshold value 90 seconds, so the time-out time of RP is 150 seconds in the message, other routers are received this BSR message, and the RP time-out time of self is set to 150 seconds.
3. relative time 60+1 second
BSR receives new RP notification packet, and the RP time-out time is re-set as 150 seconds.
As long as RP and BSR are normal, then step 2,3 will repeat always.RP time-out time on other routers changed between 90 to 150 seconds always, so when the n value gets 30 in this example, discontinuous the losing of chance that can tolerate BSR.
Connect face step 3, if candidate RP no longer sends the RP notification packet to BSR, the RP on the BSR will be overtime:
4. relative time is 120 seconds
The last RP time-out time of BSR is 90 seconds, because time-out time is not less than threshold value, so send the BSR message, the time-out time of RP is 150 seconds in the message.
5. relative time is 180 seconds
The last RP time-out time of BSR 30 seconds, less than threshold value 90 seconds, so the RP time-out time is set to 30 seconds in the BSR message that sends, after other routers were received this message, time-out time was set to 30 seconds.
6. relative time is 210 seconds
RP on the last RP of BSR and other routers is simultaneously overtime.
So n value capping value (RP notification packet transmitting time/2) time, still can guarantee the unanimity of RP information on each router again.
Thereby as can be seen from the above description, the benefit of this scheme is when the BSR message takes place to lose once in a while, to receive BSR message common multicast router and can tolerate losing of this message, and can not cause the concussion of RP information.
In addition, the preferred embodiments of the present invention are described for illustrative purposes, rather than limitation of the present invention.One of ordinary skill in the art should be appreciated that under the situation that does not break away from scope and spirit of the present invention different improvement, increase and decrease all are possible, and they are also all limited by claim of the present invention.
Claims (7)
1. method that improves the robustness of multicast PIM-SM protocol network, this method may further comprise the steps:
1) when needs send bootstrap router message, BootStrap Router takes out the meeting point time-out time of self;
2) BootStrap Router compared the meeting point time-out time and a scheduled time of described taking-up;
3) when the meeting point of described taking-up time-out time during more than or equal to described scheduled time, the meeting point time-out time in the BootStrap Router bootstrap router message to be sent is set to the meeting point retention time; And
4) when the meeting point of described taking-up time-out time during less than described scheduled time, the meeting point time-out time in the BootStrap Router bootstrap router message to be sent is set to the local meeting point time-out time on the meeting point.
2. method according to claim 1 is characterized in that, the described scheduled time obtains by following formula:
The scheduled time=the meeting point notification packet send the blanking time+n second
Wherein the span of n is 1 between (meeting point notification packet send blanking time/2).
3. method according to claim 2 is characterized in that, described n value gets 10.
4. according to the described method of any one claim in the claim 1,2 or 3, it is characterized in that the time value that the described meeting point retention time allows for the PIM-SM agreement.
5. method according to claim 4 is characterized in that, the described meeting point retention time is 150 seconds.
6. according to the described method of any one claim in claim 2 or 3, it is characterized in that described meeting point notification packet sends blanking time and there is certain proportionate relationship in the described meeting point retention time.
7. method according to claim 6 is characterized in that, the described meeting point retention time is 2.5 times that described meeting point notification packet sends blanking time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031499996A CN100499635C (en) | 2003-08-04 | 2003-08-04 | Method for improving robustness of group-playing PIM-SM protocol network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031499996A CN100499635C (en) | 2003-08-04 | 2003-08-04 | Method for improving robustness of group-playing PIM-SM protocol network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1581870A true CN1581870A (en) | 2005-02-16 |
| CN100499635C CN100499635C (en) | 2009-06-10 |
Family
ID=34579753
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB031499996A Expired - Fee Related CN100499635C (en) | 2003-08-04 | 2003-08-04 | Method for improving robustness of group-playing PIM-SM protocol network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100499635C (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100421415C (en) * | 2006-03-16 | 2008-09-24 | 杭州华三通信技术有限公司 | Method for decreasing group broadcasting service delay |
| WO2008122234A1 (en) * | 2007-04-04 | 2008-10-16 | Huawei Technologies Co., Ltd. | Mothod for handling three-layered network's interface state and three-layered network equipment |
| CN100444585C (en) * | 2006-07-24 | 2008-12-17 | 杭州华三通信技术有限公司 | Network equipment and method for realizing sparse mode protocol unrelated group broadcasting field hierarchy |
| WO2009065359A1 (en) * | 2007-11-23 | 2009-05-28 | Huawei Technologies Co., Ltd. | Bootstrap router, and method and system for timeout management |
| CN101411120B (en) * | 2006-01-25 | 2012-10-31 | 法国电信公司 | Burn-in system for multicast data transmission |
| CN102855923A (en) * | 2011-07-02 | 2013-01-02 | 龙岩市新罗区智电电子厂 | Intelligent music play device |
| CN103634219A (en) * | 2013-11-27 | 2014-03-12 | 杭州华三通信技术有限公司 | Maintaining method and device for Anycast-RP (rendezvous point) |
| CN104202240A (en) * | 2014-07-30 | 2014-12-10 | 上海斐讯数据通信技术有限公司 | Method of accelerating RP (Rendezvous Point) switchover |
| CN104301033B (en) * | 2014-08-26 | 2017-01-25 | 国家电网公司 | Electric power optical fiber communication network robustness indicator evaluation method |
-
2003
- 2003-08-04 CN CNB031499996A patent/CN100499635C/en not_active Expired - Fee Related
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101411120B (en) * | 2006-01-25 | 2012-10-31 | 法国电信公司 | Burn-in system for multicast data transmission |
| CN100421415C (en) * | 2006-03-16 | 2008-09-24 | 杭州华三通信技术有限公司 | Method for decreasing group broadcasting service delay |
| CN100444585C (en) * | 2006-07-24 | 2008-12-17 | 杭州华三通信技术有限公司 | Network equipment and method for realizing sparse mode protocol unrelated group broadcasting field hierarchy |
| WO2008122234A1 (en) * | 2007-04-04 | 2008-10-16 | Huawei Technologies Co., Ltd. | Mothod for handling three-layered network's interface state and three-layered network equipment |
| WO2009065359A1 (en) * | 2007-11-23 | 2009-05-28 | Huawei Technologies Co., Ltd. | Bootstrap router, and method and system for timeout management |
| CN101442474B (en) * | 2007-11-23 | 2011-12-21 | 华为技术有限公司 | Bootstrap router and method and system for managing overtime time |
| CN102855923A (en) * | 2011-07-02 | 2013-01-02 | 龙岩市新罗区智电电子厂 | Intelligent music play device |
| CN102855923B (en) * | 2011-07-02 | 2016-11-02 | 龙岩市新罗区智电电子厂 | Intelligent music play device |
| CN103634219A (en) * | 2013-11-27 | 2014-03-12 | 杭州华三通信技术有限公司 | Maintaining method and device for Anycast-RP (rendezvous point) |
| CN103634219B (en) * | 2013-11-27 | 2017-03-08 | 杭州华三通信技术有限公司 | A kind of maintaining method of Anycast Rendezvous Point Anycast RP and device |
| CN104202240A (en) * | 2014-07-30 | 2014-12-10 | 上海斐讯数据通信技术有限公司 | Method of accelerating RP (Rendezvous Point) switchover |
| CN104301033B (en) * | 2014-08-26 | 2017-01-25 | 国家电网公司 | Electric power optical fiber communication network robustness indicator evaluation method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100499635C (en) | 2009-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1777149A (en) | Method for realizing multicast translation in three-layer switching unit | |
| CN1237755C (en) | Subgroup multicasting in communications network | |
| CN1791054A (en) | Virtual special network multicast method by virtual router mode | |
| CN1816010A (en) | Multicasting source filtering treatment method | |
| CN1878143A (en) | Multicast network deploying method and multicast network | |
| CN1816011A (en) | Data transfer apparatus and multicast system and program | |
| CN1551568A (en) | Reliable delivery of multi-cast conferencing data | |
| CN1868178A (en) | Packet distribution control method | |
| CN1607783A (en) | Processing broadcast data in a mobile ac-hoc network | |
| CN101030943A (en) | Method for transmitting message and route | |
| CN1169224A (en) | Multi-processor environments | |
| CN1747447A (en) | IP group broadcasting method for supporting different service quality in specification service network domain | |
| CN1567837A (en) | A method and system for multicast source control | |
| CN1243430C (en) | Method for realizing registration from multicast source to collection point | |
| CN1845527A (en) | Method and system for providing multicast service in microwave access global intercommunication system | |
| CN101043429A (en) | Method for establishing multicasting LSP in MPLS field and multicasting data communication system | |
| CN1581870A (en) | Method for improving robustness of group-playing PIM-SM protocol network | |
| CN101047881A (en) | Method and system for providing multicast bear | |
| CN1731756A (en) | Method and device for processing user to leave, switching multicast service channel request using slow leaving mechanism | |
| CN1588927A (en) | Method for large scale multimedia cut-in net gate | |
| CN101043436A (en) | Method for improving communication quality based on label distribution protocol | |
| CN1414740A (en) | Centralized management method of local net exchange equipment | |
| CN101052004A (en) | Multicast transmission method based on virtual distribution net in network | |
| CN1798098A (en) | Method of differentiating multiple services for anti IP data stream in multicast to impact communication system | |
| CN101035088A (en) | Method, system and access device for realizing the intercommunication of two layers of local specific service |
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: 20090610 Termination date: 20160804 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |