CN114095479B - Processing method of IGMPv3/MLDv2 member report message - Google Patents
Processing method of IGMPv3/MLDv2 member report message Download PDFInfo
- Publication number
- CN114095479B CN114095479B CN202010741010.6A CN202010741010A CN114095479B CN 114095479 B CN114095479 B CN 114095479B CN 202010741010 A CN202010741010 A CN 202010741010A CN 114095479 B CN114095479 B CN 114095479B
- Authority
- CN
- China
- Prior art keywords
- multicast
- address
- report message
- last
- specific
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 8
- 238000000034 method Methods 0.000 claims 5
- 230000009286 beneficial effect Effects 0.000 description 1
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/16—Multipoint routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/36—Flow control; Congestion control by determining packet size, e.g. maximum transfer unit [MTU]
Abstract
The invention discloses a processing method of IGMPv3/MLDv2 member report message, if the number of multicast sources exceeds the limit, the last multicast source address field is filled with a first specific IP address; if the last IP address of the multicast source address list in the Group Record received by the multicast router is the first specific IP address, the multicast source address reported by the message is incomplete, and the message is further followed; if the last multicast source field in the last Report message is filled with the second specific IP: representing the last Report message.
Description
Technical Field
The invention relates to a processing method of report messages, in particular to a processing method of IGMPv3/MLDv2 member report messages.
Background
If the multicast source address contained in a single Group Record segment in the membership report message IS too many, resulting in the length of the entire message exceeding the MTU limit, and the type field of the Group Record IS mode_is_ EXCLUDE or change_to_ EXCLUDE _mode, then the multicast source address exceeding the limit will not be reported, and the list of multicast source addresses for each report remains substantially consistent.
Directly discarding the multicast source addresses exceeding the limit may result in the multicast group members not always receiving the multicast traffic of the multicast source actually desiring to request the multicast. If one wants to report all multicast source addresses, one needs to adjust the MTU, but when the message length exceeds the maximum MTU, there is still a partial packet source data loss.
Disclosure of Invention
The invention designs and develops a processing method of IGMPv3/MLDv2 membership report message, solves the problem that multicast traffic sent by partial multicast sources cannot be requested when the limit of the MTU is exceeded, does not need to modify the MTU, and can adapt to any number of multicast source addresses.
A processing method of IGMPv3/MLDv2 member report message,
If the number of the multicast sources exceeds the limit, filling the last multicast source address field with a first specific IP address;
If the last IP address of the multicast source address list in the Group Record received by the multicast router is the first specific IP address, the multicast source address reported by the message is incomplete, and the message is further followed;
If the second Report message still cannot send all multicast source lists, the last multicast source address segment of the message is still filled with the first specific IP address; and so on;
Filling the last multicast source field in the last Report message with a second specific IP: representing the last Report message;
if the second specific IP address filled in the last multicast source field in the Report message received by the multicast router indicates that the Report message is received completely, generating a multicast forwarding table item and notifying a related multicast routing protocol to issue the multicast table item.
As a further preference, the first specific IP address is IGMP:0.0.0.0, MLD: 0:0:0:0:0.
As a further preference, the second specific IP address is IGMP:255.255.255.255, mld: FF, FF and FF.
As a further preference, the first specific IP address is IGMP:255.255.255.255, mld: FF, FF and FF.
As a further preference, the second specific IP address is IGMP:0.0.0.0, MLD: 0:0:0:0:0.
As a further preferred option, if the multicast router does not receive the subsequent message within a certain period of time, the cached data is generated into a multicast forwarding table entry, and the relevant multicast routing protocol is notified to issue the multicast route.
The beneficial effects of the invention are as follows:
When the multicast source addresses contained in a single Group Record segment in the member report message are too many, and the length of the whole message exceeds the limit of the MTU, the multicast traffic of all multicast sources can still be normally on demand.
Drawings
Fig. 1 is a processing flow of a transmitting end of the present invention.
Fig. 2 is a flow chart of the multicast router processing according to the present invention.
Detailed Description
The present invention is described in further detail below with reference to the drawings to enable those skilled in the art to practice the invention by referring to the description.
By filling the last multicast source address segment of the Group Record with a special IP address (such as IGMP:0.0.0.0, mld: 0:0:0:0:0:0), and when the multicast router parses the message, if the IP address of the last multicast source address field is a special IP (e.g., IGMP:0.0.0.0, mld: 0:0:0:0:0), then it is considered that there is an additional message. Thus, the problem of multicast source data loss can be avoided.
The last multicast source address field may be populated with a particular IP address (e.g., IGMP:0.0.0.0, mld: 0) when the number of multicast sources exceeds the limit.
As a preference, if the last IP address of the multicast source address list in the Group Record received by the multicast router is IGMP:0.0.0.0, MLD:0:0:0:0:0, then the multicast source address of the message report is incomplete, and there are further messages. As a preference, the last IP address of the multicast source address list is IGMP:0.0.0.0, MLD:0:0:0:0:0 are just one preferred, but other IP addresses are also possible.
If the second Report message still cannot send all multicast source lists, then the specific IP address (IGMP: 0.0.0.0, MLD: 0:0:0:0) still used by the last multicast source address field of the message, and so on. As a preference, the specific IP address (IGMP: 0.0.0.0, MLD: 0:0:0:0:0) still used by the last multicast source address field is just one preference, but other IP addresses are also possible.
The IP padding of the last multicast source field in the last Report message is IGMP:255.255.255.255, mld: FF: FF: FF: FF: FF stands for the last Report message.
If the last multicast source field in the Report message received by the multicast router fills the IP address of IGMP:255.255.255.255, mld: and the step of generating a multicast forwarding table item and notifying a related multicast routing protocol to issue the multicast table item after the Report message is received. As a preference, the IP address filled in the multicast source field is IGMP:255.255.255.255, mld: FF: FF is just one preference, but may also be other IP addresses.
If the multicast router does not receive the subsequent message in the time T, the cached data is generated into a multicast forwarding table item, and the relevant multicast routing protocol is informed to issue the multicast routing. The latency tsault is 10 seconds and may also be configured by the administrator based on the network status.
The processing flow of the message at the transmitting end is shown in fig. 1, and the processing flow of the multicast router is shown in fig. 2.
Although embodiments of the present invention have been disclosed above, it is not limited to the details and embodiments shown and described, it is well suited to various fields of use for which the invention would be readily apparent to those skilled in the art, and accordingly, the invention is not limited to the specific details and illustrations shown and described herein, without departing from the general concepts defined in the claims and their equivalents.
Claims (6)
1. A processing method of IGMPv3/MLDv2 member report message is characterized in that,
If the number of the multicast sources exceeds the limit, filling the last multicast source address field with a first specific IP address;
If the last IP address of the multicast source address list in the Group Record received by the multicast router is the first specific IP address, the multicast source address reported by the message is incomplete, and the message is further followed;
if the second Report message still cannot send all multicast source lists, the last multicast source address segment of the message is still filled with the first specific IP address; and so on;
the last multicast source field in the last Report message is filled with the second specific IP address: representing the last Report message;
If the last multicast source field in the Report message received by the multicast router is filled with the second specific IP address, indicating that the Report message is received completely, generating a multicast forwarding table item and notifying a related multicast routing protocol to issue the multicast table item.
2. The method for processing IGMPv3/MLDv2 membership report message as set forth in claim 1, wherein said first specific IP address is IGMP:0.0.0.0, MLD: 0:0:0:0:0.
3. The method for processing IGMPv3/MLDv2 membership report message according to claim 1 or 2, wherein said second specific IP address is IGMP:255.255.255.255, mld: FF, FF and FF.
4. The method for processing IGMPv3/MLDv2 membership report message as set forth in claim 1, wherein said first specific IP address is IGMP:255.255.255.255, mld: FF, FF and FF.
5. The method for processing IGMPv3/MLDv2 membership report message according to claim 1 or 4, wherein said second specific IP address is IGMP:0.0.0.0, MLD: 0:0:0:0:0.
6. The method for processing IGMPv3/MLDv2 membership report message as defined in claim 1, wherein if no subsequent message is received by the multicast router for a certain time, generating a multicast forwarding table entry from the buffered data, and notifying the relevant multicast routing protocol to issue the multicast route.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010741010.6A CN114095479B (en) | 2020-07-29 | 2020-07-29 | Processing method of IGMPv3/MLDv2 member report message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010741010.6A CN114095479B (en) | 2020-07-29 | 2020-07-29 | Processing method of IGMPv3/MLDv2 member report message |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114095479A CN114095479A (en) | 2022-02-25 |
| CN114095479B true CN114095479B (en) | 2024-04-30 |
Family
ID=80294865
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010741010.6A Active CN114095479B (en) | 2020-07-29 | 2020-07-29 | Processing method of IGMPv3/MLDv2 member report message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114095479B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105099937A (en) * | 2015-06-17 | 2015-11-25 | 杭州华三通信技术有限公司 | Method and equipment for determining PMTU |
| WO2016050177A1 (en) * | 2014-09-30 | 2016-04-07 | 华为技术有限公司 | Pmtu determination method, network device and system |
| CN110351197A (en) * | 2018-04-04 | 2019-10-18 | 华为技术有限公司 | Data transmission method and relevant apparatus |
-
2020
- 2020-07-29 CN CN202010741010.6A patent/CN114095479B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016050177A1 (en) * | 2014-09-30 | 2016-04-07 | 华为技术有限公司 | Pmtu determination method, network device and system |
| CN105099937A (en) * | 2015-06-17 | 2015-11-25 | 杭州华三通信技术有限公司 | Method and equipment for determining PMTU |
| CN110351197A (en) * | 2018-04-04 | 2019-10-18 | 华为技术有限公司 | Data transmission method and relevant apparatus |
Non-Patent Citations (2)
| Title |
|---|
| 分片与多播基于网络处理器的高速实现;俞致伟;微机发展(第07期);全文 * |
| 基于IPV4的IP数据报的分片与重组;王鹏;;时代教育(第11期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114095479A (en) | 2022-02-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5339221B2 (en) | Network device, network system, and method for converting multicast packet to unicast packet | |
| US7876754B2 (en) | Methods and arrangements for monitoring subsource addressing multicast distribution trees | |
| US6055364A (en) | Content-based filtering of multicast information | |
| US7697524B2 (en) | Method and system for determining path maximum transfer unit for IP multicast | |
| US7400625B2 (en) | Protocol for multicast communication | |
| KR20170037818A (en) | Information-centric networking with small multi-path or single-path forwarding state | |
| KR101604810B1 (en) | Methods for obtaining terminal multicast status | |
| CN111431816B (en) | Distributed flow rate limiting method and system | |
| US20030218980A1 (en) | Device and system for multicast communication | |
| US7009971B2 (en) | Methods and arrangements for multicasting a data stream at different data rates to groups of subscribers | |
| US20040033075A1 (en) | Delivering multicast streams in a passive optical network | |
| WO2008138248A1 (en) | A method, an interface board and a router for transmitting the message | |
| CN114095479B (en) | Processing method of IGMPv3/MLDv2 member report message | |
| US20050141502A1 (en) | Method and apparatus to provide multicast support on a network device | |
| EP1936876B1 (en) | Method and system for ensuring data exchange between a server system and a client system | |
| CN1812375A (en) | Method of constructing a unique transmission address by a server and server using this method | |
| EP2192719A1 (en) | Method and system for providing source specific multicast service on Ethernet network | |
| CN106487890A (en) | A kind of cross-node communication network requesting method based on XMPP | |
| Liao et al. | Receiver-initiated group membership protocol (RGMP): A new group management protocol for IP multicasting | |
| US7924743B2 (en) | Method for multicast distribution tree switchover | |
| CN101877678B (en) | Method and device for multicast users of specific source group to leave quickly | |
| US20230318969A1 (en) | Optimizing network load in multicast communications | |
| KR100922139B1 (en) | System and method for blocking a multicast spam in pim multicast protocol | |
| JP3693953B2 (en) | Broadcast transmission method, apparatus, and program | |
| Liao et al. | Receiver-initiated group membership protocol (RGMP): a new group management protocol for IP multicasting |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |