WO2008122234A1 - Procédé de gestion d'états d'interface de réseau à trois couches et équipement de réseau à trois couches - Google Patents

Procédé de gestion d'états d'interface de réseau à trois couches et équipement de réseau à trois couches Download PDF

Info

Publication number
WO2008122234A1
WO2008122234A1 PCT/CN2008/070636 CN2008070636W WO2008122234A1 WO 2008122234 A1 WO2008122234 A1 WO 2008122234A1 CN 2008070636 W CN2008070636 W CN 2008070636W WO 2008122234 A1 WO2008122234 A1 WO 2008122234A1
Authority
WO
WIPO (PCT)
Prior art keywords
state
refresh message
interval
data
duration
Prior art date
Application number
PCT/CN2008/070636
Other languages
English (en)
French (fr)
Inventor
Xinlong Li
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008122234A1 publication Critical patent/WO2008122234A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast

Definitions

  • the present invention relates to the field of network technologies, and in particular, to a method for processing an interface state of a layer 3 network device and a layer 3 network device.
  • PIM-DM Protocol Independent Multicast-Dense Mode
  • PIM-DM Protocol Independent Multicast-Dense Mode
  • the members of the multicast group are relatively dense.
  • PIM-DM assumes that each subnet in each network has at least one receiving station interested in the multicast source, so the multicast packet is spread to All the points in the network.
  • PIM-DM The working process of PIM-DM can be summarized as follows: Neighbor discovery: In PIM-DM, the multicast router needs to use Hello messages to discover neighbors and maintain neighbor relationships. Build a Shortest Path Tree (SPT) tree and build an SPT. The process of the tree is also Flooding & Prune, forming a multicast forwarding tree rooted at the multicast source; Graft, when the pruned downstream node needs to be restored to the forwarding state, the node The grafting message is used to notify the upstream node to send upstream to the hop by hop. The upstream router receives the graft message and resumes forwarding data traffic. Reverse path forwarding (RPF) checks, when the data packet arrives, the correctness of the arrival path is performed.
  • RPF Reverse path forwarding
  • FIG. 1 is a schematic diagram of a conventional multicast network. In the multicast network shown in Figure 1, the multicast source continuously sends multicast data.
  • Router A In the link between Router A and Router B in Figure 1, the same packet is repeatedly sent. Router A and Router B respectively. Upon receiving the multicast data on the inbound interface, the two routers will elect a unique data forwarder router A through the Assert mechanism, which is called the winner. Router B is called the loser, and Router B will put the outbound interface. (Interface 1 of Router B) Deletes from the outbound interface list and sends a Prune message to Router A. The Hold time field in the message is assigned the default value of 180 seconds, or the Interval field in the status refresh message is received. The default of 60 seconds is also 180 seconds. The outgoing interface of Router A receives the Prune message and starts the PmnePending timer.
  • the outgoing interface of Router A (interface 1 of Router B) is deleted from the outbound interface list, the outgoing interface enters the Prune state, and the timeout time of the Prune timer of Router A is set.
  • Time Prune messages received in the router B sends a specified Hold Time field, that is received router B sends a Prune message Hold Time field 180 seconds.
  • the first hop router periodically sends a status refresh message.
  • the router A resets the Prune timer of the outbound interface. The timeout period of the outbound interface of the router A remains unchanged.
  • the Prune flag is added to the status refresh message, and is sent to the outbound interface of Router B.
  • the outbound interface of Router B receives the message. Because this is the message sent by the winner, the Assert timer timeout is updated to the status refresh message. 3 times the time interval in the message.
  • the inventors have found that at least the following problems exist in the prior art: If the first hop router, the user changes the transmission time interval of the state refresh message to be larger, for example, 200 seconds, The Prune timer on the outbound interface of Router A only resets the timeout timer when forwarding the status refresh message.
  • the outbound interface of Router B receives the status refresh message and sets the Assert timer to three times 200 times, that is, 600 seconds. After 180 seconds, the Prune timer of the outbound interface of Router A expires.
  • the outbound interface of Router A is added to the outbound interface list.
  • the Graft message is sent upwards and sent to the first hop router hop by hop.
  • the multicast forwarding tree is re-established. In the case that there is no real data receiver downstream, the multicast routing entry is incorrect and will not be restored to the correct state.
  • the multicast traffic data will be sent to Router A and the shared network segment, causing a huge waste of network bandwidth. .
  • An object of the embodiments of the present invention is to provide a method for processing an interface state of a three-layer network device and three
  • the layer network device is configured to avoid waste of network bandwidth resources caused by an error in the outbound interface list of the layer 3 network device when the first hop network device changes the interval of the state refresh message sending interval.
  • an embodiment of the present invention provides a method for processing an interface state of a layer 3 network device, including: receiving a state refresh message; if the outbound interface for forwarding the multicast data is in a state of stopping forwarding data, and If the duration of the outbound data forwarding state is less than the preset multiple of the state refresh message sending interval, the duration of the outbound interface in the state of stopping the forwarding data is updated to a preset multiple of the interval of the state refresh message sending interval.
  • An embodiment of the present invention provides a Layer 3 network device, including: a receiving unit, configured to receive a status refresh message, and a determining unit, configured to determine, when the receiving unit receives the status refresh message, a forwarding group Whether the outgoing interface of the broadcast data is in the state of stopping the forwarding of data; the comparing unit, the preset multiple of the duration for stopping the forwarding of the data state and the sending interval of the state refreshing message; and the preset multiple of the interval of the sending interval of the state refreshing message
  • the duration of the outbound interface in the state of stopping forwarding data is updated to a preset multiple of the duration of the state refresh message sending interval.
  • the Layer 3 network device when the Layer 3 network device forwards the message after receiving the state refresh message, if the outbound interface that forwards the multicast data is in the state of stopping the forwarding of the data, and the outbound interface is in the state of stopping the forwarding state, the duration is smaller than the state refresh message.
  • the preset multiple of the interval duration is updated to the preset multiple of the interval of the state refresh message sending interval, and thus the multicast data is forwarded when the sending interval of the state refresh message is changed.
  • the timeout period of the outbound interface is also updated accordingly. Therefore, the entry of the outbound interface list does not generate an error, thus avoiding the phenomenon that the multicast data forwarded by the Layer 3 network device does not have a receiver in the network.
  • FIG. 1 is a schematic diagram of a multicast network in the prior art
  • FIG. 3 is a schematic diagram of an apparatus according to an embodiment of the present invention.
  • the method includes: receiving a status refresh message; if the outbound interface that forwards the multicast data is in the state of stopping forwarding data, and the time when the outbound interface is in the state of stopping forwarding data is smaller than the status refresh message sending interval
  • the method may further include: if the outbound interface that forwards the multicast data is in the state of stopping the forwarding of the data, and the length of the outbound interface being in the state of stopping the forwarding of the data and the interval of sending the state refresh message If the preset multiples are the same, the outbound interface is changed from the stop forwarding data state to the forwarding data state.
  • the duration of the status refresh message transmission interval can be determined in a variety of ways.
  • the duration of the state refresh message sending interval may be obtained from the received state refresh message.
  • the duration of the state refresh message sending interval may be carried in the interval (Interval) field of the state refresh message.
  • the time interval for receiving the state refresh message may be counted, and the duration of the state refresh message sending interval may be determined according to the statistical result.
  • the status refresh message can be the State Refresh Message specified by the IETF rfc3973 protocol.
  • the format of the State Refresh Message is as follows:
  • PIM State Refresh Messages have the following format:
  • PIM Ver PIM version number, currently 2 Type: Type 9, indicating state refresh message
  • Multicast Group Address Multicast Group Address
  • Source Address Source Address
  • Metric Prefence Metric Priority
  • Interval Interval, filled by the first hop router, forwarded by other routers
  • the duration of the status refresh message transmission interval may be carried in the Interval field in the above format.
  • the preset multiple of the state refresh message transmission interval duration is three times the duration of the state refresh message transmission interval.
  • the preset multiple of the status refresh message sending interval may be greater than 180 seconds.
  • the execution body of each step in the foregoing method may be a layer 3 network device, that is, a state in which the layer 3 network device processes the forwarding multicast data interface.
  • a process provided by an embodiment of the present invention is as follows:
  • step 202 If the status refresh message is forwarded, the outbound interface for forwarding the multicast data is stopped for the transmission interval, and the process proceeds to step 203 or 204;
  • the Layer 3 network device may be a router or a switch.
  • the Layer 3 network device when the Layer 3 network device is a router, the specific process of the foregoing method is as follows: 11): The router periodically receives a state refresh message, and the state refresh message is generated by the first hop router and spread to the entire network;
  • Router A When Router A receives the prune message sent by Router B, if there is no data receiver downstream, the outgoing interface of the forwarded multicast data of Router A is deleted from the outbound interface list, and the outgoing interface of Router A's forwarding multicast data is cut.
  • the state of the branching time of the pruning timer of the outbound interface that is set;
  • the preset multiple of the time interval for receiving the status refresh message is compared with the length of time when the outbound interface of the router that forwards the multicast data is in the state of stopping the forwarding of the data, if the time when the outbound interface is in the state of stopping the forwarding of the data is less than A preset multiple of the interval at which the status refresh message is sent, a preset multiple of the interval. For example, when the router A receives the status update message, the outbound interface of the multicast data forwarded by the router A is in the prune state, and the timeout period of the prune timer is 180 seconds, and the sending period in the state refresh message is 200 seconds.
  • the timeout period of the pruning timer is updated to 600 seconds.
  • the pruning timer will time out after 600 seconds, the protocol state is changed, and the state refresh message is sent every 200 seconds. Once, the pruning timer is refreshed, and the timeout period for resetting the timer is 600 seconds later.
  • the outbound interface is re-added to the outbound interface list, and the outbound interface is changed from the stop forwarding data state to the forwarding data state.
  • the duration of the status refresh message sending interval may be carried in the status refresh message; or, the time interval for receiving the status refresh message may be counted, and the duration of the status refresh message sending interval may be determined according to the statistical result. .
  • join/prune message may be a Join/Prune Message according to the IETF rfc3973 protocol, and the format is as follows:
  • Type 3 indicates a Join/Prune message
  • Upstream Neighbor Address upstream neighbor address
  • Multicast Group Address Multicast Group Address Number of Joined Sources: Number of sources into a particular group
  • Number of Joined Sources Number of sources for pruning specific groups
  • the duration is set according to the sending interval of the received state refresh message, so when the state of the state refresh message is changed, The duration of the outbound interface in the state of stopping the forwarding of the data can be updated accordingly, thereby avoiding the problem of wasted network resources caused by the error of the outbound interface of the router.
  • Embodiment 2 When the Layer 3 network device is a Layer 3 switch, the specific process of the foregoing method is as follows:
  • the Layer 3 switch periodically receives the status refresh message, and the status refresh message is generated by the source Layer 3 switch and diffused to the entire network;
  • the preset multiple of the time interval for receiving the status refresh message is compared with the length of the outgoing interface of the set three-layer switch for forwarding the multicast data, if the outbound interface is in the state of stopping forwarding data.
  • the duration is less than a preset multiple of a preset multiple time interval of the time interval in which the status refresh message is sent;
  • the multiple of the preset may be three times according to the protocol.
  • the duration of the status refresh message sending interval may be carried in the status refresh message; or, the time interval for receiving the status refresh message may be counted, and the duration of the status refresh message sending interval may be determined according to the statistical result. . It can be seen from the embodiment that the length of the outbound interface for forwarding the multicast data of the Layer 3 switch is set according to the duration of the sending interval of the received state refresh message. The duration of the outbound interface in the state of stopping the forwarding of the data may be updated accordingly, thereby avoiding the problem of wasted network resources caused by the error of the outbound interface of the router.
  • the embodiment of the present invention further provides a three-layer network device, including: a receiving unit, configured to receive a state refresh message; and a determining unit, configured to: when the receiving unit receives the state refresh message, determine Whether the outbound interface of the forwarded multicast data is in the state of stopping the forwarding of data; the comparing unit is a preset multiple of the duration of the state in which the forwarding of the data is stopped and the interval of the sending of the state refreshing message; and the preset of the interval of the sending interval of the state refreshing message is smaller When the multiple is exceeded, the duration of the outbound interface in the state of stopping the forwarding of data is updated to a preset multiple of the duration of the state refresh message transmission interval.
  • the Layer 3 network device may further include: an interface state transition unit, configured to convert the outbound interface from a stop forwarding data state to a forwarding data state when the comparison unit has the same long preset multiple.
  • an interface state transition unit configured to convert the outbound interface from a stop forwarding data state to a forwarding data state when the comparison unit has the same long preset multiple.
  • the interface state transition unit can also be combined with the update unit into one functional unit.
  • the Layer 3 network device can be a router or a Layer 3 switch.
  • a preferred three-layer network device according to an embodiment of the present invention is described below with reference to FIG. As shown in Figure 3, it includes:
  • the receiving unit 301 is configured to periodically receive a status refresh message.
  • the determining unit 302 is configured to: when the receiving unit 301 receives the status refresh message, determine whether the outbound interface for forwarding the multicast data is in the state of stopping forwarding data; in the data state, determining the duration and state of the interface being in the state of stopping forwarding the data. The duration of the interval for sending the message is refreshed, and the preset multiple of the duration of the interface that stops the forwarding of the data state and the interval of the state refresh message sending interval is compared;
  • the updating unit 304 is configured to: when the comparison unit 303 compares that the elapsed interface is in a state of stopping the forwarding of the data, and the duration is less than a preset multiple of the duration of the state refresh message sending interval, the egress interface The duration of the stop forwarding data state is updated to a preset multiple of the duration of the state refresh message sending interval;
  • the interface state transition unit 305 is configured to: when the comparison unit 303 compares that the egress interface is in the state of stopping the forwarding data state and the preset multiple of the state refresh message sending interval duration, the outbound interface stops forwarding data. The state transitions to the forwarding data state.
  • the Layer 3 network device further includes:
  • the sending unit 306 is configured to: when the determining unit 302 determines that the outbound interface is in the state of stopping forwarding data, adding a flag for stopping forwarding data to the status refresh message and transmitting the flag.
  • the comparison unit 303 can determine the duration of the status refresh message transmission interval in a variety of ways. For example, the duration of the state refresh message sending interval may be obtained from the received state refresh message. Further, the duration of the state refresh message sending interval may be carried in an interval (Interval) field of the state refresh message. For example, the time interval for receiving the state refresh message may be counted, and the duration of the state refresh message sending interval may be determined according to the statistical result.
  • Interval interval
  • the duration of the status refresh message transmission interval may be carried in the Interval field in the above format. According to the agreement, the preset multiple of the status refresh message sending interval is three times the interval of the status refresh message sending interval. Optionally, the preset multiple of the status refresh message sending interval may be greater than 180 seconds.
  • the duration is smaller than the state refresh message.
  • the preset multiple of the interval of the interval is updated, and the duration of the outbound interface is updated to a preset multiple of the interval of the state refresh message sending interval. It can be seen that when the sending interval of the state refresh message is changed, the corresponding update is also updated. The length of time that the outbound interface is in the forwarding state. Therefore, no error occurs in the entries of the outbound interface list, thus avoiding the phenomenon that the multicast data forwarded by the Layer 3 network device does not have a receiver in the network. The problem of wasting network bandwidth resources caused by technology.

