Multicast source discovery method and communication equipment

Abstract

The embodiment of the invention provides a multicast source discovery method and communication equipment, the method can be applied to a last-hop multicast router, and the method comprises the following steps: responding to local join of a multicast group, generating a request message, and flooding the request message in a multicast domain; wherein the request message is used for requesting multicast source information corresponding to the multicast group; and receiving a response message from a first hop multicast router in the multicast domain, and obtaining the multicast source information according to the response message, the response message being a feedback message generated by the first hop multicast router for the request message, and the response message comprising the multicast source information.

Description

Technical Field

[0001] This application relates to the field of multicast technology in the communication field, and in particular, to a multicast source discovery method and a communication device. Background Art

[0002] In the multicast source discovery mechanism in the related art, the first-hop multicast router connected to the multicast source periodically floods PIM Flooding Mechanism (PFM) protocol packets carrying multicast source information. The PFM protocol packets are flooded hop by hop to the entire Protocol Independent Multicast (PIM) domain, and each router that receives the PFM protocol packets can learn the multicast group and the corresponding multicast source information. However, this method requires flooding a large number of PFM protocol packets periodically (default 60 seconds), resulting in a large network overhead. Summary of the Invention

[0003] The objective of the embodiments of this application is to provide a multicast source discovery method and a communication device, which can solve the problem of large network overhead of the multicast source discovery method.

[0004] In a first aspect, an embodiment of this application provides a multicast source discovery method, which is applied to a last-hop multicast router and includes: generating a request packet in response to a local join of a multicast group, and flooding the request packet within the multicast domain; where the request packet is used to request multicast source information corresponding to the multicast group; receiving a response packet from a first-hop multicast router within the multicast domain, and obtaining the multicast source information according to the response packet, where the response packet is a feedback packet generated by the first-hop multicast router for the request packet, and the response packet includes the multicast source information.

[0005] In a second aspect, an embodiment of this application provides a multicast source discovery method, which is applied to a first-hop multicast router and includes: receiving a request packet, where the request packet is generated by a last-hop multicast router within the multicast domain in response to a local join of a multicast group and flooded within the multicast domain, and the request packet is used to request multicast source information corresponding to the multicast group; generating a response packet in response to the request packet and sending the response packet, where the response packet includes the multicast source information.

[0006] In a third aspect, an embodiment of the present application provides a communication device, such as a last-hop multicast router, including the following modules: a communication module, configured to generate a request message in response to a local join of a multicast group, and flood the request message within the multicast domain; wherein the request message is used to request multicast source information corresponding to the multicast group; the communication module is further configured to receive a response message from a first-hop multicast router within the multicast domain, and obtain the multicast source information according to the response message, wherein the response message is a feedback message generated by the first-hop multicast router in response to the request message, and the response message includes the multicast source information.

[0007] In a fourth aspect, an embodiment of the present application provides a communication device, such as a first-hop multicast router, including the following modules: a communication module, configured to receive a request message, which is generated by a last-hop multicast router within a multicast domain in response to a local join of a multicast group and flooded within the multicast domain, and the request message is used to request multicast source information corresponding to the multicast group; the communication module is further configured to generate a response message and send the response message in response to the request message, and the response message includes the multicast source information.

[0008] In a fifth aspect, an embodiment of the present application provides a communication device, including: a memory, a processor, and computer-executable instructions stored on the memory and executable on the processor, and when the computer-executable instructions are executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0009] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0010] In the embodiment of the present application, it is only necessary to flood the request message and the response message when a multicast group locally joins, without the need for the first-hop multicast router to flood periodically, reducing the frequency of flooding of PIM protocol messages in the network and facilitating the saving of network overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0012] Figure 1 A flowchart showing the multicast source discovery method provided by the embodiment of the present application;

[0013] Figure 2 A schematic structural diagram showing the multicast group and multicast source request TLV provided by an embodiment of the present application;

