WO2020168982A1 - 一种发送和获取断言报文的方法和网络节点 - Google Patents

一种发送和获取断言报文的方法和网络节点 Download PDF

Info

Publication number
WO2020168982A1
WO2020168982A1 PCT/CN2020/075199 CN2020075199W WO2020168982A1 WO 2020168982 A1 WO2020168982 A1 WO 2020168982A1 CN 2020075199 W CN2020075199 W CN 2020075199W WO 2020168982 A1 WO2020168982 A1 WO 2020168982A1
Authority
WO
WIPO (PCT)
Prior art keywords
assert
multicast
records
message
address
Prior art date
Application number
PCT/CN2020/075199
Other languages
English (en)
French (fr)
Inventor
刘毅松
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20759660.2A priority Critical patent/EP3905613A4/en
Publication of WO2020168982A1 publication Critical patent/WO2020168982A1/zh
Priority to US17/382,596 priority patent/US11909546B2/en

Links

Images

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
    • H04L12/1881—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with schedule organisation, e.g. priority, sequence management
    • 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
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/806—Broadcast or multicast traffic
    • 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
    • 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
    • H04L12/1886—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
    • 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/12—Shortest path evaluation
    • H04L45/124—Shortest path evaluation using a combination of metrics
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/48—Routing tree calculation
    • 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/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • 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/74—Address processing for routing

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a method and device for sending an Assert message.
  • Multicast packets arrive at receivers (members of the multicast group) from the multicast source, and the multicast packets need to be replicated and forwarded through the multicast network.
  • a multicast protocol needs to be configured.
  • the Protocol Independent Multicast (PIM) protocol is currently the most widely used intra-domain multicast protocol.
  • the multicast distribution tree constructed by the PIM protocol can be used to guide the forwarding of multicast packets.
  • the PIM protocol can realize functions such as creating multicast routes on demand, dynamically responding to network topology changes, and performing forwarding according to routing table entries.
  • the PIM protocol runs on devices 101-105.
  • the device 102 sends the multicast packet obtained from the device 101 to the downstream device 104.
  • the device 103 sends the same multicast packet obtained from the device 101 to its downstream device 105.
  • device 106 since device 106 is a layer 2 switching device in a shared network, for example, in a shared area network (LAN), device 106 will send device 102 to downstream devices
  • the multicast packet of 104 is transparently transmitted to other devices 103-105 connected to it, so that the device 103 forwarding the multicast packet will also receive the multicast packet from its outgoing interface, so that the device 103 will find that the device 103 is still in the same LAN.
  • the device 102 If another device forwards the same multicast message, this will trigger the device 103 to multicast an Assert message. After the device 102 receives the Assert message sent from the device 103, it selects the winner according to the Assert election rules to forward the multicast packet, ensuring that a copy of the multicast packet is transmitted in the same LAN.
  • the embodiments of the present application provide a method and device for sending and acquiring Assert messages, which are used to improve the efficiency of processing messages and reduce network device overhead.
  • this application provides a method for sending an Assert message.
  • the method includes a network node determining multiple Assert records based on a multicast source address. Each Assert record in the multiple Assert records respectively includes a multicast source address and a multicast group address, where the multiple Assert records have the same multicast source address, and different Assert records in the multiple Assert records contain The multicast group addresses are different from each other.
  • the network node generates an Assert message according to the multiple Assert records, where the Assert message includes a multicast source address and the multicast group address in the multiple Assert records.
  • the network node multicasts the Assert message.
  • a network node uses the above method to generate an Assert message based on multiple Assert records, and multicasts the Assert message to other network nodes, which can improve the efficiency of sending Assert messages, especially in the scenario where a large number of Assert messages are triggered.
  • the method can reduce equipment processing overhead to shorten the time for repeated multicast traffic.
  • the network node determining multiple Assert records based on a multicast source address includes: the network node determines a first Assert record set based on a multicast source address, and the first Assert record set includes The first Assert record and the second Assert record of the multicast source address.
  • multiple Assert records are determined based on the same multicast source address, and one Assert message is generated according to the multiple Assert records, which further improves the efficiency of sending Assert messages.
  • the network node generating an Assert message according to the multiple Assert records includes: the network node extracts a multicast source address, and combines the multicast of the first Assert record and the second Assert record The group address generates an Assert message.
  • the network node can extract the same multicast source address from multiple Assert records, improve the utilization of Assert messages, and improve the efficiency of sending Assert messages.
  • the method before the network node sends the Asser message, the method further includes that the network node receives a Hello message sent by other network nodes in the multicast network, where the Hello message carries the first identifier, The first identifier is used to indicate that other network nodes in the multicast network support the function of receiving the Assert message.
  • the network node can determine whether the device sending the Hello message has the function of processing the Assert message through the identifier carried in the Hello message.
  • the Assert message carries the number of multicast group addresses.
  • the network node can carry the number of multicast group addresses included in the Assert message in the Assert message.
  • this application provides yet another method for sending an Assert message.
  • the method includes a network node determining a first Assert record set based on an RP address of a convergence point.
  • the first Assert record set includes multiple Assert records, where each Assert record includes a multicast source address and a multicast group address. Different Assert records in the multiple Assert records respectively contain the first multicast group address.
  • the network node generates an Assert message, where the Assert message includes an RP address, the first multicast group address, and multiple multicast source addresses. The network node multicasts the Assert message.
  • the network node uses the above method to generate an Assert message from multiple Assert records according to the RP address, and multicasts the Assert message to other network nodes, which can improve the efficiency of sending Assert messages, especially in scenarios where a large number of Assert messages are triggered.
  • the above method can reduce equipment processing overhead, so as to shorten the time for repeated sending of multicast traffic.
  • the method further includes: the network node determines a second Assert record set based on the RP address, where the second Assert record set includes multiple Assert records.
  • Each Assert record in the second Assert record set includes a multicast source address and a multicast group address respectively.
  • Different Assert records in the multiple Assert records in the second Assert record set respectively contain the second multicast group address, and the Assert message also includes the second multicast group address, the first multicast group address, and the second multicast group address. The group address is different.
  • the Assert message includes multiple different multicast group addresses, which improves the utilization rate of the Assert message and improves the efficiency of sending the Assert message.
  • the network node generating an Assert message includes: the network node extracts the RP address, the multicast group address of the first Assert record set and the second Assert record set, and combines the first Assert The record set and the multicast source address of the second Assert record set generate the Assert message.
  • the network node can extract the same RP address, which improves the utilization rate of Assert messages and the efficiency of sending Assert messages.
  • the method before the network node sends the Asser message, the method further includes: the network node receives the Hello message sent by other network nodes in the multicast network, where the Hello message carries the first identifier , The first identifier is used to indicate that other network nodes in the multicast network support the function of receiving the Assert message.
  • the Assert message carries the number of multicast group addresses and multicast source addresses.
  • a method for acquiring an Assert message in a multicast network includes the network node receiving an Assert message, where the Assert message includes a multicast source address and multiple multicast group addresses.
  • the network node obtains multiple Assert records by parsing the Assert message, and each Assert record in the multiple Assert records respectively includes the multicast source address and one of the multiple multicast group addresses ,
  • the multicast group addresses in the multiple Assert records are different from each other.
  • the network node parsing the Assert message to obtain multiple Assert records includes: the network node combining the multicast source address carried in the Assert message and the multiple multicast group addresses, Obtain the multiple Assert records.
  • a method for obtaining an Assert message in a multicast network includes: the network node receives an Assert message, the Assert message includes a rendezvous RP address and a first Assert record set, the first Assert record set includes The first multicast group address and multiple multicast source addresses.
  • the network node obtains multiple Assert records by parsing the first Assert record set, and each Assert record in the multiple Assert records includes a multicast source address and a multicast group address, and the multiple Assert records are different The Assert records respectively contain the first multicast group address.
  • the Assert message further includes a second Assert record set.
  • the method further includes: the network node parses the second Assert record set to obtain multiple Assert records, and different Assert records in the second Assert record set respectively contain the second multicast group address.
  • the first multicast group address and the second multicast group address are different.
  • an embodiment of the present application provides a network node that sends an Assert message to execute the first aspect or any one of the possible implementation methods of the first aspect.
  • the network node includes a unit for executing the method in the first aspect or any one of the possible implementation manners of the first aspect.
  • the embodiments of the present application provide yet another network node that sends an Assert message, and executes the second aspect or any one of the possible implementation methods of the second aspect.
  • the network node includes a unit for executing the second aspect or any one of the possible implementation manners of the second aspect.
  • an embodiment of the present application provides a network node that obtains an Assert message, and executes the third aspect or any one of the possible implementation methods of the third aspect.
  • the network node includes a unit for executing the third aspect or the method in any one of the possible implementation manners of the third aspect.
  • an embodiment of the present application provides a network node that obtains an Assert message, and executes the fourth aspect or any one of the possible implementation methods of the fourth aspect.
  • the network node includes a unit for executing the fourth aspect or the method in any one of the possible implementation manners of the fourth aspect.
  • a network device for sending or acquiring an Assert message.
  • the device includes a processor, a transceiver, and a memory.
  • the functional modules of the fifth aspect, sixth aspect, seventh aspect, and eighth aspect described above may be implemented by hardware, or implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the transceiver is used to complete the functions of the receiving unit and the transmitting unit
  • the processor is used to complete the functions of the determining, generating, and acquiring unit
  • the memory is used for the processor to process the program instructions of the method of the embodiment of the present application.
  • the processor, the transceiver, and the memory are connected through a bus and communicate with each other.
  • a system for sending and acquiring Assert messages includes the network devices provided in the first and second aspects described above, called the first network device, and the networks provided in the third and fourth aspects.
  • the device is called the second network device.
  • the first network device is configured to determine multiple Assert records based on a multicast source address or RP address; generate an Assert message; and multicast the Assert message.
  • the second network device is configured to receive the Assert message sent by the first network node and obtain multiple Assert records by parsing the Assert message.
  • the present application provides a computer-readable storage medium for storing computer software instructions used by the aforementioned network node, which includes a program designed to execute the aforementioned aspect.
  • Fig. 1 is a schematic diagram of a scenario for sending a multicast packet provided by an embodiment of the application.
  • FIG. 2 is a schematic flowchart of a method for sending an Assert message according to an embodiment of the application.
  • FIG. 3 is a schematic diagram of a message format of an Assert message provided by an embodiment of the application.
  • FIG. 4 is a schematic diagram of another message format of an Assert message provided by an embodiment of the application.
  • FIG. 5 is a schematic diagram of another message format of an Assert message provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of the message format of the PIM Hello message provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of a scenario for forwarding an Assert message provided by an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of a first network device for sending an Assert message according to an embodiment of the application.
  • FIG. 9 is a schematic structural diagram of another first network device for sending an Assert message according to an embodiment of the application.
  • FIG. 10 is a schematic structural diagram of a second network device for acquiring an Assert message according to an embodiment of the application.
  • FIG. 11 is a schematic structural diagram of another second network device for acquiring an Assert message according to an embodiment of the application.
  • FIG. 12 is a schematic structural diagram of a system for sending and obtaining Assert messages according to an embodiment of the application.
  • the network node in the embodiment of the present invention may be a router, a switch, or a network device such as a forwarder in a software-defined network (Software-defined network, SDN).
  • SDN Software-defined network
  • FIG. 1 a schematic diagram of an application scenario for forwarding multicast traffic is provided.
  • This scenario includes a multicast source, network nodes 101-106 and receivers (receiver) 1-4.
  • the nodes in the multicast network support PIM protocol and Internet Group Management Protocol (IGMP), receivers 1-4 can join the multicast group through IGMP, and network nodes 101-106 can use the PIM protocol to construct multicast Distribution tree.
  • the leaf nodes 104 and 105 in the multicast tree can receive multicast packets through the forwarding node 102, and can also receive multicast packets through the forwarding node 103.
  • the leaf node 105 forwards the received multicast message to the receiver 1-2, and the leaf node 106 forwards the received multicast message to the receiver 3-4.
  • the leaf node 104 can join the multicast group G1 through the upstream forwarding node 102, and the leaf node 105 can join the multicast group G1 through the forwarding node 103.
  • the device 106 can be a Layer 2 switch, so that when the multicast traffic sent by the node 102 to the downstream device 104 through the device 106 is forwarded, the multicast traffic is transparently transmitted to the forwarding node 103 and the leaves through the device 106.
  • the node 105 enables the outgoing interface of the forwarding node 103 to receive the multicast traffic sent downstream, which causes the multicast traffic to be forwarded.
  • the forwarding node 102 may check to discard the multicast traffic received from the downstream interface through reverse path forwarding (RPF), and trigger the forwarding node 102 to send an Assert message.
  • RPF reverse path forwarding
  • the RPF check is used to realize a loop-free forwarding of multicast packets, that is, the RPF mechanism ensures that multicast packets are received from the correct interface, and multicast packets that pass the RPF check can be forwarded along the multicast tree. If the packet is received from the wrong interface, the network device will discard the multicast packet.
  • the forwarding node can avoid repeated forwarding of the same multicast message through the assertion mechanism.
  • the forwarding node 102 multicasts the Assert message, so that after receiving the Assert message, other forwarding nodes compare the parameters carried in the received Assert message with the parameters of the same type of the device. Through election rules, such as comparing priority or cost, select the winner's downstream outbound interface to determine a forwarding path.
  • election rules such as comparing priority or cost
  • this application provides a method, device and system for sending an Assert message.
  • This method can extend the PIM Assert message format, classify the content of multiple Assert messages according to the same source address or RP address, and aggregate the Assert messages with the same source address or multiple Assert messages with the same RP into An Assert message to improve the efficiency of message processing, especially in a scenario where a large number of Assert messages are triggered to send, the above method can reduce equipment processing overhead and shorten the time for multicast traffic repetition.
  • the methods for sending and acquiring PIM Assert messages, network nodes, and system solutions provided by the embodiments of the present invention are similar in principle. Therefore, the embodiments of the network nodes, methods, and systems can be referred to each other, and the same or similar parts will not be repeated.
  • an embodiment of the present invention provides a method for sending an Assert message, and the method includes:
  • the first network node determines multiple Assert records based on a multicast source address or Rendezvous Point (RP) address.
  • RP Rendezvous Point
  • the first network node determines multiple Assert records based on a multicast source address, and each Assert record in the multiple Assert records includes one multicast source address and one multicast group address, and Different Assert records in multiple Assert records contain different multicast group addresses.
  • the Assert record may be determined by the first network device according to the content of the received Assert message, or may be determined by the content of the Assert message generated by the first network device to be sent out.
  • the first network node determines a first Assert record set based on an RP address of a rendezvous point, the first Assert record set includes a plurality of Assert records, and each Assert record in the plurality of Assert records includes one A multicast source address and a multicast group address, and different Assert records in the multiple Assert records respectively contain the first multicast group address.
  • the first network node receives the multicast traffic, uses the multicast source address for the RPF check for the shortest path tree (Shortest Path Tree, SPT), and uses the RP address for the RPF check for the shared tree (RP Tree, RPT).
  • SPT Shortest Path Tree
  • RPT RP Tree
  • the first network node finds that there are other nodes in the same LAN that forward the same multicast traffic it triggers the first network node to multicast the Assert message, where the destination address of the Assert message is the permanent group address 224.0.0.13.
  • the trigger condition for the first network node to send the Assert message can also be receiving the Assert message sent by other network devices in the multicast network, etc. There are many trigger conditions for triggering the first network node to send the Assert message, which is not limited by this application. .
  • each Assert record includes a multicast entry or route of the first network node, the multicast entry includes a multicast source address and a multicast group address, for example, each Assert record includes a multicast route (S,G) or (*,G), where * means that the multicast source address is 0.
  • each Assert record includes a multicast entry (S, G).
  • each Assert record includes a multicast routing table (S, G) or (*, G), where if there is an (S, G) entry in the RPT, the Assert record includes (S, G). If there is no (S, G) entry and there is a (*, G) entry, the Assert record includes the (*, G) entry.
  • the first network node determining a plurality of Assert records based on a multicast source address includes: the first network node determines a first Assert record set based on a multicast source address, and the first Assert record set includes The first Assert record and the second Assert record of the multicast source address.
  • the first network node determines a second Assert record set based on the RP address
  • the second Assert record set includes multiple Assert records
  • each Assert record in the second Assert record set includes one A multicast source address and a multicast group address
  • different Assert records in the multiple Assert records in the second Assert record set respectively contain a second multicast group address
  • the Assert message also includes the second multicast Group address, the first multicast group address and the second multicast group address are different.
  • S202 The first network node generates an Assert message.
  • the first network node generates an Assert message according to the multiple Assert records, where the Assert message includes one of the multicast source addresses and the multicast group addresses in the multiple Assert records.
  • the first network node may extract one of the multicast source addresses, and combine the multicast group addresses of the first Assert record and the second Assert record to generate an Assert message.
  • the first network node extracts the RP address, the multicast group address of the first Assert record set, and the second Assert record set, and combines the first Assert record set and the second Assert record set.
  • the multicast source address generates the Assert message.
  • this application provides a format for sending an Assert message.
  • the first network node extracts the same multicast source address (source address) that the first Assert record and the second Assert record have, and fills it in the table in Figure 3. Shown in the multicast group address (Group Address).
  • the first network device fills in the group address of the first Assert record in the multicast group address 1, and fills the group address of the second Assert record in the multicast group address 2.
  • the first network node classifies the multicast entries (S, G) located in the SPT based on the same multicast source address, and divides the entries into different Assert record sets according to the multicast source address.
  • An Assert record set includes two or more Assert records with the same multicast source address.
  • the first Assert record set includes multiple Assert records (S1, G1) and (S1, G2) with the same source address S1.
  • the first network node fills in S1 in the "multicast source address" part shown in FIG. 3, G1 in the "multicast group address 1" part, and G2 in the "multicast group address 2" part.
  • the first network node determines the first Assert record set according to the same RP address.
  • the first Assert record set includes the first Assert sub-record set and the second Assert sub-record set with the same multicast group address.
  • the first Assert The sub-record set includes a third Assert record and a fourth Assert record with the same multicast group address
  • the second Assert sub-record set includes a fifth Assert record and a sixth Assert record with the same multicast group address.
  • this application provides another format for sending an Assert message.
  • the first network node extracts the same RP address of the first Assert sub-record set and the second Assert sub-record set and fills it in Figure 4 shows the "RP Address" part.
  • the first network device fills the same multicast group address of the first Assert sub-record set in the multicast group address 1 part, and fills the same multicast group address of the second Assert sub-record set in the multicast group address 2 parts.
  • the "multicast group address" can be the same multicast group address extracted from multiple Assert records.
  • the first Assert sub-record set includes a third Assert record and a fourth Assert record that have the same multicast group address.
  • the second Assert sub-record set includes a fifth Assert record and a sixth Assert record that have the same multicast group address.
  • the network node can extract the same multicast group address that the third Assert record and the fourth Assert record have and fill in the "Multicast group address" part shown in Figure 5, and add the multicast source address of the third Assert record Fill in the "Multicast source address 1" part, and fill in the "Multicast source address 2" part with the multicast source address recorded in the fourth Assert.
  • the third record, the fourth record, the fifth record, and the sixth record may be (S, G) or (*, G).
  • the first network node classifies the routing table entries in the RPT based on the same RP address, and divides the entries into different Assert record sets according to the RP address.
  • Each Assert record set includes two or more of the same RP addresses.
  • the Assert sub-record set of the RP address, each Assert sub-record set includes multiple Assert records, and the multiple Assert records have the same multicast group address.
  • the method before the first network point sends the Asser message, the method further includes: the first network node receives a PIM Hello message sent by other network nodes in the multicast network, and the Hello message carries the first identifier, The first identifier is used to negotiate a message format that supports aggregating the multiple Assert records into one Assert message.
  • each interface of the network node that is enabled with the PIM protocol will send a Hello message.
  • Hello messages can be used to discover PIM neighbors, coordinate various PIM protocol message parameters, and maintain neighbor relationships.
  • the destination address of the multicast packet of the Hello packet is 224.0.0.13 (representing all PIM network nodes in the same network segment).
  • the Hello message includes an identifier for negotiating to support aggregated Assert messages.
  • this application provides a Hello message carrying the identifier, where the "Option type" can be used to mark The Assert message is a message that aggregates multiple Assert records.
  • the "packaging-type” can be used to identify a specific method of packaging Assert records. Different packaging methods are identified by different values.
  • the Assert message may also carry the second and third identifiers.
  • the second identifier is used to indicate the number of multicast group addresses carried in the Assert message
  • the third identifier is used to indicate the number of multicast source addresses carried in the Assert message.
  • the identifier N in the number of multicast group addresses (N) in the Assert message indicates that the number of multicast group addresses carried in the Assert message is N, and may also indicate the number of aggregated Assert records.
  • the identifier O in the number of multicast group addresses (O) in the Assert message indicates that the number of multicast group addresses carried in the Assert message is zero.
  • the identifier P in the number of multicast source addresses (P) in the Assert message indicates that the number of multicast group addresses carried in the Assert message is P.
  • the Assert message further includes parameter information, and the parameter information may include the cost of the unicast route to the multicast source and the priority of the unicast routing protocol to the multicast source.
  • S203 The first network node multicasts the Assert message.
  • the first network node multicasts the aggregated Assert message to other network nodes in the multicast network.
  • the format of the Assert message may be the format shown in FIG. 3 or FIG. 4.
  • the Assert message may carry two or more different Assert record sets, such as a first Assert record set and a second Assert record set.
  • the first Assert record set may have the same first multicast source address
  • the second Assert record set may have the same second multicast source address, where the first multicast source address and the second multicast source address are different.
  • the Assert message carries two or more different Assert record sets, such as a first Assert record set and a second Assert record set.
  • the first Assert record set may have the same first RP address
  • the second Assert record set may have the same second RP address, where the first RP address and the second RP address are different.
  • S204 The second network node receives the Assert message sent by the first network node.
  • the second network node receives the Assert message, and the Assert message may include one multicast source address and multiple corresponding multicast group addresses.
  • the Assert message may further include an RP address and a first Assert record set, where the first Assert record set includes the first multicast group address and multiple multicast source addresses.
  • S205 The second network node obtains multiple Assert records by parsing the Assert message.
  • the first network node parses the Assert message to obtain multiple Assert records, and each Assert record in the multiple Assert records includes the multicast source address and the multiple multicast group addresses.
  • the multicast group address in the multiple Assert records is different from each other.
  • the first network node may obtain the multiple Assert records by combining the multicast source address and the multiple multicast group addresses carried in the Assert message.
  • the first network node parses the first Assert record set to obtain multiple Assert records.
  • Each Assert record in the multiple Assert records includes a multicast source address and a multicast group address. Different Assert records in each Assert record respectively contain the first multicast group address.
  • the first network node parses the second Assert record set to obtain multiple Assert records, and different Assert records in the second Assert record set respectively contain the second multicast group address, the first multicast group address and The second multicast group address is different.
  • the first network node parses the second Assert record set to obtain multiple Assert records.
  • Different Assert records in the second Assert record set respectively contain a second multicast group address, the first multicast group address and the second group The broadcast group address is different.
  • the second network node receives the Assert message as shown in FIG. 3, and the second network node separates the "multicast source address” part from “multicast group address 1" and "multicast group address 2". Go to the "multicast group address N" to combine to obtain multiple Assert records (multicast source address, multicast group address 1), (multicast source address, multicast group address 2) and other multicast entries.
  • the second network node determines that the Assert message carries the first Assert record set, and the Assert record set includes one RP address and multiple multicast group addresses. As shown in Figure 4, the Assert message carries one "RP address" and multiple "Multicast group addresses”. Each "Multicast group address” corresponds to multiple source addresses as shown in Figure 5, for example, “Multicast source address 1". "And "Multicast source address 2" etc.
  • the second network node combines each multicast group address, such as multicast group address 1 and its corresponding source addresses such as "multicast source address 1" and “multicast source address 2" to obtain (multicast group address 1 , Multicast source address 1) and (multicast group address 1, multicast source address 1) and other multiple Assert records.
  • the second network node may also obtain the parameter information of the first network device from the Assert message, such as the cost of the unicast route to the multicast source and the unicast route to the multicast source by the first network. Parameters such as the priority of the routing protocol.
  • the second network node conducts an Assert election with the acquired information and the parameters carried by itself.
  • the specific election rule may be that, for example, the unicast routing protocol that reaches the multicast source has a higher priority and wins. If the priorities are the same, the unicast route to the multicast source with the smaller cost wins. If both parameters are the same, the one with the largest interface IP address cost wins.
  • Specific rules can be set as needed, and there are no restrictions on election rules here.
  • upstream network nodes 701 and 702 connect downstream receivers 5-6 through a shared network, and receivers 5-6 send Internet multicast
  • the management protocol Internet Group Management Protocol, IGMP
  • multicast listener discovery protocol multicast listener discovery, MLD
  • report messages are added to the network nodes 701 and 702.
  • the network node 703 is a layer 2 switching device.
  • the network node 703 It can also be a Layer 2 switching device in a Layer 2 Ethernet network.
  • DR elections occur between network nodes 701 and 702.
  • network node 701 is elected DR.
  • the network node 702 forwards the multicast traffic.
  • the network node 701 starts to forward the multicast traffic, and the network node 702 has not stopped forwarding the multicast traffic.
  • An Assert campaign may also occur between the network node 701 and the network node 702, which triggers the network node 701 to send an Assert message to the network node 702, and the network node 702 sends an Assert message to the network node 701.
  • the network node needs to send and receive a large number of Assert messages.
  • the network node that sends the Assert message can use the method steps shown in Figure 2 to send aggregated Assert messages.
  • the network node 701 is the first network node in the multicast network in FIG. 2, and the network node 702 is the second network node in FIG. 2; or the network node 702 is the first network node in the multicast network in FIG. 2,
  • the network node 701 is the second network node in FIG. 2 and performs related operations.
  • FIG. 2 For a specific method of sending an Assert message and obtaining an Assert message, reference may be made to the embodiment shown in FIG. 2, which will not be repeated here.
  • the above method by extending the PIM Assert message, multiple Assert messages are classified according to the group address with the same source address or the group address with the same RP address, and the same type of Assert messages are aggregated into one Assert message to improve message processing Especially in a scenario where a large number of Assert messages are triggered to send, the above method can reduce equipment processing overhead and improve message processing efficiency.
  • FIG. 8 shows a possible structure diagram of a network node that sends an Assert message involved in the foregoing embodiment, for example, a first network node.
  • the first network node 800 can implement the first network node in the embodiment of FIG. 2 Function.
  • the first network node 800 includes: a determining unit 801, a generating unit 802, and a sending unit 803. These units can perform the corresponding functions of the first network node in the foregoing method embodiments.
  • the determining unit 801 is used to support the first network node 800 to perform the process S201 in FIG. 2; the generating unit 802 is used to support the first network node 800 to perform the process S202 in FIG.
  • the node 800 executes the process S203 in FIG. 2.
  • the determining unit 801 is configured to perform the determination of various information performed by the first network node in the foregoing method embodiment;
  • the determining unit 801 is configured to determine multiple Assert records based on a multicast source address or Rendezvous Point (RP) address;
  • the generating unit 802 is configured to generate an Assert message;
  • the sending unit 803 is configured to group Broadcast and send the Assert message.
  • RP Rendezvous Point
  • the first network device 900 includes a processor 901 and a transceiver 902, and may also include a memory 903 and a bus 904.
  • the processor 901, the transceiver 902, and the memory 903 are connected to each other through a bus 904;
  • the bus 904 may be a peripheral component interconnection standard (peripheral component interconnect, PCI for short) bus or an extended industry standard architecture (EISA for short) )Bus etc.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in FIG.
  • the first network device 900 can implement the function of the first network device in the embodiment shown in FIG. 2.
  • the processor 901 and the transceiver 902 can perform corresponding functions of the first network device in the foregoing method example.
  • the transceiver 902 is used to support the first network device 900 to perform the process S203 in FIG. 2 and/or other processes performed by the first network device in the technology described herein.
  • the processor 901 is configured to support the first network device 900 to perform the processes S201 and S202 in FIG. 2 and/or other processes performed by the first network device in the technology described herein.
  • the memory 903 is used to store the program code and data of the first network device 900.
  • the first network device 900 may be a router or a switch or a network device with a forwarding function, and the network device 900 can implement the function of the first network device in the foregoing method embodiment.
  • FIG. 10 shows a schematic structural diagram of a network node that obtains an Assert message involved in the foregoing embodiment, for example, a possible schematic structural diagram of a second network node.
  • the second network node 1000 can implement the first network node in the embodiment of FIG. 2 2.
  • the receiving unit 1001 is configured to support the second network node 1000 to perform the process S204 in FIG. 2; the obtaining unit 1002 is configured to support the second network node 1000 to perform the process S205 in FIG. 2.
  • the receiving unit 1001 is configured to perform the reception of various information performed by the first network node in the foregoing method embodiment; the obtaining unit 1002 is configured to perform various information acquisition performed by the second network node in the foregoing method embodiment.
  • the receiving unit 1001 is configured to receive Assert messages sent by other network nodes in the multicast network; the acquiring unit 1002 is configured to obtain multiple Assert records by parsing the Assert message.
  • the specific execution process please refer to the detailed description of the corresponding steps in the embodiment shown in FIG. 2, which will not be repeated here.
  • the second network device 1100 includes a processor 1101 and a transceiver 1102, and may also include a memory 1103 and a bus 1104.
  • the processor 1101, the transceiver 1102, and the memory 1103 are connected to each other through a bus 1104;
  • the bus 1104 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) )Bus etc.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used to represent in FIG. 11, but it does not mean that there is only one bus or one type of bus.
  • the second network device 1100 can implement the function of the second network device in the embodiment shown in FIG. 2.
  • the processor 1101 and the transceiver 1102 may perform corresponding functions of the second network device in the foregoing method example.
  • the transceiver 1102 is used to support the second network device 1100 to perform the process S204 in FIG. 2 and/or other processes performed by the first network device in the technology described herein.
  • the processor 1101 is configured to support the second network device 1100 to perform the process S205 in FIG. 2 and/or other processes performed by the second network device in the technology described herein.
  • the memory 1103 is used to store the program code and data of the second network device 1100. For the specific execution process, please refer to the detailed description of the corresponding steps in the embodiment shown in FIG. 2, which will not be repeated here.
  • the second network device 1100 may be a router or a switch or a network device with a forwarding function, and the network device 1100 can implement the function of the first network device in the foregoing method embodiment.
  • the system 1200 is used to implement the method for sending and obtaining Assert messages in the foregoing method embodiments.
  • the system 1200 includes a first network node 1201 and a second network node 1202.
  • the first network node 1201 and the second network node 1202 can respectively implement the functions of the first network node and the second network node in the embodiment shown in FIG. 2.
  • the first network node 1201 performs the processes S201 to S203 in FIG. 2 and/or other processes performed by the first network device in the technology described herein.
  • the second network node 1202 performs the processes S204 and S203 in FIG.
  • the first network node 1201 determines multiple Assert records based on a multicast source address or RP address, generates an Assert message, and multicasts the Assert message.
  • the second network node 1202 is configured to receive the Assert message sent by the first network node 1201, and obtain multiple Assert records by parsing the Assert message.
  • the system 1200 further includes a third network node.
  • the first network node may send the generated Assert message to the third network node.
  • the embodiment of the present invention also provides a storage medium for storing the software instructions used in the foregoing embodiment, which includes a program for executing the method shown in the foregoing embodiment, and when it is executed on a computer or device, it causes The computer or device shown executes the methods in the foregoing method embodiments.
  • the "first” in the first network device mentioned in the embodiment of the present invention is only used for name identification, and does not represent the first in order. This rule also applies to "second” and "third”.
  • any of the device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physically separate
  • the physical unit can be located in one place or distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.
  • the steps of the method or algorithm described in the disclosure of the embodiment of the present invention may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read only memory (ROM), erasable programmable read-only memory (erasable programmable ROM (EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory (EPROM, EEPROM), hard disk, mobile hard disk, optical disk, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in the core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • the functions described in the present invention can be implemented by hardware, software, firmware or any combination thereof.
  • these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Abstract

本申请提供了一种发送和获取Assert消息的方法和设备，用于以提升处理报文的效率，减轻网络设备开销。该方法包括网络节点基于一个组播源地址确定多个Assert记录。该多个Assert记录中的每个Assert记录分别包括一个组播源地址和一个组播组地址，其中，该多个Assert记录具备相同的组播源地址，该多个Assert记录中不同Assert记录包含的组播组地址互不相同。该网络节点根据该多个Assert记录生成一个Assert消息，其中该Assert消息包括一个该组播源地址和该多个Assert记录中的组播组地址。网络节点组播发送所述Assert消息。

Description

一种发送和获取断言报文的方法和网络节点
本申请要求于2019年02月21日提交中国国家知识产权局、申请号为201910128323.1、申请名称为“一种发送和获取断言报文的方法和网络节点”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种发送断言(Assert)报文的方法和设备。
背景技术
组播报文从组播源到达接收者(组播组成员)，需要通过组播网络来实现组播报文的复制和转发。为了构建组播网络，需要配置组播协议，例如协议无关组播(Protocol Independent Multicast，PIM)协议是目前应用最为广泛的域内组播协议。通过PIM协议构建的组播分发树，可以用来指导组播报文转发。PIM协议可实现按需创建组播路由、动态响应网络拓扑变化、按照路由表项执行转发等功能。
如图1所示，在设备101-105运行PIM协议。设备102将从设备101中获得的组播报文发送给下游设备104。设备103将从设备101中获得的同一组播报文发送给其下游设备105。而在上述转发组播报文的过程中，由于设备106是共享网路中的一个二层交换设备，例如处于共享局域网(local area network,LAN)中，设备106会将设备102发送给下游设备104的组播报文透传给与其相连的其他设备103-105，这样转发该组播报文的设备103还会从其出接口接收到该组播报文，使设备103发现同一LAN中还有其他设备转发同一组播报文，这将触发设备103组播发送断言(Assert)报文。设备102接收从设备103发送的Assert消息后，通过Assert选举规则选出获胜者来转发组播报文，保证同一LAN中传输一份组播报文。
然而，随着组播业务的广泛部署，组播表项数量成倍增加，组播网络的设备很可能出现短时大量发送Assert消息的情况，增大网络开销，这会对共享网络的设备造成较大的冲击，还可能因不能及时处理而导致Assert消息被丢弃，影响组播报文的正常转发。
发明内容
本申请实施例提供了一种发送和获取Assert消息的方法和设备，用于以提升处理报文的效率，减轻网络设备开销。
第一方面，本申请提供了一种发送Assert消息的方法，该方法包括网络节点基于一个组播源地址确定多个Assert记录。该多个Assert记录中的每个Assert记录分别包括一个组播源地址和一个组播组地址，其中，该多个Assert记录具备相同的组播源地 址，该多个Assert记录中不同Assert记录包含的组播组地址互不相同。该网络节点根据该多个Assert记录生成一个Assert消息，其中该Assert消息包括一个该组播源地址和该多个Assert记录中的组播组地址。网络节点组播发送所述Assert消息。
采用上述方法，网络节点根据多个Assert记录生成一个Assert消息，并将该Assert消息组播发送给其他网络节点，可以提升发送Assert消息的效率，尤其是在大量触发发送Assert消息的场景下，上述方法可以减轻设备处理开销，以缩短组播流量重复发送的时间。
在一种可能的设计中，该网络节点基于一个组播源地址确定多个Assert记录包括：该网络节点基于一个组播源地址确定第一Assert记录集，所述第一Assert记录集包括具备相同的组播源地址的第一Assert记录和第二Assert记录。
上述方法，基于同一组播源地址确定多个Assert记录，并根据该多个Assert记录生成一个Assert消息，进一步提升了发送Assert消息的效率。
在一种可能的设计中，该网络节点根据所述多个Assert记录生成一个Assert消息包括：所述网络节点提取一个该组播源地址，并组合第一Assert记录和第二Assert记录的组播组地址生成一个Assert消息。
采用上述方法，网络节点可以提取出多个Assert记录中相同的组播源地址，提高Assert消息的利用率，以及提高发送Assert消息的效率。
在一种可能的设计中，在该网络节点发送Asser报文之前，该方法还包括该网络节点接收组播网中其他网络节点发送的Hello报文，其中，该Hello报文携带第一标识，该第一标识用于指示所述组播网中其他网络节点支持接收所述Assert消息的功能。
采用上述方法，网络节点可以通过Hello报文中携带的标识确定发送该Hello报文的设备是否具备处理该Assert消息的功能。
在一种可能的设计中，所述Assert消息携带组播组地址的数目。
采用上述方法，网络节点可以将Assert消息所包含的组播组地址的数目携带在该Assert消息中。
第二方面，本申请提供了又一种发送Assert报文的方法，该方法包括网络节点基于一个汇聚点RP地址确定第一Assert记录集。该第一Assert记录集包括多个Assert记录，其中，每个Assert记录分别包括一个组播源地址和一个组播组地址。多个Assert记录中不同的Assert记录分别包含第一组播组地址。该网络节点生成一个Assert消息，其中，该Assert消息包括一个所述RP地址、所述第一组播组地址和多组播源地址。网络节点组播发送该Assert消息。
采用上述方法，网络节点根据RP地址将多个Assert记录生成一个Assert消息，并将该Assert消息组播发送给其他网络节点，可以提升发送Assert消息的效率，尤其是在大量触发发送Assert消息的场景下，上述方法可以减轻设备处理开销，以缩短组播流量重复发送的时间。
在一种可能的设计中，该方法还包括：该网络节点基于所述RP地址确定第二Assert记录集，其中，该第二Assert记录集包括多个Assert记录。第二Assert记录集合中的每个Assert记录分别包括一个组播源地址和一个组播组地址。第二Assert记录集合中的多个Assert记录中不同的Assert记录分别包含第二组播组地址，该Assert消息还包括所述第二 组播组地址，第一组播组地址和第二组播组地址不同。
采用上述方法，使得Assert消息包括不同的多个组播组地址，提高Assert消息的利用率，提升发送Assert消息的效率。
在一种可能的设计中，该网络节点生成一个Assert消息包括：该网络节点提取所述RP地址、第一Assert记录集和第二Assert记录集的所述组播组地址，并组合第一Assert记录集和第二Assert记录集的组播源地址生成所述Assert消息。
采用上述方法，网络节点可以提取出具备相同的RP地址，提高Assert消息的利用率和发送Assert消息的效率。
在一种可能的设计中，在所述网络节点发送Asser报文之前，该方法还包括：该网络节点接收组播网中其他网络节点发送的Hello报文，其中，Hello报文携带第一标识，第一标识用于指示所述组播网中其他网络节点支持接收该Assert消息的功能。
在一种可能的设计中，该Assert消息携带组播组地址和组播源地址的数目。
第三方面，一种组播网络中获取Assert消息的方法，该方法包括该网络节点接收Assert消息，其中，该Assert消息包括一个组播源地址和多个组播组地址。该网络节点通过解析所述Assert消息获得多个Assert记录，该多个Assert记录中的每个Assert记录分别包括所述组播源地址和所述多个组播组地址中的一个组播组地址，该多个Assert记录中的组播组地址互不相同。
在一种可能的设计中，该网络节点解析所述Assert消息获得多个Assert记录包括：该网络节点将该Assert消息携带的所述组播源地址和所述多个组播组地址进行组合，获取所述多个Assert记录。
第四方面，一种组播网络中获取Assert消息的方法，该方法包括：该网络节点接收Assert消息，该Assert消息包括汇聚点RP地址和第一Assert记录集，所述第一Assert记录集包括第一组播组地址和多个组播源地址。该网络节点通过解析第一Assert记录集获取多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所述多个Assert记录中不同的Assert记录分别包含第一组播组地址。
在一种可能的设计中，该Assert消息还包括第二Assert记录集。该方法还包括：该网络节点解析第二Assert记录集获得多个Assert记录，第二Assert记录集中不同的Assert记录分别包含第二组播组地址。第一组播组地址和第二组播组地址不同。
第五方面，本申请实施例提供了一种发送Assert消息的网络节点，执行第一方面或第一方面任意一种可能的实现方式中的方法。具体的，该网络节点包括用于执行第一方面或第一方面的任意一种可能的实现方式中的方法的单元。
第六方面，本申请实施例提供了又一种发送Assert消息的网络节点，执行第二方面或第二方面任意一种可能的实现方式中的方法。具体的，该网络节点包括用于执行第二方面或第二方面的任意一种可能的实现方式中的方法的单元。
第七方面，本申请实施例提供了一种获取Assert消息的网络节点，执行第三方面或第三方面任意一种可能的实现方式中的方法。具体的，该网络节点包括用于执行第三方面或第三方面的任意一种可能的实现方式中的方法的单元。
第八方面，本申请实施例提供了一种获取Assert消息的网络节点，执行第四方面 或第四方面任意一种可能的实现方式中的方法。具体的，该网络节点包括用于执行第四方面或第四方面的任意一种可能的实现方式中的方法的单元。
第九方面，提供一种发送或获取Assert消息的网络设备，该设备包括处理器、收发器和存储器。上述第五方面、第六方面、第七方面以及第八方面的功能模块可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。例如，收发器，用于完成接收单元和发送单元的功能，处理器，用于完成确定、生成和获取单元的功能，存储器，用于处理器处理本申请实施例的方法的程序指令。处理器、收发器和存储器通过总线连接并完成相互间的通信。
第十方面，提供了一种发送和获取Assert消息的系统，该系统包含前述第一方面和第二方面提供的网络设备，称为第一网络设备，以及第三方面、第四方面提供的网络设备，称为第二网络设备。第一网络设备用于基于一个组播源地址或者RP地址确定多条Assert记录；生成一个Assert消息；组播发送该Assert消息。第二网络设备用于接收第一网络节点发送的Assert消息和通过解析该Assert消息获得多个Assert记录。
第十一方面，本申请提供了一种计算机可读存储介质，用于储存为上述网络节点所用的计算机软件指令，其包括用于执行上述方面所设计的程序。
附图说明
图1为本申请实施例提供的一种发送组播报文的场景示意图。
图2为本申请实施例提供的一种发送Assert消息的方法流程示意图。
图3为本申请实施例提供的一种Assert消息的报文格式示意图。
图4为本申请实施例提供的又一种Assert消息的报文格式示意图。
图5为本申请实施例提供的又一种Assert消息的报文格式示意图。
图6为本申请实施例提供的PIM Hello报文的报文格式示意图。
图7为本申请实施例提供的转发Assert消息的场景示意图。
图8为本申请实施例提供的一种发送Assert消息第一网络设备结构示意图。
图9为本申请实施例提供的另一种发送Assert消息第一网络设备结构示意图。
图10为本申请实施例提供的一种获取Assert消息第二网络设备结构示意图。
图11为本申请实施例提供的另一种获取Assert消息第二网络设备结构示意图。
图12为本申请实施例提供的一种发送和获取Assert消息的系统结构示意图。
具体实施方式
下面结合附图，对本发明的实施例进行描述。
本发明实施例中的网络节点可以为路由器、交换机、或者为软件定义网络(Software-defined networking，SDN)中的转发器等网络设备。
如图1所示，提供了一种转发组播流量的应用场景示意图。该场景包括组播源、网络节点101-106和接收者(receiver)1-4。组播网络中的节点支持PIM协议和网路群组管理协议(Internet Group Management Protocol，IGMP)，接收者1-4可以通过IGMP加入组播组，网络节点101-106可以使用PIM协议构建组播分发树。组播树中的叶子节点104和105可以通过转发节点102接收组播报文，也可以通过转发节点103接收组播报文。叶子节点105将 接收到的组播报文转发给接收者1-2，叶子节点106将接收到的组播报文转发给接收者3-4。
在上述组播报文转发过程中，叶子节点104可以通过上游转发节点102加入组播组G1，叶子节点105可以通过转发节点103加入组播组G1。然而，在共享网络中，设备106可以为二层交换机，这样在转发节点102通过设备106向下游设备104发送的组播流量时，造成该组播流量通过设备106透传给转发节点103和叶子节点105，使得转发节点103出接口收到发下游发送的组播流量，导致组播流量转发。在这种情况下，转发节点102可以通过逆向路径转发(Reverse Path Forwarding,RPF)检查将从下游接口收到的该组播流量丢弃，并触发转发节点102发送断言(Assert)报文。该RPF检查用于实现组播报文转发的无环化，即RPF机制确保组播报文从正确的接口被收到，通过RPF检查的组播报文可以沿着组播树进行转发，如果数据包从错误的接口被收到，网络设备将丢弃该组播报文。
如上所述，转发节点可以通过断言机制来避免对相同组播报文的重复转发。如图1所示的场景中，转发节点102组播发送Assert消息，使得其它转发节点在接收到该Assert消息后，将接收到的Assert消息中携带的参数与该设备的同类型参数做比较，通过竞选规则，例如比较优先级或者度量值(cost)等，选出胜利者(winner)的下游出接口，以确定一条转发路径。关于PIM Assert消息定义可以参见互联网工程任务小组(internet engineering task force，IETF)公开的征求意见稿(Requirement For Comments,RFC)7761相关描述，本申请不再赘述。
然而，随着组播业务应用的广泛部署，组播网络中可能出现短时发送大量Assert消息的场景，这对共享网络中的网络节点造成较大的冲击，增加网络节点处理了PIM Assert消息的数量，有可能造成Assert消息被丢弃，导致延长网络中组播流量重复转发的时间。
为了解决上述技术问题，本申请提供了一种发送Assert消息的方法、设备和系统。该方法可以通过扩展PIM Assert消息格式，将多个Assert消息的内容根据相同的源地址或者RP地址进行分类，并将具有相同的源地址的Assert消息或者具有相同的RP的多个Assert消息聚合为一个Assert消息，以提升报文处理的效率，尤其是在大量触发发送Assert消息的场景下，上述方法可以减轻设备处理开销，缩短组播流量重复的时间。本发明实施例提供的发送和获取PIM Assert消息的方法、网络节点和系统解决问题的原理相似，因此，网络节点、方法和系统的实施例可以相互参见，相同或类似之处不再赘述。
结合图1所示的应用场景，参阅图2，本发明实施例提供了一种发送Assert消息的方法，该方法包括：
S201，第一网络节点基于一个组播源地址或者汇聚点(Rendezvous Point,RP)地址确定多条Assert记录。
在一个示例中，第一网络节点基于一个组播源地址确定多个Assert记录，所述多个Assert记录中的每个Assert记录包括一个所述组播源地址和一个组播组地址，所述多个Assert记录中不同Assert记录包含的组播组地址互不相同。该Assert记录可以是第一网络设备根据接收的Assert消息内容确定的，也可以是第一网络设备生成的将要向外发送的Assert消息的内容确定的。
在一个示例中，第一网络节点基于一个汇聚点RP地址确定第一Assert记录集，所述第一Assert记录集包括多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所述多个Assert记录中不同的Assert记录分别包含第一组播 组地址。
在一个示例中，第一网络节点接收组播流量，对于最短路径树(Shortest Path Tree,SPT)使用组播源地址进行RPF检查，对于共享树(RP Tree,RPT)使用RP地址进行RPF检查。当第一网络节点发现同一LAN中还存在其他节点转发同一个组播流量，则触发该第一网络节点组播发送Assert消息，其中该Assert消息的目的地址为永久组地址224.0.0.13。第一网络节点发送Assert消息的触发条件还可以是接收到组播网络中其他网路设备发送的Assert消息等，触发第一网络节点发送Assert消息的触发条件有很多，本申请对此并不限制。
在一个示例中，每个Assert记录包括第一网络节点的一条组播表项或路由，所述组播表项包括组播源地址和组播组地址，例如每个Assert记录包括一个组播路由(S,G)或(*,G)，其中*表示组播源地址为0。当该第一网络节点位于SPT中，每个Assert记录包括一个组播表项(S,G)。当该第一网络节点位于RPT，每个Assert记录包括一个组播路由表(S,G)或(*,G)，其中如果RPT中存在(S,G)表项，Assert记录包括(S,G)，如果没有(S,G)表项，存在(*,G)表项，则Assert记录包括(*,G)表项。
在一个示例中，第一网络节点基于一个组播源地址确定多个Assert记录包括：第一网络节点基于一个组播源地址确定第一Assert记录集，所述第一Assert记录集包括具备相同的组播源地址的第一Assert记录和第二Assert记录。
在一个示例中，第一网络节点基于所述RP地址确定第二Assert记录集，所述第二Assert记录集包括多个Assert记录，所述第二Assert记录集合中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所述第二Assert记录集合中的多个Assert记录中不同的Assert记录分别包含第二组播组地址，所述Assert消息还包括所述第二组播组地址，所述第一组播组地址和所述第二组播组地址不同。
S202，第一网络节点生成一个Assert消息。
在一个示例中，第一网络节点根据所述多个Assert记录生成一个Assert消息，所述Assert消息包括一个所述组播源地址和所述多个Assert记录中的组播组地址。第一网络节点可以提取一个所述组播源地址，并组合所述第一Assert记录和所述第二Assert记录的组播组地址生成一个Assert消息。
在一个示例中，第一网络节点提取所述RP地址、第一Assert记录集和第二Assert记录集的组播组地址，并组合所述第一Assert记录集和所述第二Assert记录集的组播源地址生成所述Assert消息。
如图3所示，为本申请提供一种发送Assert消息的格式，第一网络节点将第一Assert记录和第二Assert记录具备的同一组播源地址(source address)提取出来填写在图3所示的组播组地址(Group Address)中。第一网络设备将第一Assert记录的组地址填写在组播组地址1中，将第二Assert记录的组地址填写在组播组地址2中。
举例来说，第一网络节点将位于SPT中的组播表项(S,G)基于相同的组播源地址进行分类，并根据组播源地址将表项分为不同的Assert记录集，每个Assert记录集包括两个以上具备相同组播源地址的Assert记录。例如第一Assert记录集包括具备相同源地址S1的多个Assert记录(S1,G1)和(S1,G2)。第一网络节点将S1填写在图3所示的“组播源地址”部分，将G1填写在“组播组地址1”部分，将G2填写在“组播组地址2”部分。
在一个示例中，第一网络节点根据同一RP地址确定第一Assert记录集，第一Assert记录 集包括具备相同组播组地址的第一Assert子记录集和第二Assert子记录集，第一Assert子记录集包括具备相同组播组地址的第三Assert记录和第四Assert记录，所述第二Assert子记录集包括具备相同组播组地址的第五Assert记录和第六Assert记录。
举例来说，如图4所示，为本申请提供另一种发送Assert消息的格式，第一网络节点将第一Assert子记录集和第二Assert子记录集具备的同一RP地址提取出来填写在图4所示的“RP地址”部分。第一网络设备将第一Assert子记录集具备的相同的组播组组地址填写在组播组地址1部分，将第二Assert子记录集具备的相同的组播组地址填写在组播组地址2部分。
如图5所示，为本申请提供一种图4中“组播组地址”部分的格式。“组播组地址”可以是从多个Assert记录中提取的相同的组播组地址。例如，第一Assert子记录集包括具备相同组播组地址的第三Assert记录和第四Assert记录。第二Assert子记录集包括具备相同组播组地址的第五Assert记录和第六Assert记录。网络节点可以将第三Assert记录和第四Assert记录所具备的的相同的组播组地址提取出来填写在图5所示的“组播组地址”部分，将第三Assert记录的组播源地址填写在“组播源地址1”部分，将和第四Assert记录的组播源地址填写在“组播源地址2”部分。第三记录、第四记录、第五记录和第六记录可以是(S,G)或者(*,G)。
举例来说，第一网络节点将位于RPT中的路由表项基于相同的RP地址进行分类，并根据RP地址将表项分为不同的Assert记录集，每个Assert记录集包括两个以上具备相同RP地址的Assert子记录集，每个Assert子记录集包括多个Assert记录，该多个Assert记录具备相同的组播组地址。
在一个示例中，在第一网络点发送Asser报文之前，所述方法还包括：第一网络节点接收组播网中其他网络节点发送的PIM Hello报文，该Hello报文携带第一标识，所述第一标识用于协商支持将所述多条Assert记录聚合在一个Assert消息的报文格式。
在一个示例中，网络节点的每个使能了PIM协议的接口上，都会对外发送Hello报文。Hello报文可以用于发现PIM邻居、协调各项PIM协议报文参数、维持邻居关系。Hello报文的组播报文的目的地址是224.0.0.13(表示同一网段中所有PIM网络节点)。
在一个示例中，Hello报文包括用于协商支持聚合Assert消息的标识，如图5所示，为本申请提供一种携带该标识的Hello报文，其中，将“Option类型”可以用于标记该Assert消息是聚合多个Assert记录的报文，可以将“打包-类型”用于标识具体的打包Assert记录的方法，不同的打包方法，用不同的值标识。
在一个示例中，该Assert消息还可以携带第二和第三标识。第二标识用于表示所述Assert消息携带的组播组地址的数目，第三标识用于表示所述Assert消息携带的组播源地址的数目。如图3所示，Assert消息中的组播组地址数目(N)中的标识N表示Assert消息携带的组播组地址的数目为N，还可以表示聚合的Assert记录的数目。如图4所示，Assert消息中的组播组地址数目(O)中的标识O表示Assert消息携带的组播组地址的数目为O。如图5所示，Assert消息中的组播源地址数目(P)中的标识P表示Assert消息携带的组播组地址的数目为P。
在一个示例中，Assert消息还包括参数信息，该参数信息可以包括到达组播源的单播路由的度量值(cost)和到达组播源的单播路由协议的优先级等。
S203，第一网络节点组播发送该Assert消息。
在一个示例中，第一网络节点将经过聚合的Assert消息组播发送给组播网络中的其他网络节点。该Assert消息的格式可以是图3或者图4所示的格式。
在一个示例中，该Assert消息可以携带两个以上不同的Assert记录集，例如第一Assert记录集和第二Assert记录集。第一Assert记录集可以具有相同的第一组播源地址，第二Assert记录集可以具有相同的第二组播源地址，其中第一组播源地址和第二组播源地址不同。
在一个示例中，该Assert消息携带了两个以上不同的Assert记录集，例如第一Assert记录集和第二Assert记录集。第一Assert记录集可以具有相同的第一RP地址，第二Assert记录集可以具有相同的第二RP地址，其中第一RP地址和第二RP地址不同。
S204，第二网络节点接收第一网络节点发送的Assert消息。
在一个示例中，第二网络节点接收Assert消息，该Assert消息可以是包括一个组播源地址和多个对应的组播组地址。Assert消息还可以包括一个RP地址和第一Assert记录集，所述第一Assert记录集包括第一组播组地址和多个组播源地址。
S205，第二网络节点通过解析该Assert消息获得多个Assert记录。
在一个示例中，第一网络节点解析所述Assert消息获得多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括所述组播源地址和所述多个组播组地址中的一个组播组地址，所述多个Assert记录中的组播组地址互不相同。第一网络节点可以通过将所述Assert消息携带的所述组播源地址和所述多个组播组地址进行组合，获取所述多个Assert记录。
在一个示例中，第一网络节点解析第一Assert记录集获取多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所述多个Assert记录中不同的Assert记录分别包含第一组播组地址。
在一个示例中，第一网络节点解析第二Assert记录集获得多个Assert记录，所述第二Assert记录集中不同的Assert记录分别包含第二组播组地址，所述第一组播组地址和所述第二组播组地址不同。第一网络节点解析第二Assert记录集获得多个Assert记录，所述第二Assert记录集中不同的Assert记录分别包含第二组播组地址，所述第一组播组地址和所述第二组播组地址不同。
举例来说，第二网络节点接收到如图3所示的Assert消息，第二网络节点将“组播源地址”部分分别和“组播组地址1”、“组播组地址2”，一直到“组播组地址N”进行组合，获得多个Assert记录(组播源地址,组播组地址1)、(组播源地址,组播组地址2)等组播表项。
在一个示例中，第二网络节点确定Assert消息携带第一Assert记录集，该Assert记录集包括一个RP地址和多个组播组地址。如图4所示，Assert消息携带一个“RP地址”和多个“组播组地址”，每个“组播组地址”如图5所示对应多个源地址，例如“组播源地址1”和“组播源地址2”等。该第二网络节点将每个组播组地址,例如组播组地址1和与其对应的“组播源地址1”和“组播源地址2”等源地址进行组合获得(组播组地址1,组播源地址1)和(组播组地址1,组播源地址1)等多个Assert记录。
在一个示例中，第二网络节点还可以从Assert消息获得第一网络设备的参数信息，例如第一网络设到达组播源的单播路由的度量值(cost)和到达组播源的单播路由协议的优 先级等参数。第二网络节点将获取的上述信息与自身携带的参数进行Assert竞选，具体竞选规则例如可以是到达组播源的单播路由协议优先级较高者获胜。如果优先级相同，则到组播源的单播路由的开销较小者获胜。如果两个参数都相同，则接口IP地址开销最大者获胜。具体规则可以根据需要进行设置，此处对竞选规则不做限制。
上述方法还可以适用指定路由器(designated router，DR)竞选场景中，例如图7所示，在上游网络节点701和702通过共享网络连接下游接收者5-6，接收者5-6发送因特网组播管理协议(Internet Group Management Protocol,IGMP)或者组播监听者发现协议(multicast listener discovery,MLD)report报文加入网络节点701和702，其中网络节点703为二层交换设备，该场景中网络节点703还可以是二层以太网络中二层交换设备等。根据RFC7761的4.3章节描述网络节点701和702之间发生DR竞选，只有成为DR才能在该网络中向接收者4-6转发组播流量，例如网络节点701当选DR。当网络节点701发生故障后由网络节点702转发组播流量，而在网络节点701的恢复的过程中，网络节点701开始转发组播流量，而网络节点702还未停止转发组播流量，此时网络节点701和网络节点702之间也可能发生Assert竞选，触发网络节点701向网络节点702发送Assert消息，网络节点702向网络节点701发送Assert消息。当该场景中的组播转发节点超过2台时，网络节点需要发送和接收大量的Assert消息，此时发送Assert消息的网络节点可以采用上述图2所示的方法步骤发送经过聚合的Assert消息，以提高报文的发送效率，减小网络开销。例如，网络节点701为图2中组播网络中的第一网络节点，网络节点702为图2中的第二网络节点；或者网络节点702为图2中组播网络中的第一网络节点，网络节点701为图2中的第二网络节点并执行相关操作。具体的发送Assert消息和获取Assert消息的方式可以参考图2所示实施例，此处不在赘述。
采用上述方法，通过扩展PIM Assert消息，使得多个Assert消息根据源地址相同的组地址或者RP地址相同的组地址进行分类，并将同类型的Assert消息聚合为一个Assert消息，以提升报文处理的效率，尤其是在大量触发发送Assert消息的场景下，上述方法可以减轻设备处理开销，提高报文处理效率。
图8示出了上述实施例中所涉及的发送Assert消息的网络节点，例如第一网络节点的一种可能的结构示意图，该第一网络节点800可以实现图2实施例中的第一网络节点的功能。参阅图8，该第一网络节点800包括：确定单元801、生成单元802和发送单元803。这些单元可以执行上述方法实施例中第一网络节点的相应功能。确定单元801，用于支持第一网络节点800执行图2中的过程S201；生成单元802，用于支持第一网络节点800执行图2中的过程S202；发送单元803，用于支持第一网络节点800执行图2中的过程S203。例如，确定单元801，用于执行上述方法实施例中第一网络节点执行的各种信息的确定；生成单元802，用于执行上述方法实施例中第一网络节点执行的各种信息生成；发送单元803，用于执行上述方法实施例中第一网络节点执行的各种信息发送。举例来说，确定单元801，用于基于一个组播源地址或者汇聚点(Rendezvous Point,RP)地址确定多条Assert记录；生成单元802，用于生成一个Assert消息；发送单元803，用于组播发送该Assert消息。具体执行过程请参考上述图2所示实施例中相应步骤的详细描述，这里不再一一赘述。
参阅图9所示，提供一种发送Assert消息的网络节点的结构示意图，例如该第一网络设 备900包括：处理器901和收发器902，还可以包括存储器903以及总线904。其中，处理器901、收发器902以及存储器903通过总线904相互连接；总线904可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。该第一网络设备900可以实现图2所示的实施例中的第一网络设备的功能。处理器901和收发器902可以执行上述方法示例中第一网络设备的相应功能。收发器902用于支持第一网络设备900执行图2中的过程S203，和/或本文所描述的技术中第一网络设备执行的其它过程。处理器901用于支持第一网络设备900执行图2中的过程S201和S202，和/或本文所描述的技术中第一网络设备执行的其它过程。存储器903，用于存储第一网络设备900的程序代码和数据。具体执行过程请参考上述图2所示实施例中相应步骤的详细描述，这里不再一一赘述。第一网络设备900可以为路由器或交换器或有转发功能的网络设备，网络设备900能够实现前述方法实施例中的第一网络设备的功能。
图10示出了上述实施例中所涉及的获取Assert消息的网络节点的结构示意图，例如第二网络节点的一种可能的结构示意图，该第二网络节点1000可以实现图2实施例中的第二网络节点的功能。参阅图10，该第二网络节点1000包括：接收单元1001和获取单元1002。这些单元可以执行上述方法实施例中第二网络节点的相应功能。接收单元1001，用于支持第二网络节点1000执行图2中的过程S204；获取单元1002，用于支持第二网络节点1000执行图2中的过程S205。例如，接收单元1001，用于执行上述方法实施例中第一网络节点执行的各种信息的接收；获取单元1002，用于执行上述方法实施例中第二网络节点执行的各种信息获取。举例来说，接收单元1001，用于接收组播网络中其他网络节点发送的Assert消息；获取单元1002，用于通过解析该Assert消息获得多个Assert记录。具体执行过程请参考上述图2所示实施例中相应步骤的详细描述，这里不再一一赘述。
参阅图11所示，提供一种获取Assert消息的网络节点的结构示意图，例如该第二网络设备1100包括：处理器1101和收发器1102，还可以包括存储器1103以及总线1104。其中，处理器1101、收发器1102以及存储器1103通过总线1104相互连接；总线1104可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。该第二网络设备1100可以实现图2所示的实施例中的第二网络设备的功能。处理器1101和收发器1102可以执行上述方法示例中第二网络设备的相应功能。收发器1102用于支持第二网络设备1100执行图2中的过程S204，和/或本文所描述的技术中第一网络设备执行的其它过程。处理器1101用于支持第二网络设备1100执行图2中的过程S205，和/或本文所描述的技术中第二网络设备执行的其它过程。存储器1103，用于存储第二网络设备1100的程序代码和数据。具体执行过程请参考上述图2所示实施例中相应步骤的详细描述，这里不再一一赘述。第二网络设备1100可以为路由器或交换器或有转发功能的网络设备，网络设备1100能够实现前述方法实施例中的第一网络设备的功能。
参阅图12所示，提供一种发送和获取Assert消息的系统1200的结构示意图，该系统1200用于实现前述方法实施例中的发送和获取Assert报文的方法。该系统1200包括第一网络节 点1201和第二网络节点1202。该第一网络节点1201和第二网络节点1202可以分别实现图2所示的实施例中的第一网络节点和第二网络节点的功能。例如，第一网络节点1201执行图2中的过程S201至S203，和/或用于本文所描述的技术中第一网络设备执行的其它过程。第二网络节点1202执行图2中的过程S204和S203，和/或用于本文所描述的技术中第一网络设备执行的其它过程。第一网络节点1201基于一个组播源地址或者RP地址确定多条Assert记录，生成一个Assert消息，并组播发送该Assert消息。第二网络节点1202，用于接收第一网络节点1201发送的Assert消息，通过解析该Assert消息获得多个Assert记录。
在一个示例中，该系统1200还包括第三网络节点。第一网络节点可以将生成的Assert消息发送给第三网络节点。
本发明实施例还提供了一种存储介质，用于储存前述实施例中所用的软件指令，其包括用于执行前述实施例所示的方法的程序，当其在计算机或设备上执行时，使得所示计算机或设备执行前述方法实施例中的方法。
本发明实施例中提到的第一网络设备中的“第一”只是用来做名字标识，并不代表顺序上的第一。该规则同样适用于“第二”和“第三”。
需说明的是，以上描述的任意装置实施例都仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外，本发明提供的第一网络设备或控制器实施例附图中，模块之间的连接关系表示它们之间具有通信连接，具体可以实现为一条或多条通信总线或信号线。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read only memory，ROM)、可擦除可编程只读存储器(erasable programmable ROM，EPROM)、电可擦可编程只读存储器(electrically EPROM，EEPROM)、硬盘、移动硬盘、光盘或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (28)

  1. 一种组播网络中发送断言Assert消息的方法，其特征在于，所述方法包括：
    网络节点基于一个组播源地址确定多个Assert记录，所述多个Assert记录中的每个Assert记录包括一个所述组播源地址和一个组播组地址，所述多个Assert记录中不同Assert记录包含的组播组地址互不相同；
    所述网络节点根据所述多个Assert记录生成一个Assert消息，所述Assert消息包括一个所述组播源地址和所述多个Assert记录中的组播组地址；
    网络节点组播发送所述Assert消息。
  2. 根据权利要求1所述的方法，其特征在于，所述网络节点基于一个组播源地址确定多个Assert记录包括：
    所述网络节点基于一个组播源地址确定第一Assert记录集，所述第一Assert记录集包括具备相同的组播源地址的第一Assert记录和第二Assert记录。
  3. 根据权利要求2所述的方法，其特征在于，所述网络节点根据所述多个Assert记录生成一个Assert消息包括：
    所述网络节点提取一个所述组播源地址，并组合所述第一Assert记录和所述第二Assert记录的组播组地址生成一个Assert消息。
  4. 根据权利要求1-3任一所述的方法，其特征在于，在所述网络节点发送Asser报文之前，所述方法还包括：
    所述网络节点接收组播网中其他网络节点发送的Hello报文，所述Hello报文携带第一标识，所述第一标识用于指示所述组播网中其他网络节点支持接收所述Assert消息的功能。
  5. 根据权利要求1-4任一所述的方法，其特征在于，所述Assert消息携带组播组地址的数目。
  6. 一种组播网络中发送断言Assert消息的方法，其特征在于，所述方法包括：
    网络节点基于一个汇聚点RP地址确定第一Assert记录集，所述第一Assert记录集包括多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所述多个Assert记录中不同的Assert记录分别包含第一组播组地址；
    所述网络节点生成一个Assert消息，所述Assert消息包括一个所述RP地址、所述第一组播组地址和多组播源地址；
    网络节点组播发送所述Assert消息。
  7. 根据权利要求6所述的方法，其特征在于，还包括：
    所述网络节点基于所述RP地址确定第二Assert记录集，所述第二Assert记录集包括多个Assert记录，所述第二Assert记录集合中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所述第二Assert记录集合中的多个Assert记录中不同的Assert记录分 别包含第二组播组地址，所述Assert消息还包括所述第二组播组地址，所述第一组播组地址和所述第二组播组地址不同。
  8. 根据权利要求7所述的方法，其特征在于，所述网络节点生成一个Assert消息包括：
    所述网络节点提取所述RP地址、所述第一Assert记录集和所述第二Assert记录集的所述组播组地址，并组合所述第一Assert记录集和所述第二Assert记录集的组播源地址生成所述Assert消息。
  9. 根据权利要求6-8任一所述的方法，其特征在于，在所述网络点发送Asser报文之前，所述方法还包括：
    所述网络节点接收组播网中其他网络节点发送的Hello报文，所述Hello报文携带第一标识，所述第一标识用于指示所述组播网中其他网络节点支持接收所述Assert消息的功能。
  10. 根据权利要求6-9任一所述的方法，其特征在于，所述Assert消息携带组播组地址和组播源地址的数目。
  11. 一种组播网络中获取Assert消息的方法，其特征在于，该方法包括：
    网络节点接收Assert消息，所述Assert消息包括一个组播源地址和多个组播组地址；
    所述网络节点解析所述Assert消息获得多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括所述组播源地址和所述多个组播组地址中的一个组播组地址，所述多个Assert记录中的组播组地址互不相同。
  12. 根据权利要求11所述的方法，其特征在于，所述网络节点解析所述Assert消息获得多个Assert记录包括：
    所述网络节点将所述Assert消息携带的所述组播源地址和所述多个组播组地址进行组合，获取所述多个Assert记录。
  13. 一种组播网络中获取Assert消息的方法，其特征在于，所述方法包括：
    网络节点接收Assert消息，所述Assert消息包括汇聚点RP地址和第一Assert记录集，所述第一Assert记录集包括第一组播组地址和多个组播源地址；
    所述网络节点解析第一Assert记录集获取多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所述多个Assert记录中不同的Assert记录分别包含第一组播组地址。
  14. 根据权利要求13所述的方法，其特征在于，所述Assert消息还包括第二Assert记录集，所述方法还包括：
    所述网络节点解析第二Assert记录集获得多个Assert记录，所述第二Assert记录集中不同的Assert记录分别包含第二组播组地址，所述第一组播组地址和所述第二组播组地址不同。
  15. 一种发送断言Assert消息的设备，其特征在于，所述设备包括：
    确定单元，用于基于一个组播源地址确定多个Assert记录，所述多个Assert记录中的每个Assert记录包括一个所述组播源地址和一个组播组地址，所述多个Assert记录中不同Assert记录包含的组播组地址互不相同；
    生成单元，用于根据所述多个Assert记录生成一个Assert消息，所述Assert消息包括一个所述组播源地址和所述多个Assert记录中的组播组地址；
    发送单元，用于组播发送所述Assert消息。
  16. 根据权利要求15所述的设备，其特征在于，所述确定单元，具体用于基于一个组播源地址确定第一Assert记录集，所述第一Assert记录集包括具备相同的组播源地址的第一Assert记录和第二Assert记录。
  17. 根据权利要求16所述的设备，其特征在于，所述生成单元，具体用于提取一个所述组播源地址，并组合所述第一Assert记录和所述第二Assert记录的组播组地址生成一个Assert消息。
  18. 根据权利要求15-17任一所述的设备，其特征在于，该设备还包括接收单元，所述接收单元用于接收组播网中其他网络节点发送的Hello报文，所述Hello报文携带第一标识，所述第一标识用于指示所述组播网中其他网络节点支持接收所述Assert消息的功能。
  19. 根据权利要求15-18任一所述的设备，其特征在于，所述Assert消息携带组播组地址的数目。
  20. 一种组播网络中发送断言Assert消息的设备，其特征在于，所述设备包括：
    确定单元，用于基于一个汇聚点RP地址确定第一Assert记录集，所述第一Assert记录集包括多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所述多个Assert记录中不同的Assert记录分别包含第一组播组地址；
    生成单元，用于生成一个Assert消息，所述Assert消息包括一个所述RP地址、所述第一组播组地址和多组播源地址；
    发送单元，用于组播发送所述Assert消息。
  21. 根据权利要求20所述的设备，其特征在于，所述确定单元还用于基于所述RP地址确定第二Assert记录集，所述第二Assert记录集包括多个Assert记录，所述第二Assert记录集合中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所 述第二Assert记录集合中的多个Assert记录中不同的Assert记录分别包含第二组播组地址，所述Assert消息还包括所述第二组播组地址，所述第一组播组地址和所述第二组播组地址不同。
  22. 根据权利要求21所述的设备，其特征在于，所述生成单元，具体用于提取所述RP地址、所述第一Assert记录集和所述第二Assert记录集的所述组播组地址，并组合所述第一Assert记录集和所述第二Assert记录集的组播源地址生成所述Assert消息。
  23. 根据权利要求20-22任一所述的设备，其特征在于，所述设备还包括接收单元，所述接收单元用于接收组播网中其他网络节点发送的Hello报文，所述Hello报文携带第一标识，所述第一标识用于指示所述组播网中其他网络节点支持接收所述Assert消息的功能。
  24. 根据权利要求20-23任一所述的设备，其特征在于，所述Assert消息携带组播组地址和组播源地址的数目。
  25. 一种组播网络中获取Assert消息的设备，其特征在于，该设备包括：
    接收单元，用于接收Assert消息，所述Assert消息包括一个组播源地址和多个组播组地址；
    获取单元，用于通过解析所述Assert消息获得多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括所述组播源地址和所述多个组播组地址中的一个组播组地址，所述多个Assert记录中的组播组地址互不相同。
  26. 根据权利要求25所述的设备，其特征在于，所述获取单元，具体用于将所述Assert消息携带的所述组播源地址和所述多个组播组地址进行组合，获取所述多个Assert记录。
  27. 一种组播网络中获取Assert消息的设备，其特征在于，该设备包括：
    接收单元，用于接收Assert消息，所述Assert消息包括汇聚点RP地址和第一Assert记录集，所述第一Assert记录集包括第一组播组地址和多个组播源地址；
    获取单元，用于通过解析第一Assert记录集获取多个Assert记录，所述多个Assert记录中的每个Assert记录分别包括一个组播源地址和一个组播组地址，所述多个Assert记录中不同的Assert记录分别包含第一组播组地址。
  28. 根据权利要求27所述的设备，其特征在于，所述Assert消息还包括第二Assert记录集，所述获取单元，还用于通过解析第二Assert记录集获得多个Assert记录，所述第二Assert记录集中不同的Assert记录分别包含第二组播组地址，所述第一组播组地址和所述第二组播组地址不同。
PCT/CN2020/075199 2019-02-21 2020-02-14 一种发送和获取断言报文的方法和网络节点 WO2020168982A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20759660.2A EP3905613A4 (en) 2019-02-21 2020-02-14 PROCEDURE FOR SENDING AND RECEIVING AN ASSERT MESSAGE AND NETWORK NODES
US17/382,596 US11909546B2 (en) 2019-02-21 2021-07-22 Method and network node for sending and obtaining assert packet

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910128323.1 2019-02-21
CN201910128323.1A CN111600798B (zh) 2019-02-21 2019-02-21 一种发送和获取断言报文的方法和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/382,596 Continuation US11909546B2 (en) 2019-02-21 2021-07-22 Method and network node for sending and obtaining assert packet

Publications (1)

Publication Number Publication Date
WO2020168982A1 true WO2020168982A1 (zh) 2020-08-27

Family

ID=72144784

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075199 WO2020168982A1 (zh) 2019-02-21 2020-02-14 一种发送和获取断言报文的方法和网络节点

Country Status (4)

Country Link
US (1) US11909546B2 (zh)
EP (1) EP3905613A4 (zh)
CN (2) CN114221913A (zh)
WO (1) WO2020168982A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114205287B (zh) * 2021-12-17 2024-03-19 锐捷网络股份有限公司 组播接收者信息收集方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101989952A (zh) * 2010-11-03 2011-03-23 中兴通讯股份有限公司 一种组播方法及装置
US9356789B1 (en) * 2013-09-25 2016-05-31 Juniper Networks, Inc. Robust control plane assert for protocol independent multicast (PIM)
CN106302176A (zh) * 2016-08-15 2017-01-04 华为技术有限公司 一种用于控制组播传输的方法及设备
CN109218207A (zh) * 2018-09-30 2019-01-15 新华三技术有限公司 一种组播流量处理方法、装置及路由设备

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7746858B2 (en) * 2006-01-03 2010-06-29 Cisco Technology, Inc. Scaling enhancement for PIM control messages in multicast VPNs
CN100456684C (zh) * 2006-04-07 2009-01-28 华为技术有限公司 一种组播业务的实现方法和网络设备
US8345683B1 (en) * 2006-07-31 2013-01-01 Alcatel Lucent Data plane independent assert election
CN101420362B (zh) * 2007-10-22 2012-08-22 华为技术有限公司 组播流量切换的方法、系统及路由器
CN101635671A (zh) * 2008-07-25 2010-01-27 华为技术有限公司 加快组播收敛的方法、系统和设备
CN101459606B (zh) * 2008-12-31 2011-04-20 华为技术有限公司 一种组播虚拟私有网络的外联网组网方法、系统和装置
CN101789900B (zh) * 2009-11-19 2012-08-15 福建星网锐捷网络有限公司 组播转发路径的查询方法、中间节点和管理节点
US9240942B2 (en) * 2011-02-28 2016-01-19 Cisco Technology, Inc. Bandwidth utilization for equal cost multiple paths
CN102158415B (zh) * 2011-04-22 2015-01-28 中兴通讯股份有限公司 本地局域网中组播流量转发方法及组播路由器
US9619989B1 (en) * 2014-05-01 2017-04-11 Synapse Wireless, Inc. Asset tracking systems and methods
US9160553B2 (en) * 2013-11-27 2015-10-13 Architecture Technology Corporation Adaptive multicast network communications
CN106878188B (zh) * 2017-01-16 2019-11-12 新华三技术有限公司 一种断言报文的发送方法和装置
US20180367451A1 (en) * 2017-06-16 2018-12-20 Cisco Technology, Inc. Optimized protocol independent multicast assert mechanism

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101989952A (zh) * 2010-11-03 2011-03-23 中兴通讯股份有限公司 一种组播方法及装置
US9356789B1 (en) * 2013-09-25 2016-05-31 Juniper Networks, Inc. Robust control plane assert for protocol independent multicast (PIM)
CN106302176A (zh) * 2016-08-15 2017-01-04 华为技术有限公司 一种用于控制组播传输的方法及设备
CN109218207A (zh) * 2018-09-30 2019-01-15 新华三技术有限公司 一种组播流量处理方法、装置及路由设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3905613A4

Also Published As

Publication number Publication date
US11909546B2 (en) 2024-02-20
EP3905613A4 (en) 2022-02-09
EP3905613A1 (en) 2021-11-03
CN111600798B (zh) 2021-11-19
US20210351947A1 (en) 2021-11-11
CN111600798A (zh) 2020-08-28
CN114221913A (zh) 2022-03-22

Similar Documents

Publication Publication Date Title
US11206148B2 (en) Bit indexed explicit replication
US8339973B1 (en) Multicast traceroute over MPLS/BGP IP multicast VPN
US9077551B2 (en) Selection of multicast router interfaces in an L2 switch connecting end hosts and routers, which is running IGMP and PIM snooping
US7477642B2 (en) MPLS traffic engineering for point-to-multipoint label switched paths
EP2437444A1 (en) Method, router and communication system for rapid multicast convergence
US9160616B2 (en) Multicast packet transmission method, related device and system
US11381883B2 (en) Dynamic designated forwarder election per multicast stream for EVPN all-active homing
CN109981323B (zh) 一种检测数据链路层组播路径状态的方法和网络设备
EP2783482A1 (en) Improved replication management for remote multicast replication network
US20180367451A1 (en) Optimized protocol independent multicast assert mechanism
US9548917B2 (en) Efficient multicast delivery to dually connected (VPC) hosts in overlay networks
WO2022021818A1 (zh) 数据报文的处理方法及装置、存储介质、电子装置
WO2021093463A1 (zh) 报文转发的方法、第一网络设备以及第一设备组
US20230155921A1 (en) Multicast packet sending method, apparatus, and system
EP2719120B1 (en) Protocol independent multicast last hop router discovery
KR20220062347A (ko) 역 경로 포워딩 rpf 검사 방법 및 장치
WO2020168982A1 (zh) 一种发送和获取断言报文的方法和网络节点
US9313037B2 (en) Method, apparatus and system for forwarding data under protocol independent multicast dual join
CN108011828B (zh) 一种组播切换方法、装置、核心层交换机及存储介质
WO2012103748A1 (zh) 一种组播控制方法、路由设备及组播系统
WO2020244372A1 (zh) 一种实现组播的方法和装置
CN116094987A (zh) 转发路径的确定方法及装置
CN113992564A (zh) 报文处理方法及装置
CN107276774B (zh) 一种组播报文传输方法以及转发设备
KR102568754B1 (ko) Bierv6 패킷 전달 방법, 장치 및 시스템

Legal Events

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

Ref document number: 20759660

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020759660

Country of ref document: EP

Effective date: 20210728

NENP Non-entry into the national phase

Ref country code: DE