Landscapes

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

Description

处理三层网络设备接口状态的方法和三层网络设备
本申请要求于 2007 年 4 月 4 日提交中国专利局、 申请号为 200710090343. K 发明名称为"转变三层网络设备接口状态的方法和三层网络 设备"的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及网络技术领域、尤其涉及一种处理三层网络设备接口状态的方 法和三层网络设备。
背景技术
随着网络技术的不断发展， IP传输得到了越来越多的应用。 其中， 组播 技术作为一种有效的 IP 传输解决方案在很多方面显示出其特有的优势。 PIM-DM ( Protocol Independent Multicast-Dense Mode, 协议无关组播-密集模 式）， 属于密集模式的组播路由协议。 在这种网络环境下， 组播组的成员相对 比较密集 , PIM-DM假设每个网络中的每个子网都存在至少一个对组播源感兴 趣的接收站点 , 因此组播数据包被扩散到网络中的所有点。
PIM-DM的工作过程可以概括为： 邻居发现， 在 PIM-DM中， 组播路由 器需要使用 Hello消息来发现邻居， 并维护邻居关系； 构建最短路径树（SPT, Shortest Path Tree )树， 构建 SPT树的过程也就是扩散或剪枝（Flooding & Prune ), 形成一个以组播源为根的组播转发树； 嫁接（Graft ), 当被剪枝的下 游节点需要恢复到转发状态时，该节点使用嫁接消息通知上游节点，逐跳向上 游发送， 上游路由器收到嫁接消息， 恢复转发数据流量； 反向路径转发（RPF， Reverse Path Forwarding )检查， 当数据包到达时， 进行到达路径的正确性检 查；断言（Assert )机制，在共享网络中会出现相同报文的重复发送，通过 Assert 机制来选定一个唯一的转发者， 由优胜者负责转发数据， 而其他落选路由器则 剪掉对应的接口以禁止转发组播数据； 状态刷新机制 （ State Refresh Mechanism ), 状态刷新消息由第一跳路由器产生， 扩散到全网， 路由器接收 到状态刷新消息后， 减少数据泛滥和后续的剪枝消息，刷新协议状态机中的超 时定时器， 并更新出接口的剪枝状态和快速响应拓朴变化， 利用状态刷新机制 周期性的扩散到全网， 来代替周期性的扩散剪枝。 图 1为现有的一种组播网络示意图。在图 1所示的组播网络中，组播源持 续发出组播数据， 在图 1中的路由器 A和路由器 B之间的链路会出现相同报 文的重复发送， 路由器 A和路由器 B分别在入接口收到组播数据， 这两台路 由器会通过 Assert机制选举出唯一的一个数据转发者路由器 A, 称之为优胜 者， 路由器 B被称之为落选者， 路由器 B将会把出接口 （路由器 B的接口 1 ) 从出接口列表中删除， 同时会向路由器 A发送剪枝（Prune ) 消息， 消息中的 Hold time字段赋值为缺省的 180秒，或者收到状态刷新 文中 Interval字段 (缺 省 60秒） 的三倍也是 180秒， 路由器 A的出接口收到 Prune消息， 同时启动 剪枝延时 (PmnePending)定时器， 因为下游没有数据接收者， 最终剪枝延时 (PmnePending)定时器超时后， 路由器 A的出接口 （路由器 B的接口 1 )被从 出接口列表中删除， 出接口进入 Prune状态， 并将路由器 A的 Prune定时器的 超时时间设置为收到的路由器 B发送的 Prune消息中的 Hold Time字段所指明 的时间， 也就是收到路由器 B发送 Prune报文 Hold Time字段的 180秒。 在上 游， 由于第一跳路由器周期性的发送状态刷新消息， 路由器 A收到后， 会重 置自身出接口的 Prune定时器，路由器 A出接口 Prune定时器的超时时间保持 不变，并在收到的状态刷新消息中加上 Prune标志，向路由器 B的出接口发送， 路由器 B的出接口收到该消息， 因为这是优胜者发送来的消息，会更新 Assert 定时器超时时间为状态刷新消息报文中时间间隔的 3倍。
但是，在实现本发明的过程中 ,发明人发现现有技术中至少存在如下问题： 如果第一跳路由器上， 用户将状态刷新消息的发送时间间隔更改为较大， 比如 改为 200秒，这样在路由器 A出接口上的 Prune定时器在转发状态刷新消息时 只是重置超时定时器， 而路由器 B的出接口收到状态刷新消息后把 Assert定 时器设置为 200的 3倍即 600秒，这样在 180秒后，路由器 A的出接口的 Prune 定时器超时， 路由器 A的出接口重新加入出接口列表， 同时向上发送 Graft消 息， 并逐跳向上发送到第一跳路由器， 组播转发树重新建立起来， 在下游没有 真正的数据接收者情况下， 组播路由表项错误， 而且不会恢复为正确状态， 组 播流量数据会发送到路由器 A和共享网段， 造成了网络带宽的极大浪费。
发明内容
本发明实施例的目的是提供一种处理三层网络设备接口状态的方法和三 层网络设备， 用以在第一跳网络设备更改状态刷新消息发送间隔时长时，避免 因三层网络设备的出接口列表发生错误而造成网络带宽资源的浪费。
为解决上述技术问题，本发明实施例一方面提供了一种处理三层网络设备 接口状态的方法， 包括： 接收状态刷新消息； 如果转发组播数据的出接口处于 停止转发数据状态，且所述出接口处于停止转发数据状态的时长小于所述状态 刷新消息发送间隔时长的预置倍数，则将所述出接口处于停止转发数据状态的 时长更新为所述状态刷新消息发送间隔时长的预置倍数。
本发明实施例另一方面提供了一种三层网络设备， 包括： 接收单元， 用于 接收状态刷新消息； 判断单元， 用于在所述接收单元接收到所述状态刷新消息 时， 判断转发组播数据的出接口是否处于停止转发数据状态； 比较单元， 用于 停止转发数据状态的时长与状态刷新消息发送间隔的时长的预置倍数；更新单 所述状态刷新消息发送间隔时长的预置倍数时，将所述出接口处于停止转发数 据状态的时长更新为所述状态刷新消息发送间隔时长的预置倍数。
在本发明实施例中，三层网络设备在接收状态刷新消息后进行转发时， 如 果转发组播数据的出接口处于停止转发数据状态，并且该出接口处于停止转发 状态的时长小于状态刷新消息发送间隔时长的预置倍数，则将该出接口处于停 止转发状态的时长更新为状态刷新消息发送间隔时长的预置倍数， 由此可见， 当状态刷新消息的发送间隔被更改时 ,转发组播数据的出接口处于停止转发状 态的时长也相应的更新， 这样， 出接口列表的表项不会发生错误， 从而避免了 三层网络设备转发的组播数据在网络中没有接收者的现象，因此解决了现有技 术造成的浪费网络带宽资源的问题。
附图说明
图 1为现有技术的一种组播网络示意图；
图 2为本发明实施例提供的流程图；
图 3为本发明实施例提供的装置示意图。
具体实施方式
首先说明本发明实施例的处理三层网络设备接口状态的方法。所述方法可 以包括：接收状态刷新消息； 如果转发组播数据的出接口处于停止转发数据状 态 ,且所述出接口处于停止转发数据状态的时长小于所述状态刷新消息发送间
Figure imgf000006_0001
状态刷新消息发送间隔时长的预置倍数。 此外， 接收状态刷新消息之后， 所述 方法还可以包括： 如果转发组播数据的出接口处于停止转发数据状态，且所述 出接口处于停止转发数据状态的时长与所述状态刷新消息发送间隔时长的预 置倍数相同， 则将所述出接口由停止转发数据状态转变为转发数据状态。
所述状态刷新消息发送间隔的时长可以由多种方式确定。例如，可以从接 收的状态刷新消息中获取所述状态刷新消息发送间隔的时长，进一步来说，状 态刷新消息发送间隔的时长可以携带于所述状态刷新消息的间隔（ Interval )字 段。 再例如， 可以对接收所述状态刷新消息的时间间隔进行统计， 根据统计结 果确定所述状态刷新消息发送间隔的时长。
状态刷新消息可以是 IETF rfc3973协议规定的 State Refresh Message, State Refresh Message的格式如下：
PIM State Refresh Messages have the following format：
□ 1 Ξ 3
0 1 2 3 4 5 S 7 8 9 0 1 2 3 4 5 S 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I PIM Ver I Type I Reserved I Checksum I
I Multicast Group Address [Encoded Group Fornnat) I
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I Source Address (Encoded Unicast Format J I
I Originator: Address (Encoded Unicast Format) I
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I R I Metric Preference I
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I Metric I
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I Mask:丄 en I TTL I P I H I O I Reserved I Interval I
+-+ -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 各个字段的说明如下：
PIM Ver: PIM版本号， 目前为 2 Type: 类型 9, 表示 state refresh消息
Reserved: 予贞留
Checksum: 校验码
Multicast Group Address： 组播组地址
Source Address： 源地址
Originator Address: 第一跳路由器地址
R: 剪枝位
Metric Prefence: 度量优先级
Metric ： 度量
Masklen: 掩码长度
TTL: Time To Live生成时间
Interval: 时间间隔， 由第一跳路由器填充， 其他路由器转发
状态刷新消息发送间隔的时长可以携带于上述格式中的 Interval字段。 另夕卜，根据协议规定，状态刷新消息发送间隔时长的预置倍数为状态刷新 消息发送间隔时长的 3倍。可选的，状态刷新消息发送间隔时长的预置倍数可 以大于 180秒。
需要说明的是， 上述方法中的各个步骤的执行主体可以是三层网络设备， 即， 三层网络设备处理其转发组播数据接口的状态。
为使本发明的目的、技术方案及优点更加清楚明白， 以下参照附图并举实 施例， 对本发明实施例进一步详细说明。
请参见图 2， 本发明实施例提供的一个流程如下：
201 : 接收状态刷新消息；
202: 若转发所述状态刷新消息时， 转发组播数据的出接口处于停止转发 息发送间隔时长， 转步骤 203或 204;
203 : 当所述出接口处于停止转发数据状态的时长小于所述状态刷新消息 发送间隔时长的预置倍数时，将所述出接口处于停止转发数据状态的时长更新 为所述状态刷新消息发送间隔时长的预置倍数； 204: 当所述出接口处于停止转发数据状态的时长达到所述状态刷新消息 发送间隔时长的预置倍数时，将所述出接口由停止转发数据状态转变为转发数 据状态。
所述三层网络设备可以为路由器或者交换机，下面分别就这两种情况列举 实施例进行伴细说明。
实施例一， 当所述三层网络设备为路由器时， 上述方法的具体流程如下： 11 ): 路由器周期性的接收状态刷新消息， 状态刷新消息由第一跳路由器 产生， 并向全网扩散；
12 ): 当所接收的状态刷新消息需要在路由器的转发组播数据的出接口进 行转发时，如果路由器的转发组播数据的出接口从出接口列表删除，转发组播 数据的出接口处于停止转发数据状态，则确定所述出接口处于停止转发数据状 态的时长。 例如， 当路由器 A和路由器 B分别接收到组播数据， 两台路由器 选出路由器 A为优胜者对数据进行转发， 路由器 B把自身的转发组播数据的 出接口从出接口列表删除， 同时向路由器 A发送剪枝消息。 路由器 A接收到 路由器 B发送的剪枝消息时， 如果下游没有数据接收者， 最终路由器 A的转 发组播数据的出接口被从出接口列表删除， 路由器 A的转发组播数据的出接 口处于剪枝状态 , 获取设置的所述出接口的剪枝定时器的超时时间；
13 ): 对接收状态刷新消息的时间间隔的预置倍数与设置的路由器的转发 组播数据的出接口处于停止转发数据状态的时长进行比较，如果所述出接口处 于停止转发数据状态的时长小于发送状态刷新消息的时间间隔的预置倍数，则 间隔的预置倍数。 例如， 路由器 A接收到状态刷新消息时， 路由器 A的转发 组播数据的出接口处于剪枝状态，且剪枝定时器的超时时间为 180秒， 而状态 刷新消息中的发送周期为 200秒，通过检查 200秒的三倍大于 180秒， 则将剪 枝定时器的超时时间更新为 600秒， 这样， 剪枝定时器在 600秒后会超时， 转 变协议状态， 状态刷新消息每隔 200秒发送一次， 刷新剪枝定时器， 重置该定 时器的超时时间为 600秒以后的时间点。
14 ): 对接收状态刷新消息的时间间隔的预置倍数与设置的路由器的转发 组播数据的出接口处于停止转发数据状态的时长进行比较，当所述出接口处于 停止转发数据状态的时长达到所述状态刷新消息发送间隔时长的预置倍数时 , + + + + + + +
所述出接口 +被重新加入出接口列表，并将所述出接口由停止转发数据状态转变 为转发数据状态。
其中， 所述状态刷新消息发送间隔的时长可以在所述状态刷新消息中携 带； 或者， 可以对接收所述状态刷新消息的时间间隔进行统计， 根据统计结果 确定所述状态刷新消息发送间隔的时长。
需要说明的是， 加入 /剪枝消息可以是按照 IETF rfc3973 协议规定的 Join/Prune Message , 其格式如下：
+ +
G 1 2 3
+ + + + + + + +■ ■■
G 1 2 3 4 5 6 7 8 9 G 1 2 3 4 5 6 7 8 9 G 1 2 3 4 5 6 7 8 9 G 1
+- +■ +- ■+- ■+
+ + + + + + +
1 PIM Ver 1 Type I Reserved I Checksum 1
+- +■ +- ■+- ■+
1 Upstream Heighbor Address (Encoded Unicast Format ) 1
+- +■ +- ■+- ■+
1 Reserved I Nimi Groups I Hold Time 1
+- +■ +- ■+- ■+
+- +■ +- ■+- ■+
1 ulticsst Group Address 1 (Encoded Group Format ) 1
+- +■ +- ■+- ■+
1 Nimii er of Joined Sources I Nimii er of Pruned Sources 1
+- +■ + + + + + + + + +- ■+- ■+ 1 1
1 1 1 1
+- +■ +- ■+- ■+ 各个字段的说明如下：
PIM Ver: PIM版本号 , 目前为 2
Type: 类型 3, 表示 Join/Prune消息
Reserved:予贞留
Checksum:校验码
Upstream Neighbor Address:上游邻居地址
Reserved:予贞留
Num Groups:组数目
Hold Time:保留时间
Multicast Group Address： 组播组地址 Number of Joined Sources: 力口入特定组的源数目
Number of Joined Sources: 剪枝特定组的源数目
从该实施例可以看出，由于路由器的转发组播数据的出接口处于停止转发 数据状态的时长是根据所接收状态刷新消息的发送间隔时长设置的 ,所以在改 变状态刷新消息发送间隔时长时，所述出接口处于停止转发数据状态的时长可 以得到相应的更新，进而可以避免由于路由器的出接口列 生错误而引起的 网络资源浪费的问题。
实施例二， 当所述三层网络设备为三层交换机时，上述方法的具体流程如 下：
21 ): 三层交换机周期性的接收状态刷新消息， 状态刷新消息由源三层交 换机产生， 并向全网扩散；
22 ): 当所接收的状态刷新消息需要在三层交换机的转发组播数据的出接 口进行转发时 , 如果三层交换机的转发组播数据的出接口从出接口列表删除 , 转发组播数据的出接口处于停止转发数据状态，则确定所述出接口处于停止转 发数据状态的时长；
23 ): 对接收状态刷新消息的时间间隔的预置倍数与设置的三层交换机的 转发组播数据的出接口处于停止转发数据状态的时长进行比较，如果所述出接 口处于停止转发数据状态的时长小于发送状态刷新消息的时间间隔的预置倍 时间间隔的预置倍数；
24 ): 对接收状态刷新消息的时间间隔的预置倍数与设置的路由器的转发 组播数据的出接口处于停止转发数据状态的时长进行比较，当所述出接口处于 停止转发数据状态的时长达到所述状态刷新消息发送间隔时长的预置倍数时 , 所述出接口被重新加入出接口列表，并将所述出接口由停止转发数据状态转变 为转发数据状态。
其中， 所述预置的倍数根据协议规定， 可以为三倍。
其中， 所述状态刷新消息发送间隔的时长可以在所述状态刷新消息中携 带； 或者， 可以对接收所述状态刷新消息的时间间隔进行统计， 根据统计结果 确定所述状态刷新消息发送间隔的时长。 从该实施例可以看出，由于三层交换机的转发组播数据的出接口处于停止 转发数据状态的时长是根据所接收状态刷新消息的发送间隔时长设置的，所以 在改变状态刷新消息发送间隔时长时，所述出接口处于停止转发数据状态的时 长可以得到相应的更新 ,进而可以避免由于路由器的出接口列 生错误而引 起的网络资源浪费的问题。
除上述方法外，本发明实施例还提供一种三层网络设备， 包括：接收单元， 用于接收状态刷新消息； 判断单元， 用于在所述接收单元接收到所述状态刷新 消息时， 判断转发组播数据的出接口是否处于停止转发数据状态； 比较单元， 处于停止转发数据状态的时长与状态刷新消息发送间隔的时长的预置倍数；更 小于所述状态刷新消息发送间隔时长的预置倍数时，将所述出接口处于停止转 发数据状态的时长更新为所述状态刷新消息发送间隔时长的预置倍数。
三层网络设备还可以包括：接口状态转变单元， 用于在所述比较单元比较 长的预置倍数相同时， 将所述出接口由停止转发数据状态转变为转发数据状 态。 当然， 接口状态转变单元也可以与更新单元合并为一个功能单元。
三层网络设备可以是路由器， 也可以是三层交换机。
下面结合图 3， 介绍本发明实施例的一种优选的三层网络设备。 如图 3所 示， 包括：
接收单元 301 , 用于周期性的接收状态刷新消息；
判断单元 302， 用于在接收单元 301接收到所述状态刷新消息时， 判断转 发组播数据的出接口是否处于停止转发数据状态； 数据状态时，确定出接口处于停止转发数据状态的时长和状态刷新消息发送间 隔的时长，比较出接口处于停止转发数据状态的时长与状态刷新消息发送间隔 的时长的预置倍数；
更新单元 304， 用于在比较单元 303比较出所述出接口处于停止转发数据 状态的时长小于所述状态刷新消息发送间隔时长的预置倍数时，将所述出接口 处于停止转发数据状态的时长更新为所述状态刷新消息发送间隔时长的预置 倍数；
接口状态转变单元 305， 用于在比较单元 303比较出所述出接口处于停止 转发数据状态的时长与所述状态刷新消息发送间隔时长的预置倍数相同时，将 所述出接口由停止转发数据状态转变为转发数据状态。
其中， 所述三层网络设备进一步包括：
发送单元 306， 用于在判断单元 302判断出所述出接口处于停止转发数据 状态时，在所述状态刷新消息中加上停止转发数据的标志并发送出去。 比较单 元 303可以有多种方式确定状态刷新消息发送间隔的时长。例如，可以从接收 的状态刷新消息中获取所述状态刷新消息发送间隔的时长，进一步来说，状态 刷新消息发送间隔的时长可以携带于所述状态刷新消息的间隔（ Interval )字段。 再例如，可以对接收所述状态刷新消息的时间间隔进行统计，根据统计结果确 定所述状态刷新消息发送间隔的时长。
状态刷新消息发送间隔的时长可以携带于上述格式中的 Interval字段。 根据协议规定，状态刷新消息发送间隔时长的预置倍数为状态刷新消息发 送间隔时长的 3倍。可选的，状态刷新消息发送间隔时长的预置倍数可以大于 180秒。
以上实施例可以看出，本发明实施例通过在接收状态刷新消息后进行转发 时，如果转发组播数据的出接口处于停止转发数据状态， 并且该出接口处于停 止转发状态的时长小于状态刷新消息发送间隔时长的预置倍数，则将该出接口 处于停止转发状态的时长更新为状态刷新消息发送间隔时长的预置倍数，由此 可见， 当更改状态刷新消息的发送间隔时，相应的也更新了出接口处于停止转 发状态的时长， 这样， 出接口列表的表项就不会发生错误， 从而避免了三层网 络设备转发的组播数据在网络中没有接收者的现象，因此解决了现有技术造成 的浪费网络带宽资源的问题。
以上对本实施例所提供的一种转变三层网络设备接口状态的方法和三层 网络设备进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式 进行了阐述， 以上实施例的说明只是用于帮助理解本发明的方法及其核心思 想； 同时， 对于本领域的一般技术人员， 依据本发明的思想， 在具体实施方式 及应用范围上均会有改变之处， 综上所述，本说明书内容不应理解为对本发明 的限制。