[0014] Figure 3 A schematic structural diagram showing the multicast group and multicast source PIM protocol response message provided by an embodiment of the present application;

[0015] Figure 4 A schematic structural diagram showing the multicast group and multicast source advertisement TLV provided by another embodiment of the present application;

[0016] Figure 5 A schematic flow diagram showing a method for discovering a multicast source provided by another embodiment of the present application;

[0017] Figure 6 A schematic structural diagram showing the last-hop multicast router provided by an embodiment of the present application;

[0018] Figure 7 A schematic structural diagram showing the first-hop multicast router provided by an embodiment of the present application;

[0019] Figure 8 A schematic hardware structure diagram of a communication device for executing the multicast source discovery method provided by an embodiment of the present application. Detailed implementation manners

[0020] In order to enable those skilled in the art to better understand the technical solutions in the present application, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0021] In order to solve the problem of large network overhead caused by the periodic flooding of PFM protocol messages by the first-hop multicast router, an embodiment of the present application provides a method for discovering a multicast source. The last-hop multicast router connected to the receiver requests multicast source information, and the first-hop multicast router responds, thereby reducing the network overhead of periodic protocol message flooding and also reducing the storage overhead of non-related routers for processing and storing a large amount of information.

[0022] Figure 1 A schematic flow diagram showing a method for discovering a multicast source provided by an embodiment of the present application. This method can be executed by the last-hop multicast router. In other words, the method can be executed by software or hardware installed in the last-hop multicast router. As Figure 1 shown, the method may include the following steps.

[0023] S102: Generate a request message in response to a local join of a multicast group, and flood the request message within the multicast domain; wherein, the request message is used to request multicast source information corresponding to the multicast group.

[0024] The embodiments of the present application can be applied in Protocol Independent Multicast - Sparse Mode (PIM - SM). The last - hop multicast router directly connected to the receiver can generate a request message in the case of a local join of the multicast group, and flood the request message within the multicast domain.

[0025] Specifically, the last - hop multicast router can generate and send a request message upon receiving a local join of the multicast group of the Internet Group Management Protocol (IGMP) or Multicast Listener Discover (MLD).

[0026] Optionally, the above - mentioned request message can be a PFM protocol message including a multicast group and a Group Source Request (GSReq) Type Length Value (TLV).

[0027] Optionally, the above - mentioned request message is flooded and sent hop - by - hop according to a first time interval and a first number of transmissions, so as to quickly learn multicast source information.

[0028] Optionally, the request message carries at least one of the multicast groups, and the request message is used to request multicast source information corresponding to each of the carried multicast groups; or, the multicast group field in the request message is a specific value, and the specific value is used to indicate requesting multicast source information corresponding to all multicast groups in the first - hop multicast router.

[0029] Optionally, the request message includes an originator address field, and the originator address field represents the routing reachable address of the last - hop multicast router, and the routing reachable address is used to instruct the first - hop multicast router to determine the destination address of the response message.

[0030] As Figure 2 shown, Figure 2 is an optional structural schematic diagram of a multicast group and a Group Source Request TLV. The request message can be a PFM message carrying a multicast group and a Group Source Request TLV, as shown in Figure 2 the Group Source Request TLV in.

[0031] Among them, the T field is a transferable flag, which is set to 1 in the multicast group and multicast source request TLV, indicating that the router should continue to forward even if it does not support this TLV.

[0032] The Type field indicates that this TLV is a multicast group and multicast source request TLV, and the specific value is to be defined.

[0033] The Length field is the total length of the carried Group Address field.

[0034] The Group Address field is used to indicate the multicast group information for which multicast source information is requested.

[0035] In this embodiment, when the last-hop multicast router receives a local multicast group join of IGMP or MLD, it generates a PFM protocol message carrying the multicast group and multicast source request TLV as shown in Figure 2 . The multicast group and multicast source request TLV can carry one or more multicast groups, indicating the multicast source information for each carried multicast group. It should be noted that when the multicast group address is a specific value of 0, it indicates a request for the multicast source information corresponding to all multicast groups in the first-hop multicast router.

[0036] In this embodiment, the last-hop multicast router can set the first transmission time interval and the first transmission count for sending the PFM protocol message carrying the multicast group and multicast source request TLV, so as to quickly learn the multicast source information. In one example, when generating a local multicast group join entry, the PFM protocol message carrying the multicast group and multicast source request TLV is sent in a pulsed manner. Within one pulse, two PFM protocol messages are continuously sent at an interval of 3 seconds, and three pulses are sent at an interval of 10 seconds. Additionally, an early stop condition can also be set. If a certain number of multicast source information has been learned, the sending can be stopped to reduce network overhead.

[0037] The originator address field in the PFM protocol message carrying the multicast group and multicast source request TLV is filled with an address reachable within a certain domain route of the last-hop multicast router. This address will be used as the destination address of the response message.

[0038] S104: Receive a response message from the first-hop multicast router in the multicast domain, and obtain the multicast source information according to the response message, where the response message is a feedback message generated by the first-hop multicast router for the request message, and the response message includes the multicast source information.

[0039] Optionally, the response message is a unicast PIM protocol reply message; or the response message is a PFM advertisement message.

[0040] In this embodiment, the request message (such as a PFM protocol message with a multicast group and multicast source request TLV) can be flooded hop by hop to the entire PIM domain. When the first-hop multicast router receives a PFM protocol message with a multicast group and multicast source request TLV, it generates a response message according to the multicast group carried in the PFM protocol message. The response message can be a PIM protocol message including a multicast group and a Group Source Reply (GSRep) message, and advertises the multicast source information of a specific multicast group or all multicast groups.

[0041] Such as Figure 3 shown, Figure 3 is a schematic structural diagram of a PIM protocol response message for a multicast group and a multicast source, Figure 3 which is an example of a response message.

[0042] Among them, the Type field indicates that the PIM protocol message type is a multicast group and multicast source reply message type, and the specific value is to be defined.

[0043] The Group Count field indicates the number of multicast groups carried in the multicast group and multicast source reply message.

[0044] After each multicast group, the multicast source associated with it is recorded. The multicast source is a directly connected source of the first-hop multicast router, and can also include multicast source information learned from the Multicast Source Discovery Protocol (MSDP) or the Multicast VPN Source Active A-D according to local policies.

[0045] In this embodiment, when the first-hop multicast router receives a PFM protocol message with a multicast group and multicast source request TLV, it responds with a PIM protocol message for a multicast group and multicast source reply message. The PIM protocol message for a multicast group and multicast source reply message can be a unicast message. The source IP address of the message is filled with the outgoing interface address of the first-hop multicast router, and the destination IP address is filled with the address indicated by the originator address field in the received PFM message with a multicast group and multicast source request TLV. The first-hop multicast router unicasts the PIM protocol message for a multicast group and multicast source reply message to the last-hop multicast router. Intermediate nodes do not need to process or learn the multicast group and multicast source information in the PIM protocol message for a multicast group and multicast source reply message except for unicast forwarding. The last-hop multicast router learns the multicast group and multicast source information locally, and the learned information will not be aged and deleted over time.

[0046] In the multicast source discovery method provided by the embodiments of the present application, the last-hop multicast router generates a request message in response to a local join of a multicast group, and floods the request message within the multicast domain. The request message is used to request multicast source information corresponding to the multicast group. The first-hop multicast router makes a feedback to the request message and sends a response message including the multicast source information. In this way, the last-hop multicast router can obtain the multicast source information according to the response message. In the embodiments of the present application, only when a local join of a multicast group occurs, it is necessary to flood the request message and the response message, without the first-hop multicast router flooding periodically. This reduces the frequency of flooding of PIM protocol messages in the network, thereby reducing the bandwidth occupied by the periodic flooding of PIM protocol messages in the network, and reducing the CPU resources occupied by the periodic learning and updating of devices, which helps to save network overhead.

