A method for optimizing group management protocol and server and system thereof
Abstract
A method for optimizing a group management protocol, comprising: receiving (S1), by a multicast router, a membership report sent by a member of a group; and characterized by understanding: checking (S2), by the multicast router, if the report includes a non-empty source list in the EXCLUDE mode; process (S3) the report as a report to join non-specific sources if the report includes a non-empty source list in EXCLUDE mode; and update (S4) the corresponding status on the router directly with report data if the report is a membership report in the INCLUDE mode that includes a non-empty source list, a membership report in the INCLUDE mode that includes a list of any sources , or a membership report in EXCLUDE mode that includes an empty source list.
Term
0.2 yearsto projected expiry
Projected expiry 5 December 2026, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
13 claims: 2 independent, 11 dependent
- 1REIVINDICACIONES 1. Un método para la optimización de un protocolo de gestión de grupos, que comprende:recibir (S1), por parte de un enrutador de multidifusión, un informe de pertenencia enviado por un miembro de un grupo;y caracterizado por comprender: comprobar (S2), por parte del enrutador de multidifusión, si el informe incluye una lista de fuentes no vacía en el modo EXCLUDE;procesar (S3) el informe como un informe de unión a fuentes no específicas si el informe incluye una lista de fuentes no vacía en el modo EXCLUDE;y actualizar (S4) el estado correspondiente en el enrutador directamente con datos del informe si el informe es un informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes no vacía, un informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes cualesquiera, o un informe de pertenencia en el modo EXCLUDE que incluye una lista de fuentes vacía.
- 2El método de la reivindicación 1, en el que el miembro del grupo le envía al enrutador de multidifusión un informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes no vacía para completar una unión a fuentes específicas.
- 3El método de la reivindicación 1, en el que el enrutador de multidifusión recibe un informe de unión a fuentes no específicas, o un informe incluye una lista de fuentes no vacía en el modo EXCLUDE, y procesa el informe según el modo INCLUDE.
- 4El método de la reivindicación 3, en el que el miembro del grupo le envía al enrutador de multidifusión un informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes cualesquiera para completar una unión a fuentes no específicas.
- 5El método de la reivindicación 4, en el que un modelo de interfaz para una unión a fuentes no específicas en el lado del miembro del grupo indica la inclusión de una lista de fuentes cualesquiera mediante "INCLUDE, ANY".
- 6El método de la reivindicación 3, en el que el miembro del grupo le envía al enrutador de multidifusión un informe de pertenencia en el modo EXCLUDE que incluye una lista de fuentes vacía para completar una unión a fuentes no específicas.
- 7El método de la reivindicación 6, en el que un modelo de interfaz para una unión a fuentes no específicas en el lado del miembro del grupo indica la exclusión de una lista de fuentes vacía mediante "EXCLUDE, NULL".
- 8El método de la reivindicación 3, en el que, si el enrutador de multidifusión recibe un informe de pertenencia en el modo EXCLUDE que incluye una lista de fuentes no vacía, el enrutador procesa el informe de acuerdo con la recepción de un informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes cualesquiera o con la recepción de un informe de pertenencia en el modo EXCLUDE que incluye una lista de fuentes vacía.
- 9El método de cualquiera de las reivindicaciones 1-8, en el que, cuando el miembro del grupo inicia una aplicación de multidifusión, o cuando el miembro del grupo recibe un mensaje periódico de consulta enviado desde el enrutador de multidifusión, o cuando el miembro del grupo cambia su estado de recepción en una interfaz el miembro del grupo le envía al enrutador de multidifusión un informe de pertenencia en el que se informa del estado actual de recepción del grupo de la interfaz.
- 10El método de cualquiera de la reivindicación 1, en el que el informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes cualesquiera o el informe de pertenencia en el modo EXCLUDE que incluye la lista de fuentes vacía se identifica como el informe de unión a fuentes no específicas.
- 11Un enrutador de multidifusión para recopilar y mantener las pertenencias al grupo, que comprende:un primer medio para recibir un informe de pertenencia enviado por un miembro del grupo;y caracterizado por comprender: un segundo medio para comprobar si el informe incluye una lista de fuentes no vacía en el modo EXCLUDE;un tercer medio para procesar el informe como un informe de unión a fuentes no específicas si el informe incluye la lista de fuentes no vacía en el modo EXCLUDE;y un cuarto medio para actualizar el estado correspondiente en el enrutador directamente con datos del informe si el informe es un informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes no vacía, un informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes cualesquiera o un informe de pertenencia en el modo EXCLUDE que incluye una lista de fuentes vacía. 5 12. El enrutador de la reivindicación 11, en el que el informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes cualesquiera, o el informe de pertenencia en el modo EXCLUDE que incluye una lista de fuentes vacía se identifica como el informe de unión a fuentes no específicas.
- 13Un sistema de multidifusión para la optimización de un protocolo de gestión de grupos caracterizado por comprender a un miembro del grupo y un enrutador de multidifusión en el que el enrutador de multidifusión 10 comprende:un primer medio para recibir un informe de pertenencia enviado por el miembro del grupo;un segundo medio para comprobar si el informe incluye una lista de fuentes no vacía en el modo EXCLUDE;un tercer medio para procesar el informe como un informe de unión a fuentes no específicas si el informe incluye la lista de fuentes no vacía en el modo EXCLUDE;y 15 un cuarto medio para actualizar el estado correspondiente en el enrutador directamente con datos del informe si el informe es un informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes no vacía, un informe de pertenencia en el modo INCLUDE que incluye una lista de fuentes cualesquiera o un informe de pertenencia en el modo EXCLUDE que incluye una lista de fuentes vacía.
- 14El sistema de la reivindicación 13, en el que el informe de pertenencia en el modo INCLUDE que incluye 20 una lista de fuentes cualesquiera, o el informe de pertenencia en el modo EXCLUDE que incluye la lista de fuentes vacía se identifica como el informe de unión a fuentes no específicas.
Independent claims13
161 paragraphs, as filed
p00001Method for optimizing the group management protocol, and its server and system
p00002Field of the Invention
p00003The present invention relates to the multicast service, and, in particular, to a method, a server and a system for optimizing a group management protocol.
p00004Background of the invention
p00005The Internet Group Management Protocol (IGMP) is designed for the management of multicast groups in Internet Protocol version 4 (IPv4). It operates between a node and a multicast router connected directly to the node. The node communicates through the protocol to the local router that it wishes to join a certain multicast group, and the router periodically consults whether the members of a known group in the local area network (LAN) are active (that is, if there is still a member of a particular multicast group in the network segment), thus collecting and maintaining the group memberships of the connected network.
p00006The IGMP exists in three versions. IGMPv1 [RFC1112] defines the basic procedures for consulting and informing about group memberships. IGMPv2 [RFC2236] is widely used today, providing a mechanism for quick disconnection of a group member. The IGMPv3 [RFC3376] adds the source filtering function, which allows a group member to indicate whether or not to receive packets from certain multicast sources.
p00007The Multicast Listening Discovery (MLD) protocol is an extension of the IGMP for applications based on Internet Protocol version 6 (IPv6). The MLD performs the same functions as the IGMP. The MLD exists in two versions: the MLDv1 and the MLDv2, which correspond to IGMPv2 and IGMPv3 respectively.
p00008In IGMPv3 or MLDv2, to support the filtering of specific sources, the protocol defines two filtering modes: INCLUDE (inclusive) and EXCLUDE (exclusive). In the INCLUDE mode a multicast receiver receives packets only from specific sources. In EXCLUDE mode, the receiver receives multicast packets only from sources other than specific sources. Specific sources are defined in a list of sources.
p00009The source filtering function defined in IGMPv3 / MLDv2 improves the ability to express group members. A receiver may choose to receive or not receive multicast packets from certain sources. In IGMPv3, the source filtering function is implemented in a node as follows:
p00010IPMulticastListen (socket, interface, multicast address, filtering mode, source list) (1)
p00011The socket is a parameter in an IPv4 system and is related to different requesting entities (a certain protocol of a higher layer or an application); The interface is a local identifier of the network interface, whether it is physical or logical; the multicast address is the address of the request group; the filtering mode is INCLUDE or EXCLUDE; and the source list is a list of unicast IP addresses of multicast sources from which the multicast receiver wishes (in the INCLUDE mode) or does not wish (in the EXCLUDE mode) to receive packets.
p00012In MLDv2, there is a similar expression:
p00013IPv6MulticastListen (socket, interface, IPv6 multicast address, filtering mode, source list) (2)
p00014The main difference between (2) and (1) is that multicast addresses and the source list are represented in the form of IPv6 addresses. For descriptive purposes, the related technical solution of the present application is described on the basis of IGMPv3. The function of filtering sources in MLDv2 is equivalent to that of IGMPv3.
p00015The IGMP is an asymmetric protocol, in which a group member (usually on a node and, occasionally, on a router) behaves differently from a multicast router. An IGMPv3 node stores the reception status of the multicast group on each socket and on each interface in order to support source filtering. The status of a socket represents the group reception wishes expressed by each application, that is, to which multicast group do you want to join the application, and what list of multicast sources do you want to filter, in which interface and in what mode of filtering. The group receive state of an interface is a combination of the group receive states of all interface sockets. The node can generate a status report of the IGMPv3 and respond to a request from the connected router to check the group memberships, according to the group's reception status and the status change in the interface.
p00016A router that has IGMPv3 enabled also needs to store the reception status of the groups of the connected network. The conceptual model is:
p00018(multicast address, group timer, filtering mode, (source records)) (3)
p00019The multicast address is the address of a group associated with the status register; the filtering mode is defined by the router, and is registered as EXCLUDE, if the router receives a report indicating the EXCLUDE mode; the group timer is used in the EXCLUDE mode, and indicates the timeout interval for the group filtering mode to change from EXCLUDE to INCLUDE; and the source register is represented in the form of (source address, source timer); the source address is the address of the multicast source from which the node wishes to receive packets; and the source timer defines the timeout interval for receiving packets from the source address.
p00020IGMPv3 and MLDv2 support source filtering, which increases the flexibility of joining the group. In particular, the INCLUDE mode is defined to support the routing protocol for Multicast Independent of the Protocol / Multicast of Specific Sources. However, the adoption of filtering modes also suffers from some weaknesses:
<dl><dt>(1) </dt><dd>Complexity of the configuration and mode switching: a router has to configure and switch the filtering mode depending on the change in the reception status of the connected system group, and the configuration and modification are closely related to the timer status of the source or group, and require complex evaluation logic. The implementation of the protocol is uncomfortable.</dd></dl>
<dl><dt>(2)</dt><dd> The EXCLUDE mode does not fully meet the requirements of real applications: on the one hand, it is strange that an application does not want to receive multicast packets from one or more sources in a multicast application system. On the other hand, even if there is a scenario in which the node connected to a router interface does not wish to receive multicast packets from a certain source, it is very possible that other nodes in the network do wish to receive data from that source. In this case, the router must also resend packets from this source. Therefore, the effect of the EXCLUDE mode is limited.</dd></dl>
p00021The document “IGMPv3 / MLDv2 and Multicast Routing Protocol Interaction (IGMPv3 / MLDv2 and Interaction with Multicast Routing Protocol); <draft-ietf-magma-igmpv3-and-routing-04.txt >> ”discloses how multicast routing protocols interact with group management protocols with source filtering. In particular, on p. 2, par. 3, D1 discloses a mechanism for the interaction of version transitions and routing protocols. An interface on which a router receives a query message corresponding to the old version must immediately switch to a compatibility mode with that old version. Any group members previously known with specific sources (known through the INCLUDE and EXCLUDE mechanisms) are converted to group members with non-specific sources.
p00022The document “MLDv2 design, implementation and evaluation for source-specific multicast over IPv6 (Design, implementation and evaluation of the MLDv2 protocol for multicasting of specific sources over IPv6)” discloses the implementation of the MLDv2 on the node side, mainly the most complex procedure Multicast Source Filtering (MSF), applied to the core of 4.4BSD.
p00023Summary of the Invention
p00024The embodiments of the present invention provide a method, a server and a system for optimizing a group management protocol in order to reduce the complexity in the configuration and switching of the filtering modes in the previous protocols.
p00025A method for optimizing a group management protocol includes:
p00026receive, from a multicast router, a group membership report sent by a group member;
p00027by the multicast router, check upon receipt of the membership report if the report includes a non-empty source list in EXCLUDE mode; if so, update a corresponding status on the router according to a union to non-specific sources; or, otherwise
p00028Update the corresponding status on the router directly with the report data if the report does not include a non-empty source list in EXCLUDE mode.
p00029In the above method, the group member sends a membership report in the INCLUDE mode to the multicast router that includes a non-empty source list to complete a binding to specific sources; and
p00030The multicast router receives a report to join non-specific sources and processes the report according to the INCLUDE mode.
p00031Additionally, the group member sends a membership report in mode 3 to the multicast router.
p00033INCLUDES that it includes a list of any sources to complete a union to non-specific sources; and the interface model for a union to non-specific sources on the member side of the group indicates the inclusion of any list of sources by means of "INCLUDE, ANY".
p00034On the other hand, the group member sends a membership report in the EXCLUDE mode to the multicast router that includes an empty source list to complete a binding to non-specific sources; and the interface model for a union to non-specific sources on the member side of the group indicates the exclusion of an empty source list using "EXCLUDE, NULL".
p00035If the multicast router receives a membership report in the EXCLUDE mode that includes a non-empty source list, the router processes the report according to the receipt of a membership report in the INCLUDE mode that includes a list of any sources or receiving a membership report in the EXCLUDE mode that includes an empty source list.
p00036A multicast router for collecting and maintaining group memberships includes a verification module, a conversion module and an identification module;
p00037the check module is adapted to determine if a membership report received includes a non-empty source list in EXCLUDE mode; if the membership report received includes a non-empty source list in the EXCLUDE mode, the check module activates the conversion module; if the membership report received does not include a non-empty source list in the EXCLUDE mode, the check module activates the identification module;
p00038The conversion module is adapted to convert the membership report received into a binding report to non-specific sources and send the report to the identification module for processing; and
p00039The identification module is adapted to identify a binding report to non-specific sources and update a corresponding status on the router.
p00040The identification module identifies as a report of union to non-specific sources a membership report in the INCLUDE mode that includes a list of any sources, or a membership report in the EXCLUDE mode that includes an empty source list.
p00041The conversion module converts a membership report into the EXCLUDE mode that includes a non-empty source list in a report that can be identified by the identification module as a report to join non-specific sources.
p00042A multicast system for the optimization of a group management protocol includes a series of group members and a multicast router.
p00043The multicast router includes a check module, a conversion module and an identification module; the check module is adapted to determine if a membership report received includes a non-empty source list in EXCLUDE mode; if the membership report received includes a non-empty source list in the EXCLUDE mode, the check module activates the conversion module; if the membership report received does not include a list of sources not empty in the EXCLUDE mode, the check module activates the identification module; The conversion module is adapted to convert the membership report received into a binding report to non-specific sources and send the report to the identification module for processing; and the identification module is adapted to identify a binding report to non-specific sources and update a corresponding status on the router.
p00044The identification module identifies as a report of union to non-specific sources a membership report in the INCLUDE mode that includes a list of any sources, or a membership report in the EXCLUDE mode that includes an empty source list.
p00045The conversion module converts a membership report into the EXCLUDE mode that includes a non-empty source list in a report that can be identified by the identification module as a report to join non-specific sources.
p00046The embodiments of the present invention provide the following benefits:
p00047The prior art defines two filtering modes and requires that the node and the router maintain complex filtering modes and processing mechanisms. In view of the limited application scenarios and the limited effects of the EXCLUDE mode filter, the embodiments of the invention select the filter function implemented by the previous EXCLUDE mode and, after receiving a membership report, check whether the membership report includes a non-empty source list in EXCLUDE mode; if so, the corresponding status on the router is updated according to a union to non-specific sources, or, otherwise (if the report is a membership report in the INCLUDE mode that includes a non-empty source list, a 4 10
p00049membership report in the INCLUDE mode that includes a list of any sources, or a membership report in the EXCLUDE mode that includes an empty source list), the corresponding status on the router is updated directly with report data without checking and mode switching.
p00050The method provided by an embodiment of the invention can prevent complex switching and processing of the filtering modes in the above protocols.
p00051Upon receipt of a membership report, the multicast router checks the filtering mode of the report and the source list attribute included in the report instead of rejecting reports in the EXCLUDE mode that include a non-empty source list afterwards. to select the previous EXCLUDE filtering mode. Accordingly, upon receipt of said report, the multicast router updates the corresponding status on the router according to a binding to non-specific sources, and therefore, the method is compatible with other multicast management protocols of previous versions.
p00052The embodiments of the invention have reserved the practical function of filtering sources in the INCLUDE mode, and therefore can support Multicasting of Specific Sources (SSM).
p00053To support the method, the embodiments of the invention also provide a multicast router and a corresponding multicast system.
p00054Brief description of the drawings
p00055Figure 1 shows a schematic of the structure of a multicast router according to an embodiment of the invention;
p00056Figure 2 shows a schematic of the structure of a multicast system according to an embodiment of the invention; and
p00057Figure 3 shows the method of a method for optimizing a group management protocol according to an embodiment of the invention.
p00058Detailed description of the invention
p00059To simplify the configuration and switching of the filtering modes in the previous protocols (including but not limited to IGMPv3 and MLDv2), an embodiment of the present invention provides a multicast router, which performs the collection and maintenance of the Current group memberships. As shown in Figure 1, the multicast router includes a test module, a conversion module and an identification module that are connected in sequence. The test module is also connected directly to the identification module.
p00060The check module is adapted to determine if a membership report received includes a non-empty source list in the EXCLUDE mode; if the membership report received includes a non-empty source list in the EXCLUDE mode, the check module activates the conversion module; If the membership report received does not include a list of sources not empty in the EXCLUDE mode, the check module activates the identification module.
p00061The conversion module is adapted to convert a membership report in the EXCLUDE mode that includes a non-empty source list in a report that can be identified by the identification module as a report to join non-specific sources and send the report to identification module for processing.
p00062The identification module is adapted to identify a binding report to non-specific sources and update a corresponding status on the router. In one embodiment of the invention, the identification module may identify a membership report in the INCLUDE mode that includes a list of any sources, or a membership report in the EXCLUDE mode that includes an empty source list, such as a report of union to non-specific sources.
p00063In accordance with the above multicast router, an embodiment of the invention provides a multicast system. As shown in Figure 2, the multicast system includes a multicast router provided by an embodiment of the invention and a series of group members connected to the multicast router.
p00064With the above multicast router and multicast system, an embodiment of the invention provides a method for optimizing a group management protocol. As shown in Figure 3, the method includes the following steps:
p00065S1. A group member sends a membership report to the multicast router.
p00067According to the prior art, when a group member starts a multicast application, or when a group member receives a periodic inquiry message sent from the multicast router, the group member sends a multicast router a report of membership, indicating the current reception status of the interface group.
p00068To be compatible with the protocols of previous versions, a group member is allowed to send membership reports in the INCLUDE and EXCLUDE modes to the multicast router.
p00069In addition, the membership report in the INCLUDE mode may be a membership report in the INCLUDE mode that includes a non-empty source list or a membership report in the INCLUDE mode that includes a list of any sources. The membership report in the EXCLUDE mode can be a membership report in the EXCLUDE mode that includes a non-empty source list or a membership report in the EXCLUDE mode that includes an empty source list.
p00070S2 After receiving the membership report, the multicast router checks if the membership report includes a non-empty source list in EXCLUDE mode; If the membership report includes a non-empty source list in the EXCLUDE mode, the procedure continues with step S3; If the membership report does not include a non-empty source list in the EXCLUDE mode, the procedure continues with step S4.
p00071After receiving the membership report, the multicast router checks the filtering mode of the report and the attribute of the report source list, and continues with step S3 to select the EXCLUDE mode in order to highlight the benefits of the present invention and make the compatibility with the protocols of the previous versions a reality;
p00072or, the multicast router continues in step S4 to update the corresponding status on the router.
p00073S3 The corresponding status on the router is updated according to a connection to non-specific sources.
p00074The embodiment of the invention optimizes the above protocols by selecting the filtering mode of the EXCLUDE mode that has few application scenarios and low filter efficiency. Upon receiving a report of the EXCLUDE mode, the router does not configure the filtering mode or perform the switching when the timeout period expires. Instead, the router processes an EXCLUDE mode report that includes a non-empty source list as a report to join non-specific sources (detailed in step S4). This means that the router updates the corresponding status on the router according to a connection to non-specific sources. This prevents the mode setting and its switching due to timeout, and the router will not return an error message to the group member upon receiving a report of the EXCLUDE mode that includes a non-empty source list, thus making it a reality. compatibility with the protocols of previous versions.
p00075S4 The corresponding status on the multicast router is updated directly with report data.
p00076If the multicast router receives a membership report in the INCLUDE mode that includes a non-empty source list in accordance with the above protocols, that is, the multicast router receives a request to join specific sources by the group member , the multicast router directly updates the corresponding status on the router with the source list not empty according to the previous procedure.
p00077If the multicast router receives a join report to non-specific sources, the router processes the report according to the INCLUDE mode.
p00078The group member can use (INCLUDE, ANY) in the interface model for a connection to non-specific sources in order to indicate the inclusion of any list of sources and send a membership report in the multicast router mode INCLUDE that you include a list of any sources. If the multicast router receives a membership report that includes (INCLUDE, ANY), the router identifies the report as a report to join non-specific sources and completes the union to non-specific sources.
p00079The group member can use (EXCLUDE, NULL) in the interface model for a connection to non-specific sources in order to indicate the exclusion of an empty source list and send a membership report in mode to the multicast router EXCLUDE that includes an empty source list. If the multicast router receives a membership report that includes (EXCLUDE, NULL), the router identifies the report as a report to join non-specific sources and completes the union to non-specific sources.
p00080The foregoing is an overview of the method for optimizing a group management protocol according to an embodiment of the invention.
p00081The definitions of related information and specific actions are described below after an earlier protocol has been optimized according to the method.
p000831. Definitions of new interface models for binding actions to non-specific sources:
p00084IPMulticastListen (socket, interface, multicast address, INCLUDE, ANY); (4)
p00085In expression (4), IPMulticastListen indicates the IGMPv3 interface model, and can be replaced by IPv6MulticastListen in the case of MLDv2; socket is a parameter in the system and is related to different requesting entities; the interface is a local identifier of the network interface; the multicast address is an address of the request group; (INCLUDE, ANY) indicates the union of a group of non-specific sources.
p00086IPMulticastListen (socket, interface, multicast address, EXCLUDE, NULL); (5)
p00087In expression (5), IPMulticastListen indicates the IGMPv3 interface model, and can be replaced by IPv6MulticastListen in the case of MLDv2; socket is a parameter in the system and is related to different requesting entities; the interface is a local identifier of the r ed interface ; the multicast address is an address of the request group; (EXCLUDE, NULL) indicates the union of a group of non-specific sources.
<dl><dt>2. </dt><dd>Definitions of the fields related to the mode in a group membership report (INCLUDE and ANY are taken as an example; EXCLUDE and NULL can be inferred): </dd></dl>
In an IGMPv3 / MLDv2 group membership report there are six types of group records [RFC3376], while four types related to INCLUDE are reserved. The four types related to INCLUDE are: NODE_IS_INCLUDE (hereinafter IS_IN), ALLOW_NEW_SOURCES (hereinafter ALLOW), BLOCK_OLD_SOURCES (hereinafter BLOCK) and CHANGE_TO_INCLUDE (hereinafter TO_IN).
<dl><dt>3. </dt><dd>New behavioral definitions of group members (INCLUDE and ANY are taken as an example, EXCLUDE and NULL can be inferred): </dd></dl>
p00088to. Change node interface status
p00089In the optimized protocol, the node status change rule is described in Table 1:
p00090Table 1
<dl><dt>Previous State </dt><dd>New state Notified Status </dd></dl>
<dl><dt>INCLUDE (A) </dt><dd>INCLUDE (B) ALLOW (BA), BLOCK (AB) </dd></dl>
<dl><dt>INCLUDE (A) </dt><dd>INCLUDE (ANY) INCLUDE (ANY) </dd></dl>
<dl><dt>INCLUDE (ANY) </dt><dd>INCLUDE (B) TO_IN (B) </dd></dl>
p00091When the node generates a report, it encapsulates the report types NODE_IS_INCLUDE, ALLOW_NEW_SOURCES, BLOCK_OLD_SOURCES and CHANGE_TO_INCLUDE.
p00092b. Actions after the node receives a query message
p00093In the previous protocol, the node side sets a group timer to respond to a source query message from a router's group. When the group timer expires, the node sends a report in response to the query. When the group timer is exhausted, the node must compare the list of sources associated with the group timer and the associated group sources of the interface in order to decide the form of the interface status to be notified to the router. In the optimized protocol, the determination rule is described in Table 2:
p00094Table 2
<dl><dt>Interface Status </dt><dd>Pending Source List Notified Status Record </dd></dl>
<dl><dt>INCLUDE (A) </dt><dd>B IS_IN (A * B) </dd></dl>
<dl><dt>INCLUDE (ANY) </dt><dd>B IS_IN (B) </dd></dl>
p00095Four. Multicast router behaviors (INCLUDE and ANY are taken as an example, EXCLUDE and NULL can be inferred):
p00096to. Router filtering mode
p00098In IGMPv3 / MLDv2, the filtering mode of an IGMPv3 / MLDv2 router is defined to reduce the number of states on the router. Specifically, after receiving a message from the EXCLUDE mode, the filtering mode of the router is set to EXCLUDE. If there is no source for EXCLUDE, when the group timer runs out, the filtering mode of the router is changed to INCLUDE.
p000995 In the optimized protocol, the router does not configure or change the filtering mode, but instead processes membership reports received only in the INCLUDE filtering mode. Therefore, the EXCLUDE mode of the previous router-side protocol is irrelevant and the optimized protocol cancels the router mode definition. The conceptual model of the reception status of the router is:
p00100multicast address, group timer (source records) (6)
p0010110 In expression (6), the multicast address is a group address associated with the status register; The group timer is adapted to check if the network connected to the router has a status of receiving non-specific source groups, and the group records are source records.
p00102b. Actions related to the timer:
p00103In the previous protocol, the group timer of an interface is used in the EXCLUDE mode, indicating the
p00104fifteen timeout interval for the router to switch from EXCLUDE mode to INCLUDE mode. The router maintains a source timer for each source record.
p00105In the optimized protocol, a group timer is not used to identify the EXCLUDE mode but is used to indicate a group of non-specific sources. In this case, the behaviors related to the group timer are described in Table 3:
p00106twenty Table 3
<dl><dt>Group Timer Value </dt><dd>Meaning and Action </dd></dl>
<dl><dt>G_Timer> 0 </dt><dd>Indicates that the connected network has a reception status from the group of non-specific sources. </dd></dl>
<dl><dt>G_Timer = = 0 </dt><dd>It indicates that the connected network does not have a reception status of the group of non-specific sources, where: 1. If a source timer is operating in the group, the network nevertheless has a reception status of the group of specific sources of the group. 2. If all the source timers of the group are exhausted, the network does not have a reception status of the group of specific sources of the group and, in this case, the group registration is deleted.</dd></dl>
p00107c. Forwarding rule of specific sources
p00108In the optimized protocol, when a multicast router connected to a subnet receives a multicast packet, the router has to determine if it forwards the packet to the subnet according to the IGMPv3 / MLDv2 information. The specific determination rule is described in Table 4:
p0010925 Table 4
<dl><dt>Group Timer </dt><dd>Source Timer Value Recommended Action </dd></dl>
<dl><dt>G_TIMER == 0 </dt><dd>S_TIMER> 0 Resend packets from the source. </dd></dl>
<dl><dt>G_TIMER == 0 </dt><dd>S_TIMER == 0 Discontinue packet forwarding from the source and delete the source record. If the group does not have another source record, delete the entire group record.</dd></dl>
<dl><dt>G_TIMER == 0 </dt><dd>Empty font list Do not forward packets from the source. </dd></dl>
<dl><dt>G_TIMER> 0 </dt><dd>S_TIMER> = 0 Resend packets from the source. </dd></dl>
<dl><dt>G_TIMER> 0 </dt><dd>Empty font list Resend packets from the source. </dd></dl>
p00110d. Receiving a report of the current membership status from a node:
p00111In the previous protocol, after receiving a record of the current status of the group, the router has to update the group timer and the source timer, and, as a result, it can also change the filtering mode of the router. In the optimized protocol, the actions are described in Table 5:
p00113Table 5
<dl><dt>Group Timer </dt><dd>Antigua Font List Report Received New Source List Action on IGMPv3 / MLDv2 </dd></dl>
<dl><dt>G_TIMER = 0 </dt><dd>TO IS_IN (B) A + B Set timer B with the value of GMI / MALI. </dd></dl>
<dl><dt>G_TIMER = 0 </dt><dd>TO IS_EX (NULL) TO Set the group timer with the value of the GMI / MALI. </dd></dl>
<dl><dt>G_TIMER> 0 </dt><dd>TO IS_IN (B) A + B Set timer B with the value of GMI / MALI. </dd></dl>
<dl><dt>G_TIMER> 0 </dt><dd>TO IS_EX (NULL) TO Set the group timer with the value of the GMI / MALI. </dd></dl>
p00114The Group Member Interval (GMI) is the group membership timer defined in IGMPv3; The Listening Interval of the Multicast Directorate (MALI) is the counterpart of the GMI in the MLDv2.
p00115and. Receiving a record of changing the filter mode and changing the source list:
p001165 In the prior art, when a message is received indicating the change of a filtering mode or a list of sources, a series of processing and switching actions will be carried out. In the optimized protocol, a router does not configure or change the filtering mode, but instead processes membership reports received only in the INCLUDE mode. This means that the router only processes change log reports from the source list. The corresponding actions are described in Table 6.
p0011710 Table 6
<dl><dt>Group Timer </dt><dd>Antigua Font List Report Received New Source List Action on IGMPv3 / MLDv2 </dd></dl>
<dl><dt>G_TIMER = 0 </dt><dd>TO ALLOW (B). A + B Set timer B with the value of GMI / MALI </dd></dl>
<dl><dt>G_TIMER = 0 </dt><dd>TO BLOCK (B) TO Send a query message: Q (G, A * B). </dd></dl>
<dl><dt>G_TIMER = 0 </dt><dd>TO TO_IN (B) A + B Set timer B with the value of GMI / MALI. Send a query message: Q (G, AB).</dd></dl>
<dl><dt>G_TIMER> 0 </dt><dd>TO ALLOW (B) A + B Set timer B with the value of GMI / MALI. </dd></dl>
<dl><dt>G_TIMER> 0 </dt><dd>TO BLOCK (B) TO Send a query message: Q (G, A * B). </dd></dl>
<dl><dt>G_TIMER> 0 </dt><dd>TO TO_IN (B) A + B Set timer B with the value of GMI / MALI. Send a query message: Q (G, AB). Send a query message: Q (G).</dd></dl>
p001185. Processing related to compatibility with other versions of IGMP / MLD (INCLUDE and ANY are taken as an example, EXCLUDE and NULL can be inferred):
p00119RFC3376 and RFC3810 describe the method for the compatibility of IGMPv3 / MLDv2 with IGMPv2 / IGMPv1 / MLDv1. The optimized IGMPv3 / MLDv2 and the above IGMPv3 / MLDv2 have the same compatibility rules. However, due to the change in the filtering mode, some kind of special processing is adopted.
p00120to. Compatibility with IGMPv1 / IGMPv2 / MLDv1 as described in Table 7:
p00122Table 7 a. Compatibility with IGMPv3 / MLDv2 as described in Table 8:
<dl><dt>IGMPv3 / MLDv2 Optimized </dt><dd>IGMPv1 IGMPv2 / MLDv1 </dd></dl>
<dl><dt>IS_IN (ALL) </dt><dd>Report Report </dd></dl>
<dl><dt>TO_IN ({}) </dt><dd>Leave / Done </dd></dl>
<dl><dt>IS_IN (A) </dt><dd>Report Report </dd></dl>
p00123Table 8
<dl><dt>IGMPv3 / MLDv2 </dt><dd>IGMPv3 / MLDv2 Optimized </dd></dl>
<dl><dt>IS_EX ({}) </dt><dd>IS_EX ({}) / IS_IN (ANY) </dd></dl>
<dl><dt>IS_IN (A) </dt><dd /><dt>IS_IN (A) </dt><dd /></dl>
<dl><dt>IS_EX (A) </dt><dd>IS_EX ({}) / IS_IN (ANY) </dd></dl>
<dl><dt>TO_IN (A) </dt><dd /><dt>TO_IN (A) </dt><dd /></dl>
<dl><dt>TO_EX (A) </dt><dd>IS_EX ({}) / IS_IN (ANY) </dd></dl>
<dl><dt>ALLOW (A) </dt><dd /><dt>ALLOW (A) </dt><dd /></dl>
<dl><dt>BLOCK (A) </dt><dd /><dt>BLOCK (A) </dt><dd /></dl>
p00124It is clear that those skilled in the art can make various modifications and variations to the invention without departing from the scope of the invention. The invention is intended to cover modifications and variations provided that they fall within the scope of protection defined by the claims or their equivalents.
2 priority claims, no other members on record
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 200610080979 | China | A | |
| 2006003289 | China | W |
Numbers
- Publication
- 2428372
- Application
- 6828243
Titles2
- Spanish
- Método para la optimización del protocolo de gestión de grupos, y servidor y sistema del mismo
- English
- Method for optimizing the group management protocol, and its server and system
Classification
- CPC, 2
- H04L12/185
- H04L63/0236
- IPC, 2
- H04L12 18
- H04L29 06