Claims

利 要
1、 一种处理三层网络设备接口状态的方法， 其特征在于， 包括： 接收状态刷新消息；
如果转发组播数据的出接口处于停止转发数据状态，且所述出接口处于停 止转发数据状态的时长小于所述状态刷新消息发送间隔时长的预置倍数，则将 时长的预置倍数。
2、 根据权利要求 1所述的方法， 其特征在于， 接收状态刷新消息后， 还 包括： 如果转发组播数据的出接口处于停止转发数据状态，且所述出接口处于 停止转发数据状态的时长与所述状态刷新消息发送间隔时长的预置倍数相同， 则将所述出接口由停止转发数据状态转变为转发数据状态。
3、根据权利要求 1或 2所述的方法， 其特征在于， 接收状态刷新消息后， 还包括： 从接收的状态刷新消息中获取所述状态刷新消息发送间隔的时长。
4、 根据权利要求 3所述的方法， 其特征在于， 所述状态刷新消息发送间 隔的时长携带于所述状态刷新消息的间隔 Interval字段。
5、根据权利要求 1或 2所述的方法， 其特征在于， 接收状态刷新消息后， 还包括： 对接收所述状态刷新消息的时间间隔进行统计，根据统计结果确定所 述状态刷新消息发送间隔的时长。
6、 根据权利要求 1所述的方法， 其特征在于， 所述预置的倍数为 3倍。
7、 根据权利要求 1或 6所述的方法， 其特征在于， 所述状态刷新消息发 送间隔时长的预置倍数大于 180秒。
8、 一种三层网络设备， 其特征在于， 包括：
接收单元， 用于接收状态刷新消息；
判断单元， 用于在所述接收单元接收到所述状态刷新消息时， 判断转发组 播数据的出接口是否处于停止转发数据状态； 时，比较出接口处于停止转发数据状态的时长与状态刷新消息发送间隔的时长 的预置倍数；
更新单元， 的时长小于所述状态刷新消息发送间隔时长的预置倍数时，将所述出接口处于 停止转发数据状态的时长更新为所述状态刷新消息发送间隔时长的预置倍数。
9、 根据权利要求 8所述的三层网络设备， 其特征在于， 还包括： 接口状 时长与所述状态刷新消息发送间隔时长的预置倍数相同时，将所述出接口由停 止转发数据状态转变为转发数据状态。
10、根据权利要求 8或 9所述的三层网络设备， 其特征在于， 所述三层网 络设备为路由器或者三层交换机。
PCT/CN2008/070636 2007-04-04 2008-03-31 Procédé de gestion d'états d'interface de réseau à trois couches et équipement de réseau à trois couches WO2008122234A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710090343.1 2007-04-04
CNB2007100903431A CN100542142C (zh) 2007-04-04 2007-04-04 转变三层网络设备接口状态的方法和装置

Publications (1)

Publication Number Publication Date
WO2008122234A1 true WO2008122234A1 (fr) 2008-10-16

Family

ID=38889917

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070636 WO2008122234A1 (fr) 2007-04-04 2008-03-31 Procédé de gestion d'états d'interface de réseau à trois couches et équipement de réseau à trois couches

Country Status (2)

Country Link
CN (1) CN100542142C (zh)
WO (1) WO2008122234A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220187A (zh) * 2013-04-03 2013-07-24 北京东土科技股份有限公司 一种三层端口状态的检测方法和装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9749220B2 (en) * 2014-09-19 2017-08-29 Telefonaktiebolaget L M Ericsson (Publ) Automated determination of tree attributes and assignment of receiver identifiers by distributed election in multicast architectures relying on packets identifying intended receivers
CN106878188B (zh) * 2017-01-16 2019-11-12 新华三技术有限公司 一种断言报文的发送方法和装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6339791B1 (en) * 1998-12-23 2002-01-15 Alcatel Multicast shortcut routing method
CN1581870A (zh) * 2003-08-04 2005-02-16 华为技术有限公司 一种提高组播pim－sm协议网络的健壮性的方法
CN1741533A (zh) * 2005-09-15 2006-03-01 杭州华为三康技术有限公司 优化建立pim－dm路由表项的方法
CN1750467A (zh) * 2004-09-16 2006-03-22 富士通株式会社 网络系统，数据传输设备，终端设备和组播方法
US20060168047A1 (en) * 2005-01-13 2006-07-27 Jennifer Li Method for suppression of multicast join/prune messages from extranet receivers
CN1889477A (zh) * 2006-07-18 2007-01-03 杭州华为三康技术有限公司 一种提高组播点播成功率的方法及协议无关组播路由器

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6339791B1 (en) * 1998-12-23 2002-01-15 Alcatel Multicast shortcut routing method
CN1581870A (zh) * 2003-08-04 2005-02-16 华为技术有限公司 一种提高组播pim－sm协议网络的健壮性的方法
CN1750467A (zh) * 2004-09-16 2006-03-22 富士通株式会社 网络系统，数据传输设备，终端设备和组播方法
US20060168047A1 (en) * 2005-01-13 2006-07-27 Jennifer Li Method for suppression of multicast join/prune messages from extranet receivers
CN1741533A (zh) * 2005-09-15 2006-03-01 杭州华为三康技术有限公司 优化建立pim－dm路由表项的方法
CN1889477A (zh) * 2006-07-18 2007-01-03 杭州华为三康技术有限公司 一种提高组播点播成功率的方法及协议无关组播路由器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ADAMS A. ET AL.: "Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)", January 2005 (2005-01-01) *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220187A (zh) * 2013-04-03 2013-07-24 北京东土科技股份有限公司 一种三层端口状态的检测方法和装置