[0047] The embodiments of the present application can also reduce the number of protocol messages that non-network boundary devices need to process, and can enable newly connected receivers to quickly learn multicast source information without each multicast router in the network storing a large amount of multicast group and multicast source information.

[0048] The embodiments of the present application can be applied to any scenario where PIM-SM multicast is used.

[0049] Optionally, based on any of the above embodiments, the method further includes the following steps: receiving an advertisement message from the first-hop multicast router, where the advertisement message is used to indicate an update message of a target multicast source. The update message of the target multicast source is generated by the first-hop multicast router when at least one of a new multicast source appears or an original multicast source fails. For example, it is generated when at least one of a new (multicast source, multicast group) entry appears or an original (multicast source, multicast group) entry is deleted and fails. The target multicast source includes the new multicast source or the failed original multicast source; updating the local multicast source information according to the advertisement message.

[0050] Optionally, the advertisement message is sent at a second time interval and a second number of times, so as to be able to quickly learn multicast source information.

[0051] Optionally, the advertisement message includes a type field, and the indication information of the type field is used to indicate that the last-hop multicast router processes the advertisement message, and the intermediate multicast router only forwards the advertisement message, reducing the processing and storage overhead of the intermediate router.

[0052] Optionally, the advertisement message includes a hold time field, and updating the local multicast source information according to the advertisement message includes: when the hold time field has a first value, determining that the target multicast source is a newly added multicast source and adding the target multicast source locally; or, when the hold time field has a second value, determining that the target multicast source has failed and deleting the target multicast source.

[0053] In this embodiment, when a new multicast source appears on the first-hop multicast router, an advertisement message is generated and sent. The advertisement message can be a PFM protocol message carrying a Group Source Advertisement (GS AD) TLV. The hold time field can have two valid values, a first value (such as the maximum value) and a second value (such as 0). The maximum value indicates that a new multicast source has appeared and never times out, and the value 0 indicates that the multicast source has failed and needs to be deleted immediately.

[0054] Figure 4 FIG. is an optional schematic diagram of the structure of the Group Source Advertisement TLV. The advertisement message can carry the Group Source Advertisement TLV in the PFM message. See Figure 4 the Group Source Advertisement TLV in

[0055] The structure of the Group Source Advertisement TLV is similar to the structure of the Multicast Group and Source Hold Time TLV defined in RFC8364, but the processing procedures are different.

[0056] The Type field is used to indicate that this TLV is the Group Source Advertisement TLV. When a new multicast source appears, the first-hop multicast router sends a PFM protocol message with the Group Source Advertisement TLV and sets the Src Holdtime field to 0xFFFF, indicating that a new multicast source has appeared. When the original multicast source fails, the first-hop multicast router sends a PFM protocol message with the Group Source Advertisement TLV, but sets the Src Holdtime field to 0. The first-hop multicast router can set the transmission time interval and the number of transmissions of the PFM protocol message with the Group Source Advertisement TLV, so that the last-hop multicast router can quickly learn about the newly appeared multicast source. Optionally, when a new multicast source is discovered, the PFM protocol message carrying the Group Source Advertisement TLV is sent in a pulsed manner. Within one pulse, two PFM protocol messages are continuously sent at an interval of 5 seconds, and three pulses are sent at an interval of 30 seconds.

[0057] By default, only the last-hop multicast router processes this TLV. Intermediate routers only forward but do not process or learn this TLV. When the last-hop multicast router receives a PFM protocol packet with a Src Holdtime of 0xFFFF in the multicast group and multicast source advertisement TLV or receives a PIM protocol packet for the multicast group and multicast source response, it learns the multicast group and multicast source information carried in the protocol packet, and this information will not be aged and deleted. Only when it receives a PFM protocol packet with a Src Holdtime of 0 in the multicast group and multicast source advertisement TLV will the corresponding multicast group and multicast source information be deleted.

[0058] It should be noted that in another implementation, the PIM protocol packet for the multicast group and multicast source response message can be omitted. The PFM protocol packet with the multicast group and multicast source advertisement TLV is used both as the response when the first-hop multicast router receives a PFM protocol packet with the multicast group and multicast source request TLV and as the flooding advertisement when a new multicast source appears.

[0059] Or in another implementation, after appropriately expanding the multicast group and multicast source hold time TLV in the existing RFC8364 and combining it with the newly added multicast group and multicast source request TLV of this application. The first-hop multicast router sets the Src Holdtime in the multicast group and multicast source hold time TLV to 0xFFFF and floods it once every 18724 seconds by default. When it receives a PFM sent by the last-hop multicast router with the multicast group and multicast source request TLV, it floods it immediately. This can also partially achieve reducing flooding while receivers can quickly learn multicast source information.

[0060] The above combination Figure 1 has described in detail the multicast source discovery method according to the embodiments of this application. Next, it will be combined with Figure 5 to describe in detail the multicast source discovery method according to another embodiment of this application. It can be understood that the interaction between the first-hop multicast router and the last-hop multicast router described from the first-hop multicast router is the same as or corresponding to the description on the last-hop multicast router side in the method shown in Figure 1 To avoid repetition, the relevant description is appropriately omitted.

[0061] Figure 5 is a schematic diagram of the implementation process of the multicast source discovery method according to the embodiments of this application and can be applied to the first-hop multicast router. As Figure 5 shown, this method 500 includes the following steps.

[0062] S502: Receive a request packet, where the request packet is generated by the last-hop multicast router in the multicast domain in response to the local join of a multicast group and flooded in the multicast domain, and the request packet is used to request multicast source information corresponding to the multicast group.

[0063] As shown in Figure 2 the figure Figure 2 below, it is a schematic diagram of an optional structure of a multicast group and a multicast source request TLV. The request message can carry the multicast group and the multicast source request TLV in the PFM message. See the Group Source Request TLV in Figure 2 .

[0064] S504: In response to the request message, generate a response message and send the response message, where the response message includes the multicast source information.

[0065] As shown in Figure 3 the figure Figure 3 below, it is a schematic diagram of the structure of a multicast group and a multicast source PIM protocol response message, Figure 3 which is an example of a response message.

[0066] In the embodiments of the present application, it is only necessary to flood the request message and the response message when the multicast group is locally joined, without the first-hop multicast router flooding periodically, reducing the frequency of PIM protocol message flooding in the network and facilitating saving network overhead.

[0067] Optionally, as an embodiment, the request message carries at least one of the multicast groups, and the request message is used to request the multicast source information corresponding to each carried multicast group; or the multicast group field in the request message is a specific value, and the specific value is used to indicate requesting the multicast source information corresponding to all multicast groups in the first-hop multicast router.

[0068] Optionally, as an embodiment, the response message is a unicast PIM protocol response message; or the response message is a PFM advertisement message.

[0069] Optionally, as an embodiment, the response message is a PIM protocol response message. Before sending the response message, the method further includes: determining the destination address of the PIM protocol response message based on the originator address field in the request message; where the originator address field represents the routable address of the last-hop multicast router.

[0070] Optionally, as an embodiment, the method further includes: sending an advertisement message, where the advertisement message is used to indicate an update message of a target multicast source, and the update message of the target multicast source is generated by the first-hop multicast router in at least one of the cases of adding a new multicast source or the failure of an original multicast source, and the target multicast source includes the new multicast source or the failed original multicast source.

[0071] Figure 4It is a schematic diagram of an optional structure for the multicast group and multicast source advertisement TLV. The advertisement message can carry the multicast group and multicast source advertisement TLV in the PFM message. See Figure 4 the Group Source Advertisement TLV in