Also Published As

Publication number Publication date
CN100542142C (zh) 2009-09-16
CN101039276A (zh) 2007-09-19

Similar Documents

Publication Publication Date Title
AU720817B2 (en) Multicast switching
KR100938513B1 (ko) 멀티캐스트 라우팅을 지원하는 멀티-홉 무선 통신 네트워크 및 그 네트워크를 운영하기 위한 방법
Gossain et al. Multicast: Wired to wireless
Garcia-Luna-Aceves et al. A multicast routing protocol for ad-hoc networks
US6917985B2 (en) Core assisted mesh protocol for multicast routing in ad-hoc Networks
EP3070890A1 (en) Multicast flow overlay using registration over a reliable transport
Semeria et al. Introduction to IP multicast routing
US20070091918A1 (en) Application-level multicasting architecture
JP2008539612A (ja) メッシュ・ネットワークにおけるマルチキャストのルーティング・プロトコル
KR20080074598A (ko) ＰＩＭ―ＳＳＭ을 이용하는 네트워크에서 Ｊｏｉｎ 메시지부하 조절 시스템 및 방법
JP2009273140A (ja) ハイブリッド型メッシュ・ルーティング・プロトコル
WO2008122234A1 (fr) Procédé de gestion d'états d'interface de réseau à trois couches et équipement de réseau à trois couches
CN110999230B (zh) 传输组播报文的方法、网络设备和系统
WO2012103748A1 (zh) 一种组播控制方法、路由设备及组播系统
Cisco Configuring IP Multicast Routing
CN109195117B (zh) 一种在广播型多跳无线网络中pim-sm的改进方法
Danilov et al. Elastic multicast for tactical communications
JP2009290893A (ja) 無線ネットワークにおける経路選択
Lee et al. An Efficient Multicasting Architecture for Context-Aware Messaging Services in the Future Internet
Shah et al. Performance under a failure of wide-area datagram networks with unicast and multicast traffic routing
Chandrasekar et al. Performance of video conferencing in unicast and multicast communication using protocol independent multicast routing
Wang et al. An intelligent on-demand multicast routing protocol in ad hoc networks
CN118041894A (zh) 一种优化冗余链路的三层组播切换方法及装置
Mode et al. The Testking network is implementing IP multicast, and they wish to avoid the problems described above. Based on this information, what IP multicast technology would you recommend? Caution: This protocol should avoid maintaining source-specific forwarding state, thereby reducing the amount of memory needed by the number of sources per
Barros et al. Are alterations needed to the IP multicast service model?

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08715369

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08715369

Country of ref document: EP

Kind code of ref document: A1