[0072] Optionally, as an embodiment, the advertisement message includes a hold time field. Before sending the advertisement message, the method further includes: when the target multicast source is a newly added multicast source, setting the hold time field to a first value; or, when the target multicast source fails, setting the hold time field to a second value.

[0073] Figure 6 It shows a schematic diagram of the structure of the last-hop multicast router 600 provided by an embodiment of the present application. The last-hop multicast router 600 includes the following modules.

[0074] A communication module 602, configured to generate a request message in response to a local join of a multicast group, and flood the request message within the multicast domain; wherein, the request message is used to request multicast source information corresponding to the multicast group.

[0075] The communication module 602 is further configured to receive a response message from the first-hop multicast router within the multicast domain, and obtain the multicast source information according to the response message, where the response message is a feedback message generated by the first-hop multicast router for the request message, and the response message includes the multicast source information.

[0076] Optionally, the last-hop multicast router 600 further includes a processing module and the like.

[0077] In the embodiment of the present application, it is only necessary to flood the request message and the response message when a multicast group locally joins, without the first-hop multicast router flooding periodically, reducing the frequency of PIM protocol message flooding in the network and facilitating saving network overhead.

[0078] Optionally, as an embodiment, the request message carries at least one of the multicast groups, and the request message is used to request multicast source information corresponding to each of the carried multicast groups; or the multicast group field in the request message is a specific value, and the specific value is used to indicate requesting multicast source information corresponding to all multicast groups in the first-hop multicast router.

[0079] Optionally, as an embodiment, the response message is a unicast PIM protocol reply message; or the response message is a PFM advertisement message of the PIM flooding mechanism.

[0080] Optionally, as an embodiment, the request message includes an originator address field, and the originator address field characterizes the routing reachable address of the last-hop multicast router, and the routing reachable address is used to instruct the first-hop multicast router to determine the destination address of the response message.

[0081] Optionally, as an embodiment, the communication module 602 is further configured to receive an advertisement message from the first-hop multicast router, where the advertisement message is used to indicate an update message of a target multicast source, and the update message of the target multicast source is generated by the first-hop multicast router when at least one of a new multicast source is added or an original multicast source fails, and the target multicast source includes the new multicast source or the failed original multicast source; and update the local multicast source information according to the advertisement message.

[0082] Optionally, as an embodiment, the advertisement message includes a hold time field, and the communication module 602 is specifically configured to: when the hold time field is a first value, determine that the target multicast source is a new multicast source and add the target multicast source locally; or, when the hold time field is a second value, determine that the target multicast source fails and delete the target multicast source.

[0083] The last-hop multicast router 600 provided in the embodiments of the present application can execute the various methods described in the foregoing method embodiments, and implement the functions and beneficial effects of the various methods described in the foregoing method embodiments, which will not be elaborated herein.

[0084] Figure 7 FIG. shows a schematic structural diagram of a first-hop multicast router 700 provided in an embodiment of the present application, and the first-hop multicast router 700 includes the following modules.

[0085] The communication module 702 is configured to receive a request message, where the request message is generated by the last-hop multicast router in the multicast domain in response to a local join of a multicast group and flooded in the multicast domain, and the request message is used to request multicast source information corresponding to the multicast group.

[0086] The communication module 702 is further configured to generate a response message and send the response message in response to the request message, where the response message includes the multicast source information.

[0087] Optionally, the first-hop multicast router 700 further includes a processing module and the like.

[0088] In the embodiments of the present application, it is only necessary to flood the request message and the response message when a multicast group is locally joined, and it is not necessary for the first-hop multicast router to flood periodically, which reduces the frequency of flooding of PIM protocol messages in the network and is convenient for saving network overhead.

[0089] Optionally, as an embodiment, the request message carries at least one of the multicast groups, and the request message is used to request multicast source information corresponding to each of the carried multicast groups; or the multicast group field in the request message is a specific value, and the specific value is used to indicate a request for multicast source information corresponding to all multicast groups in the first-hop multicast router.

[0090] Optionally, as an embodiment, the response message is a unicast PIM protocol reply message; or the response message is a PFM advertisement message.

[0091] Optionally, as an embodiment, the response message is a PIM protocol reply message, and the communication module 702 is further configured to determine the destination address of the PIM protocol reply message based on the originator address field in the request message; wherein, the originator address field represents the routable address of the last-hop multicast router.

[0092] Optionally, as an embodiment, the communication module 702 is further configured to send an advertisement message, and the advertisement message is used to indicate an update message of a target multicast source, and the update message of the target multicast source is generated by the first-hop multicast router when at least one of a new multicast source is added or an original multicast source fails, and the target multicast source includes the new multicast source or the failed original multicast source.

[0093] Optionally, as an embodiment, the advertisement message includes a hold time field, and the communication module 702 is further configured to set the hold time field to a first value when the target multicast source is a new multicast source; or set the hold time field to a second value when the target multicast source fails.

[0094] The first-hop multicast router 700 provided in the embodiment of the present application can execute the various methods described in the foregoing method embodiments, and implement the functions and beneficial effects of the various methods described in the foregoing method embodiments, which will not be elaborated herein.

[0095] Figure 8 FIG. shows a schematic hardware structure diagram of a communication device provided in an embodiment of the present application. Referring to this figure, at the hardware level, the communication device includes a processor, and optionally includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (Random-Access Memory, RAM), and may also include a non-volatile memory, such as at least one disk memory, etc. Of course, the communication device may also include other hardware required for other services.

[0096] The processor, network interface, and memory can be interconnected through an internal bus, which can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience in representation, only a bidirectional arrow is used in this figure, but it does not mean that there is only one bus or one type of bus.

[0097] A memory for storing programs. Specifically, the program can include program code, and the program code includes computer operation instructions. The memory can include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0098] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a device for locating the target user at the logical level. The processor executes the program stored in the memory and is specifically used to execute: Figures 1-5 The method disclosed in the illustrated embodiment and realizes the functions and beneficial effects of the various methods described in the foregoing method embodiments, which will not be elaborated herein.

[0099] The above as in this application Figures 1-5The method disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuit in the hardware of the processor or by instructions in software form. The above-mentioned processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or can be executed and completed by a combination of the hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0100] The communication device can also execute the various methods described in the foregoing method embodiments and achieve the functions and beneficial effects of the various methods described in the foregoing method embodiments, which will not be elaborated herein.

[0101] Of course, in addition to the software implementation manner, the communication device of the present application does not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, and can also be hardware or a logic device.

[0102] The embodiments of the present application also propose a computer-readable storage medium. The computer-readable medium stores one or more programs. When the one or more programs are executed by a communication device including a plurality of application programs, the communication device is caused to execute Figures 1-5 the method disclosed in the illustrated embodiment and achieve the functions and beneficial effects of the various methods described in the foregoing method embodiments, which will not be elaborated herein.

[0103] Among them, the computer-readable storage medium includes a read-only memory (ROM for short), a random access memory (RAM for short), a magnetic disk, an optical disc, etc.

[0104] Furthermore, the embodiment of the present application also provides a computer program product. The computer program product includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions. When the program instructions are executed by a computer, the following processes are implemented: Figures 1-5 The method disclosed in the illustrated embodiment implements the functions and beneficial effects of each method described in the foregoing method embodiments, which will not be elaborated herein.

[0105] In summary, the above are only the preferred embodiments of the present application and are not intended to limit the protection scope of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0106] The systems, devices, modules or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0107] Computer-readable media includes both permanent and non-permanent, removable and non-removable media and can be implemented by any method or technology for storing information. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0108] It should also be noted that the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, such that a process, method, commodity or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the presence of additional identical elements in the process, method, commodity or device comprising said element.

[0109] Each embodiment in this specification is described in a progressive manner. For the identical and similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the relevant parts, reference can be made to the partial description of the method embodiment.

Claims

1. A multicast source discovery method, applied to a last-hop multicast router, includes: Responding to a local join of a multicast group, generating a request message, and flooding the request message within the multicast domain; wherein, the request message is used to request multicast source information corresponding to the multicast group; Receiving a response message from a first-hop multicast router within the multicast domain, and obtaining the multicast source information according to the response message, wherein the response message is a feedback message generated by the first-hop multicast router for the request message, and the response message includes the multicast source information.

2. The method according to claim 1, wherein, The request message carries at least one of the multicast groups, and the request message is used to request multicast source information corresponding to each of the carried multicast groups; or The multicast group field in the request message is a specific value, and the specific value is used to indicate requesting multicast source information corresponding to all multicast groups in the first-hop multicast router.

3. The method according to claim 1, wherein, The response message is a unicast Protocol Independent Multicast (PIM) protocol reply message; or The response message is a PIM Flooding Mechanism (PFM) advertisement message.

4. The method according to claim 1, wherein The request message includes an originator address field, and the originator address field represents the routing reachable address of the last-hop multicast router, and the routing reachable address is used to instruct the first-hop multicast router to determine the destination address of the response message.

5. The method according to claim 1, wherein, The method further includes: Receiving an advertisement message from the first-hop multicast router, the advertisement message being used to indicate an update message of a target multicast source, and the update message of the target multicast source being generated by the first-hop multicast router in at least one of the cases of adding a new multicast source or the failure of an original multicast source, and the target multicast source including the new multicast source or the failed original multicast source; Updating the local multicast source information according to the advertisement message.

6. The method according to claim 5, wherein, The advertisement message includes a hold time field, and updating the local multicast source information according to the advertisement message includes: When the hold time field is a first value, determining that the target multicast source is a new multicast source and adding the target multicast source locally; or, When the hold time field is a second value, determining that the target multicast source has failed and deleting the target multicast source.

7. A multicast source discovery method, applied to a first-hop multicast router, includes: Receiving a request message, the request message being generated by a last-hop multicast router within the multicast domain in response to a local join of a multicast group and flooded within the multicast domain, and the request message being used to request multicast source information corresponding to the multicast group; Responding to the request message, generating a response message and sending the response message, the response message including the multicast source information.

8. The method according to claim 7, wherein, The request message carries at least one of the multicast groups, and the request message is used to request multicast source information corresponding to each of the carried multicast groups; or The multicast group field in the request message is a specific value, and the specific value is used to indicate requesting multicast source information corresponding to all multicast groups in the first-hop multicast router.

9. The method according to claim 7, wherein the response message is a unicast PIM protocol response message; or the response message is a PFM advertisement message.

10. The method according to claim 7, wherein The response message is a PIM protocol response message. Before sending the response message, the method further includes: determining a destination address of the PIM protocol response message based on an originator address field in the request message; wherein the originator address field represents a routable address of the last-hop multicast router.

11. The method according to claim 7, wherein, The method further includes: sending an advertisement message for indicating an update message of a target multicast source, the update message of the target multicast source being generated by the first-hop multicast router when at least one of a new multicast source is added or an original multicast source fails, and the target multicast source including the new multicast source or the failed original multicast source.

12. The method according to claim 11, wherein, The advertisement message includes a hold time field. Before sending the advertisement message, the method further includes: when the target multicast source is a new multicast source, setting the hold time field to a first value; or when the target multicast source fails, setting the hold time field to a second value.

13. A communication device, comprising: a processor; and a memory arranged to store computer-executable instructions that, when executed, use the processor to perform the steps of the method according to any one of claims 1-12.

14. A computer-readable medium storing one or more programs that, when executed by a communication device including a plurality of application programs, cause the communication device to perform the steps of the method according to any one of claims 1-12.

Images