WO2012152180A1 - Ds-lite网络架构承载组播业务的方法、系统和网络节点 - Google Patents

Ds-lite网络架构承载组播业务的方法、系统和网络节点 Download PDF

Info

Publication number
WO2012152180A1
WO2012152180A1 PCT/CN2012/074551 CN2012074551W WO2012152180A1 WO 2012152180 A1 WO2012152180 A1 WO 2012152180A1 CN 2012074551 W CN2012074551 W CN 2012074551W WO 2012152180 A1 WO2012152180 A1 WO 2012152180A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
ipv4
ipv6
packet
multicast packet
Prior art date
Application number
PCT/CN2012/074551
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 中兴通讯股份有限公司
Publication of WO2012152180A1 publication Critical patent/WO2012152180A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast

Definitions

  • the present invention relates to a multicast technology for network communication, and in particular, to a method, system and network node for carrying a multicast service in a DS-lite (Dual-Stack-lite) network architecture.
  • Background technique
  • IPv4 In the evolution of IPv4 to IPv6, many services are still in IPv4 format, and many client devices cannot update or upgrade to IPv6 very quickly. Therefore, IPv4 and IPv6 will coexist for a long time. During this evolution, in advance At the same time as IPv6 services, it is necessary to ensure that IPv4 services need not be interrupted.
  • IPTV Internet TV
  • IPTV Internet TV
  • mB4 Multicast Basic Bridging BroadBand element
  • - lite network architecture One of the two basic functional modules in multicast, usually located in the client device (CPE), mainly used for Internet Group Management Protocol (IGMP) to multicast listening and discovery protocol (MLD, Multicast) Listener Discover) and decapsulate IPv4-in-IPv6 multicast packets into corresponding IPv4 multicast packets and send them to the appropriate IPv4 multicast receivers.
  • CPE client device
  • IGMP Internet Group Management Protocol
  • MLD multicast listening and discovery protocol
  • MLD multicast listening and discovery protocol
  • the Transition Router element is used to encapsulate the IPv4 multicast packets of the IPv4 multicast source into corresponding IPv4-in-IPv6 multicast packets and send them in the appropriate IPv6 multicast distribution tree of the IPv6 access network.
  • the IPv4 multicast source sends IPv4 multicast packets.
  • mAFTR After the mAFTR receives the IPv4 multicast packet, the mAFTR searches the IPv4 multicast routing table according to the address of the IPv4 multicast packet. If the address matching the interface is found in the IPv4 multicast routing table, the mAFTR pair The IPv4 multicast packet is encapsulated, and the prefix configured in advance to the mAFTR is used in the encapsulation process.
  • the stateless mapping algorithm is used to map the IPv4 address in the IPv4 multicast packet to the corresponding IPv4-embedded IPv6 address, and use these IPv4-embedded
  • the IPv6 address is used as the source address and the multicast address to encapsulate IPv4 multicast packets into IPv4-in-IPv6 multicast packets.
  • mAFTR does not receive IPv4 multicast packets.
  • the source address and the destination address of the port are translated.
  • the mAFTR sends IPv4-in-IPv6 multicast packets along the IPv6 multicast distribution tree to the corresponding mB4.
  • mB4 When the mB4 receives the IPv4-in-IPv6 multicast report. In this case, mB4 first checks whether the multicast address of the IPv4-in-IPv6 multicast packet is within the pre-assigned mPrefix range and whether the source address is in the allocated uPrefix range. If not, the IPv4-in is discarded. -IPv6 multicast report , If at all, the decapsulating the IPv4-in-IPv6 multicast packets, thereby obtaining the original IPv4 multicast packets, and multicast packets to the IPv4 multicast downstream recipients.
  • the draft-qin-softwire-dslite-multicast described above mainly describes the multicast scenario when the Ds-lite network architecture is used as a transition scheme when the network is 4-6-4, where the tunneling technology using IPv4-in-IPv6 is adopted.
  • An IPv6 network can transmit IPv4 multicast packets.
  • the solution only maps the IPv4 address in the IPv4 multicast packet to the corresponding IPv4-embedded IPv6 address. It is only equivalent to adding a packet header for the IPv4 multicast packet to the IPv6 network.
  • the IPv4 multicast packet is still in the IPv4 format. This is not conducive to the transmission efficiency of the IPv4 multicast packet in the IPv6 network. Can not make the most of the multicast capabilities of IPv6 networks. Summary of the invention
  • the main purpose of the present invention is to provide a method, system, and network node for carrying a multicast service in a DS-lite network architecture, and improve the transmission efficiency of IPv4 multicast packets in an IPv6 network. Rate, the largest use of IPv6 network multicast capabilities.
  • the method for carrying a multicast service in the DS-lite network architecture provided by the present invention includes: when the mAFTR receives the IPv4 multicast packet sent by the multicast source, translating the IPv4 multicast packet into an IPv6 group Broadcast the message, and send the IPv6 multicast message to mB4;
  • the mB4 When receiving the IPv6 multicast packet, the mB4 translates the IPv6 multicast packet into an IPv4 multicast message, and multicasts the IPv4 multicast message to the multicast receiver.
  • the mAFTR translates the IPv4 multicast packet into the IPv6 multicast packet by: creating a new IPv6 multicast packet, and all the fields in the IPv6 multicast packet header are based on the IPv4 multicast packet. The header is filled in, and the content of the message remains unchanged.
  • the mAFTR translates the IPv4 multicast packet into an IPv6 multicast packet: the mAFTR creates an IPv6 multicast packet, and sets the version (Version) field in the newly created IPv6 multicast packet header to 6;
  • the Traffic Class field value is set to be the same as the service type (TOS, Type Of Service) in the IPv4 multicast packet;
  • the Flow Label field value is set to 0;
  • the payload length (Playload Length) field value is set.
  • the value of the total length of the IPv4 multicast packet is subtracted from the length of the IPv4 header; the value of the next header is obtained from the protocol field in the IPv4 multicast packet header;
  • the value of the (Hop Limit) field is the same as the value of the TTL (Time to Live) field in the IPv4 multicast packet.
  • the value of the Source Address field is obtained from the source address of the IPv4 multicast packet.
  • the value of the Address field is obtained from the destination address of the IPv4 multicast packet; the content in the IPv6 multicast packet is the same as the content in the IPv4 multicast packet.
  • the mB4 translates the IPv6 multicast packet into an IPv4 multicast packet by: creating an IPv4 multicast packet, and all fields in the IPv4 multicast packet header are based on the IPv6 multicast.
  • the message header is filled in, and the message content remains unchanged.
  • the mB4 translates the IPv6 multicast packet into an IPv4 multicast packet:
  • the mB4 creates an IPv4 multicast packet, and sets the Version field in the IPv4 multicast packet header to 4; the Internet header length (Internet Header Length) value is set to 5; and the TOS value is set in the IPv6 multicast packet.
  • the value of the Traffic Class is set to the value of the length of the IPv4 header on the payload of the IPv6 multicast packet.
  • the value of the Identification, Flags, Fragment Off field is set to 0.
  • the value of the TTL field is the Hop Limit field in the IPv6 multicast packet.
  • the value of the Source Address field is the source address of the IPv6 multicast packet that is mapped to the source address of the IPv4 multicast packet.
  • the value of the Destination Address field is the multicast address of the IPv6 multicast packet mapped to the multicast in the IPv4 multicast packet. Address: The content in the IPv4 multicast packet is the same as the content in the IPv6 multicast packet.
  • the method further includes: multicasting at any source (ASM, Any-Source)
  • the mAFTR when the mAFTR receives an IPv4 multicast packet as a registration packet, the mAFTR decapsulates the registration packet and obtains an IPv4 multicast packet.
  • a system for carrying a multicast service in a DS-lite network architecture includes: mAFTR, mB4;
  • the mAFTR is configured to: when receiving the IPv4 multicast message sent by the multicast source, translate the IPv4 multicast message into an IPv6 multicast message, and send the IPv6 multicast message to the mB4;
  • the mB4 when receiving the IPv6 multicast message, translate the IPv6 multicast message into an IPv4 multicast message, and multicast the IPv4 multicast message to the multicast receiving By.
  • the mAFTR is specifically configured to: when receiving an IPv4 multicast packet sent by the multicast source, create an IPv6 multicast packet, and all the fields in the IPv6 multicast packet header are based on the IPv4 multicast. The message header is filled in, and the message content remains unchanged.
  • the mB4 is specifically configured to: when receiving an IPv6 multicast packet sent by the mAFTR, create an IPv4 multicast packet, and use all the fields in the IPv4 multicast packet header based on the IPv6 multicast packet. The header is filled in, and the content of the message remains unchanged.
  • the present invention provides a DS-lite network carrying a multicast service network node, the network section
  • the point includes the mAFTR, and the mAFTR, when receiving the IPv4 multicast message sent by the multicast source, translates the IPv4 multicast message into an IPv6 multicast message, and sends the IPv6 multicast message to the mB4.
  • the present invention provides a method, system, and network node for carrying a multicast service in a DS-lite network architecture.
  • the mAFTR When the mAFTR receives an IPv4 multicast packet sent by a multicast source, the mAFTR translates the IPv4 multicast packet into an IPv6 group. Broadcasting the packet and sending the IPv6 multicast packet to the mB4; when receiving the IPv6 multicast packet, the mB4 translates the IPv6 multicast packet into an IPv4 multicast packet, and the IPv4 multicast packet is translated. Multicast to the downstream multicast receivers. In this way, the IPv4 multicast packets can be completely translated into IPv6 multicast packets and transmitted on the IPv6 network. This improves the transmission efficiency of IPv4 multicast packets in the IPv6 network. Take advantage of the multicast capabilities of IPv6 networks. DRAWINGS
  • FIG. 1 is a schematic diagram of a topology of a DS-lite multicast network in the prior art
  • FIG. 2 is a schematic flow chart of a method for implementing a DS-lite network architecture to carry a multicast service according to the present invention
  • FIG. 3 is a schematic diagram of a network architecture of configuring uPrefix and mPrefix64 according to the present invention
  • FIG. 4 is a schematic diagram of address mapping according to the present invention.
  • FIG. 5 is a schematic diagram of a network architecture of an IPv6 multicast distribution tree according to the first embodiment of the present invention
  • FIG. 6 is a schematic diagram of a network architecture of an IPv6 multicast distribution tree according to the second embodiment of the present invention
  • FIG. 8 is a schematic flowchart of a method for implementing a DS-lite network architecture to carry a multicast service in an SSM mode according to the present invention
  • FIG. 9 is a schematic diagram of a network architecture of an ASM mode according to the present invention.
  • FIG. 10 is a schematic flowchart of a method for implementing a DS-lite network architecture to carry a multicast service in an ASM mode according to the present invention. detailed description
  • the basic idea of the present invention is: when the mAFTR receives the IPv4 multicast message sent by the multicast source, the IPv4 multicast message is translated into an IPv6 multicast message, and the IPv6 multicast message is sent to the mB4; When receiving the IPv6 multicast packet, the mB4 translates the IPv6 multicast packet into an IPv4 multicast message, and multicasts the IPv4 multicast message to the downstream multicast receiver.
  • the present invention implements a method for carrying a multicast service in a DS-lite network architecture. As shown in FIG. 2, the method includes the following steps:
  • Step 101 When the mAFTR receives the IPv4 multicast packet sent by the multicast source, the mAFTR translates the IPv4 multicast packet into an IPv6 multicast packet, and sends the IPv6 multicast packet to the mB4.
  • the mAFTR searches the IPv4 multicast routing table according to the address of the IPv4 multicast packet, if a matching interface is found in the IPv4 multicast routing table. Address, the mAFTR translates the IPv4 multicast packet into an IPv6 multicast packet, and sends the IPv6 multicast packet to the mB4 through the IPv6 multicast distribution tree.
  • the mAFTR translates the IPv4 multicast packet into an IPv6 multicast packet, and generally creates an IPv6 multicast packet, and fills in all the fields in the IPv6 multicast packet header based on the IPv4 multicast packet header.
  • the content of the text is unchanged, specifically: the mAFTR creates an IPv6 multicast packet, and sets the Version field in the IPv6 multicast packet header to 6; the Traffic Class field value is set to be the same as the TOS in the IPv4 multicast packet; The value of the Label field is set to 0.
  • the value of the Playload Length field is the length of the IPv4 multicast packet minus the length of the IPv4 header.
  • the value of the Next Header is obtained from the protocol field in the IPv4 multicast packet header.
  • the value of the TTL field in the broadcast message is the same; the value of the Source Address field is obtained from the source address of the IPv4 multicast packet; the value of the Destination Address field is obtained from the destination address of the IPv4 multicast packet, and the IPv4 option field in the IPv4 multicast packet is ignored.
  • the content in the IPv6 multicast packet is the same as the content in the IPv4 multicast packet.
  • the value of the Source Address field is obtained from the source address of the IPv4 multicast packet.
  • the mAFTR maps the source address of the IPv4 multicast packet according to the configured unicast prefix (uPrefix, unicast Prefix) and the stateless mapping algorithm. Source address of the IPv6 multicast packet.
  • the value of the Destination Address field is obtained from the destination address of the IPv4 multicast message.
  • the mAFTR uses the stateless mapping algorithm according to the configured multicast prefix (mPrefix64, multicast Prefix) to multicast the IPv4 multicast packet. Multicast address mapped to IPv6 multicast packets.
  • the step further includes: if there is a checksum of the TCP, UDP, and ICMP in the load of the IPv4 multicast packet, the source and the multicast address of the IPv6 multicast packet obtained by the mapping are recalculated. Checksum.
  • the configuration method of the uPrefix and the mPrefix64, as shown in FIG. 3 includes:
  • the CPE and the mAFTR send a DHCPv6 request message to the Dynamic Host Configuration Protocol 6 (DHCPv6) server, requesting to obtain uPrefix and mPrefix64;
  • DHCPv6 Dynamic Host Configuration Protocol 6
  • the CPE and mAFTR After receiving the DHCPv6 response message, the CPE and mAFTR record the uPrefix and mPrefix64 in the option to complete the configuration.
  • the configuration of the above-mentioned CPE and mAFTR uPrefix and mPrefix64 can also be configured by other methods, for example, the CPE and the mAFTR are manually configured by the administrator, but the prefix configured for the CPE and the mAFTR must be the same; There are generally mB4, that is, uPrefix and mPrefix64 configured for CPE are also configured on mB4.
  • the source address of the IPv4 multicast packet is mapped to the source address of the IPv6 multicast packet and the multicast address of the IPv4 multicast packet is mapped to the IPv6 multicast packet.
  • the multicast mapping of the text, the specific mapping process is shown in Figure 4:
  • the multicast address ( 230.1.2.3 ) and mPrefix64 ( ff00:abc::/96 ) of IPv4 multicast packets are mapped to the multicast address of IPv6 multicast packets ( ff00:abc::230.1.2.3
  • the source address of the IPv4 multicast message (192.1.2.3) and the source address of the IPv6 multicast packet (2001: db8:: 192.1.2.3) are mapped to the uPrefix (2001: db8::/96).
  • IPv6 multicast distribution tree The establishment of the IPv6 multicast distribution tree described in this step is described in detail below by using examples one and two.
  • Example 1 As shown in Figure 5, when the mAFTR is located in the MLD Querier/ ⁇ designated router (DR Designated Router), if the specified source-specific multicast (SSM) mode is deployed, the IPv4 multicast source is assumed to be S (192.1). .2.3), IPv4 receiver A needs to join the corresponding IPv4 multicast group when receiving the multicast packets of S.
  • SSM source-specific multicast
  • the IPv4 receiver A sends an IGMP report message to the CPE1, and indicates in the IGMP report message that the address to be added to the IPv4 multicast group G (230.1.2.3);
  • the mB4 located on the CPE1 After receiving the IGMP message, the mB4 located on the CPE1 generates an IPv6 multicast group address corresponding to the address G (230.1.2.3) of the IPv4 multicast group according to the pre-configured mPrefix64 and uPrefix and the stateless mapping algorithm.
  • G ( ff00:abc::230.1.2.3 ), that is, mapping the address G of the IPv4 multicast group to the IPv6 multicast group address G, ( ff00:abc: :230.1.2.3 ), IPv4 source
  • the MLD message contains the IPv6 multicast group address.
  • the mAFTR sends the PIMv4 Join message to the IPv6 multicast group address G in the MLD.
  • the PIMv4 Join message contains the address G of the IPv4 multicast group that the IPv4 receiver A wants to join. ( 230.1.2.3 );
  • mAFTR since mAFTR is located on MLD Querier/ ⁇ DR, when mAFTR receives After the MLD message is received, the corresponding record is checked according to the IPv6 multicast group address G, and the port that receives the MLD message is added to the Out-Interface-List. If there is no corresponding record, the mAFTR generates and IPv6 multicast group address G, corresponding to the new record. The mAFTR verifies that the prefix of the IPv6 multicast group address G, ( ff00:abc: :230.1.2.3 ) in the MLD packet belongs to the configured mPrefix64.
  • the mAFTR is from the IPv6 multicast group G, ( ff00:abc: :230.1.2.3 ) maps the address G ( 230.1.2.3 ) of the corresponding IPv4 multicast group, and checks the corresponding IPv4 multicast routing table, adds the tunnel interface to the Out-Interface-List, and the mAFTR also generates a
  • the PIMv4 Join message contains the address G (230.1.2.3) of the IPv4 multicast group to be joined.
  • the mAFTR sends the PIMv4 Join message to the RP (Rendezvous Point) or
  • IPv4 multicast source IPv4 multicast source
  • IPv6 multicast distribution tree is established.
  • the multicast packets of the IPv4 multicast source can send data to the IPv4 receiver A through the multicast distribution tree.
  • Example 2 As shown in Figure 6, the mAFTR is located in the upstream PIMv6 router. If the SSM mode is deployed, the IPv4 multicast source is assumed to be S (192.1.2.3). When receiving the multicast data of S, the IPv4 receiver A needs to join the corresponding IPv4 multicast group.
  • the specific steps for establishing the IPv6 multicast distribution tree are as follows:
  • the IPv4 receiver A sends an IGMP report message to the mB4, and indicates in the IGMP report message that the address to be added to the IPv4 multicast group G (230.1.2.3);
  • the mB4 located on the CPE1 After receiving the IGMP report message, the mB4 located on the CPE1 generates an IPv6 multicast group corresponding to the address G (230.1.2.3) of the IPv4 multicast group according to the pre-configured mPrefix64 and uPrefix and the stateless mapping algorithm.
  • the PIM DR After receiving the MLD message, the PIM DR generates a PIMv6 Join message through the MLD Querier.
  • the PIMv6 Join message contains the IPv6 multicast group address G, (ff00:abc::230.1.2.3) ), PIM DR sends the generated PIMv6 Join message to mAFTR;
  • the mAFTR sends a PIMv4 Join message to the IPv6 multicast group address G in the PIMv6 Join message, and the PIMv4 Join message includes the IPv4 multicast group that the IPv4 receiver A wants to join.
  • Address G ( 230.1.2.3 );
  • the mAFTR After receiving the PIMv6 Join message, the mAFTR checks the corresponding record according to the IPv6 multicast group address G, (ff00:abc::230.1.2.3) in the PIMv6 Join message, and receives the received record. The port of the PIMv6 Join message is added to the Out-Interface-List. If there is no corresponding record, the mAFTR generates a new record corresponding to the IPv6 multicast group address G. Then the mAFTR checks the IPv6 multicast group in the PIMv6 Join message.
  • the prefix of the address G ( ff00:abc::230.1.2.3 ) belongs to the configured mPrefix64 ( ff00:abc::/96 )
  • the mAFTR is from the IPv6 multicast group address G
  • ( ff00:abc: :230.1.2.3 ) maps the address G ( 230.1.2.3 ) of the corresponding IPv4 multicast group, and checks the corresponding IPv4 multicast routing table, adds the tunnel interface to the Out-Interface-List, and the mAFTR also generates A PIMv4 Join message
  • the PIMv4 Join message contains the address G ( 230.1.2.3 ) of the IPv4 multicast group that you want to join.
  • the mAFTR sends the PIMv4 Join message to the RP or IPv4 multicast source.
  • IPv6 multicast distribution tree is established.
  • the multicast packets of the IPv4 multicast source can send data to the IPv4 receiver A through the multicast distribution tree.
  • Step 102 When the mB4 receives the IPv6 multicast packet, the IPv6 multicast packet is translated into an IPv4 multicast packet, and the IPv4 multicast packet is multicast to the downstream multicast receiver.
  • the mB4 After receiving the IPv6 multicast packet, the mB4 checks whether the multicast address of the IPv6 multicast packet matches the configured mPrefix64, and the source address matches the configured uPrefix. Multicast packets are translated into IPv4 multicast packets, and according to the IPv4 The multicast member information in the multicast packet is used to multicast the IPv4 multicast packet to the downstream multicast receiver.
  • the mB4 translates the IPv6 multicast packet into an IPv4 multicast packet, which is usually a new IPv4 multicast packet. For example, the field in the IPv4 multicast packet header is filled in based on the IPv6 multicast packet header, and the content of the packet is unchanged.
  • the specific information is as follows: The mB4 creates an IPv4 multicast packet, and the IPv4 multicast packet is sent.
  • the Version field in the header is set to 4; the Internet Header Length value is set to 5; the TOS value is set to the value of the Traffic Class in the IPv6 multicast packet; and the Total Length value is set to the value of the playload value in the IPv6 multicast packet plus the length of the IPv4 header.
  • the value of the Identification, Flags, and Fragment Off fields is set to 0.
  • the value of the Time to Live field is the value of the Hop Limit field in the IPv6 multicast packet.
  • the value of the Source Address field is the source address in the IPv6 multicast packet mapped to the IPv4 multicast.
  • the source address of the packet; the value of the Destination Address field is the multicast address of the IPv6 multicast packet mapped to the multicast address in the IPv4 multicast packet; the content of the IPv4 multicast packet is the same as the content of the IPv6 multicast packet. .
  • the present invention further provides a system for carrying a multicast service in a DS-lite network architecture, where the system includes: mAFTR, mB4;
  • the mAFTR is configured to: when receiving the IPv4 multicast packet sent by the multicast source, translate the IPv4 multicast packet into a corresponding IPv6 multicast packet, and send the IPv6 multicast packet to the mB4;
  • the mB4 configured to translate the IPv6 multicast packet into a corresponding IPv4 multicast packet, and multicast the IPv4 multicast packet to a downstream multicast receiver;
  • the mAFTR is configured to: when receiving an IPv4 multicast packet sent by the multicast source, create an IPv6 multicast packet, and fill in all the fields in the IPv6 multicast packet header according to the IPv4 multicast packet header. , the message content remains unchanged;
  • the mAFTR when receiving the IPv4 multicast packet sent by the multicast source, the mAFTR creates an IPv6 multicast packet, and sets the Version field in the IPv6 multicast packet header to 6; the Traffic Class field value is set to The TOS in the IPv4 multicast packet is the same; the value of the Flow Label field is set to 0; the value of the Playload Length field is the length of the IPv4 multicast 4 minus the length of the IP header; Next Header The value is obtained from the protocol in the IPv4 multicast packet header; the value of the Hop Limit is the same as the TTL value in the IPv4 multicast packet; the value of the Source Address field is obtained from the source address of the IPv4 multicast packet; the value of the Destination Address field is The destination address of the IPv4 multicast packet is obtained and the IPv4 option field in the IPv4 multicast packet is received.
  • the content of the IPv6 multicast packet is the same as the content of the IPv4 multicast packet.
  • the mB4 is configured to: when receiving an IPv6 multicast packet sent by the mAFTR, create an IPv4 multicast packet, and fill in all the fields in the IPv4 multicast packet header according to the IPv6 multicast packet header. The content of the text remains unchanged;
  • the mB4 when receiving the IPv6 multicast packet sent by the mAFTR, the mB4 creates an IPv4 multicast packet, sets the Version field in the IPv4 multicast packet header to 4, and sets the Internet Header Length value to 5; The value is set to the value of the Traffic Class in the IPv6 multicast packet.
  • the Total Length value is set to the value of the playload value in the IPv6 multicast packet plus the length of the IPv4 header.
  • the value of the Identification, Flags, and Fragment Off fields is set to 0.
  • the value of the Source Limit field is the value of the source limit in the IPv6 multicast packet.
  • the value of the Source Address field is the source address of the IPv4 multicast packet.
  • the value of the Destination Address field is the multicast in the IPv6 multicast packet. The address is mapped to the multicast address in the IPv4 multicast packet.
  • the mAFTR is specifically configured to send the IPv6 multicast message to the mB4o through an IPv6 multicast distribution tree.
  • the mAFTR is further configured to: after receiving the IPv4 multicast message, decapsulating the registration message to obtain an IPv4 multicast message.
  • the present invention also implements a network node that carries a multicast service in a DS-lite network architecture, where the network node includes a mAFTR, and when the mAFTR receives the IPv4 multicast packet sent by the multicast source, the IPv4 The multicast packet is translated into an IPv6 multicast packet, and the IPv6 multicast message is sent to the mB4.
  • the mAFTR is configured to: when receiving the IPv4 multicast message sent by the multicast source, create an IPv6 multicast packet, and use the IPv4 multicast packet header in the IPv6 multicast packet header. Fill in, the message content remains unchanged;
  • the mAFTR when receiving the IPv4 multicast packet sent by the multicast source, the mAFTR creates an IPv6 multicast packet, and sets the Version field in the IPv6 multicast packet header to 6; the Traffic Class field value is set to The value of the Flow Label field is set to 0. The value of the Playload Length field is the length of the IPv4 multicast packet minus the length of the IP header. The value of the Next Header is obtained from the protocol in the IPv4 multicast packet header.
  • the value of the Hop Limit is the same as the TTL value in the IPv4 multicast packet; the value of the Source Address field is obtained from the source address of the IPv4 multicast packet; the value of the Destination Address field is obtained from the destination address of the IPv4 multicast source, and IPv4 is ignored.
  • the IPv4 option field in the multicast packet is the same as the content in the IPv4 multicast packet.
  • the present embodiment is shown in FIG. 7.
  • the host in the IPv4 network ⁇ 192.1.2.3
  • the method for carrying the multicast service is as shown in FIG. 8. The method includes the following steps:
  • Step 201 Host B generates an IPv4 multicast message, and sends the IPv4 multicast message to the mAFTR, where the source address is the address S (192.1.2.3) of the host B, and the destination address is the address G of the IPv4 multicast group. 230.1.2.3 );
  • Step 202 After receiving the IPv4 multicast message, the mAFTR translates the IPv4 multicast message into an IPv6 multicast message, and sends the IPv6 multicast message to the mB4 through the IPv6 multicast distribution tree.
  • the mAFTR is based on the IPv4
  • the address of the multicast packet is searched in the IPv4 multicast routing table. If the matching interface address is found in the IPv4 multicast routing table, the mAFTR translates the IPv4 multicast packet into the corresponding IPv6 multicast packet and passes the The IPv6 multicast distribution tree sends the IPv6 multicast packet to mB4.
  • the mAFTR translates the IPv4 multicast message into a corresponding IPv6 multicast message, specifically: the mAFTR creates an IPv6 multicast packet, and sets the Version field in the IPv6 multicast packet header to 6;
  • the value of the Class field is set to be the same as the TOS in the IPv4 multicast packet;
  • the value of the Flow Label field is set to 0;
  • the value of the Playload Length field is set to the length of the IPv4 multicast packet minus the IP header;
  • the value of the Next Header is from the IPv4 group.
  • the value of the Hop Limit is the same as the TTL value in the IPv4 multicast packet.
  • the source address value is the source address of the IPv4 multicast packet based on the configured uPrefix prefix and the stateless mapping algorithm.
  • 192.1.2.3 Mapping to the source address S of IPv6 multicast packets, ( 2001:db8::192.1.2.3 );
  • the value of the Destination Address field is based on the configured mPrefix64 using the stateless mapping algorithm, which will be IPv4 multicast.
  • the multicast address of the text is mapped to the multicast address G of the IPv6 multicast packet, ( ff00:abc::230.1.2.3 ); the IPv4 option field in the IPv4 multicast packet is ignored; the content and IPv4 group in the IPv6 multicast packet broadcast The content in the message is the same.
  • Step 203 When the mB4 receives the IPv6 multicast packet, the IPv6 multicast packet is translated into an IPv4 multicast packet, and the IPv4 multicast packet is multicast to the downstream IPv4 receiver A. After receiving the IPv6 multicast packet, the mB4 checks whether the multicast address G of the IPv6 multicast packet, ( ff00:abc: :230.1.2.3 ) matches the configured mPrefix64 ( ff00:abc::/96 ).
  • mB4 translates the IPv6 multicast packet into an IPv4 multicast packet. And multicasting the IPv4 multicast packet to the downstream IPv4 receiver A according to the multicast member information in the IPv4 multicast packet;
  • the mB4 translates the IPv6 multicast packet into an IPv4 multicast packet, specifically: the mB4 creates an IPv4 multicast packet, and sets the Version field in the IPv4 multicast packet header to 4;
  • the value of the Header Length is set to 5;
  • the value of the Type Of Service is set to the value of the Traffic Class in the IPv6 multicast packet;
  • the value of the Total Length is set to the value of the IPv4 header in the IPv6 multicast packet;
  • the values of the Identification, Flags, and Fragment Off fields are Set to 0;
  • the value 0 of the Time to Live field is the value of the Hop Limit field in the IPv6 multicast packet;
  • the value of the Source Address is the source address S in the IPv6 multicast packet, (2001: db8::192.1.2.3) is mapped to the IPv4 address.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • a certain host B (192.1.2.3) in the IPv4 network sends an IPv4 multicast packet to the IPv4 multicast group where the IPv4 receiver A is located through the IPv6 network, thereby implementing DS-
  • the lite network architecture carries a multicast service, as shown in FIG. 10, and the method includes the following steps:
  • Step 301 Host B generates an IPv4 multicast packet, and sends the IPv4 multicast packet to the DR where the host B is located.
  • the DR sends the IPv4 multicast packet to the mAFTR, where the source address is the address S of the host B. 192.1.2.3), the destination address is the address G of the IPv4 multicast group (230.1.2.3);
  • the DR encapsulates the IPv4 multicast packet as a registration message, and Sent to the mAFTR as the RP; if there is already an SPT from the RP to the DR, the DR sends the IPv4 multicast message directly to the mAFTR as the RP.
  • Step 302 After receiving the IPv4 multicast packet, the mAFTR translates the IPv4 multicast message into an IPv6 multicast message, and sends the IPv6 multicast message to the mB4 through the IPv6 multicast distribution tree.
  • the mAFTR After the mAFTR receives the IPv4 multicast packet, if the IPv4 multicast packet is a registration packet, the mAFTR decapsulates the registration packet to obtain an IPv4 multicast packet, and sends the join message to the host B. ⁇ ; If mAFTR receives an encapsulated IPv4 multicast message, then The mAFTR sends a Register-Stop Message to the DR where the host B is located. The mAFTR searches the IPv4 multicast routing table based on the IPv4 multicast routing address. If a match is found in the IPv4 multicast routing table.
  • the interface address, the mAFTR translates the IPv4 multicast message into the IPv6 multicast message, and sends the IPv6 multicast message to the mB4 through the IPv6 multicast distribution tree.
  • the mAFTR translates the IPv4 multicast message into
  • the method of the IPv6 multicast packet is similar to the step 202, and is not described here.
  • Step 303 When the mB4 receives the IPv6 multicast packet, the IPv6 multicast packet is translated into an IPv4 multicast packet, and the IPv4 multicast packet is multicast to the downstream IPv4 receiver A.
  • the method for the mB4 to translate the IPv6 multicast packet into the IPv4 multicast packet is similar to the step 203, and details are not described herein again.
  • the solution of the present invention converts IPv4 and IPv6 into multicast messages by using mAFTR and mB4, and can completely convert IPv4 multicast packets into IPv6 multicast packets for transmission in an IPv6 network, and improve the IPv4 group.

Landscapes

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

Description

DS-lite网络架构承载组播业务的方法、 系统和网络节点 技术领域
本发明涉及网络通信的组播技术， 尤其涉及一种轻量级双协议栈 ( DS-lite, Dual-Stack-lite ) 网络架构承载组播业务的方法、 系统和网络节 点。 背景技术
在 IPv4到 IPv6的演进中， 很多业务仍然是 IPv4格式， 而且很多客户 端设备无法很快的更新或升级到 IPv6, 因此 IPv4和 IPv6将共存很长一段 时间， 在这段演进时间中， 在推进 IPv6服务的同时， 需要保证 IPv4服务需 要不被打断， DS-lite 网络架构是个很好的解决方案。 但是在现有的一些业 务如网络电视（IPTV )等， 存在着组播的需求， 而现阶段 DS-lite网络架构 只覆盖了单播服务的应用。
Draft-qin-softwire-delite-multicast 实现了采用 DS-lite 网络架构进行 4-6-4组播的需求， 其网络拓朴图如图 1所示， 其中 mB4 ( Multicast Basic Bridging BroadBand element )是 DS-lite网络架构组播中两个基本功能模块 之一， 一般位于客户端设备 ( CPE ), 主要用于 Internet组管理协议 ( IGMP, Internet Group Management Protocol )到组播侦听发现协议 ( MLD, Multicast Listener Discover )的转换以及将 IPv4-in-IPv6组播报文解封装成相应的 IPv4 组播报文， 并发送到合适的 IPv4 组播接收者； 组播地址族翻译路由器 ( mAFTR, multicast Address Family Transition Router element ), 主要用于将 IPv4组播源的 IPv4组播报文封装成相应的 IPv4-in-IPv6组播报文，并在 IPv6 接入网的合适的 IPv6组播分布树中发送。
在 IPv6组播分布树建立完毕后， IPv4组播源发送 IPv4组播报文到达 mAFTR; 当 mAFTR接收到该 IPv4组播报文后， mAFTR根据 IPv4组播报 文的地址在 IPv4组播路由表中进行查找，如果在 IPv4组播路由表中找到接 口匹配的地址， 那么 mAFTR对这个 IPv4组播报文进行封装， 在封装过程 中使用预先给 mAFTR配置的前缀， 利用无状态映射算法， 将 IPv4组播报 文中的 IPv4 地址映射到相应的 IPv4-embedded IPv6 地址， 并用这些 IPv4-embedded IPv6地址作为源地址和组播地址， 将 IPv4组播报文封装为 IPv4-in-IPv6组播报文， 其中， 在 IPv4-in-IPv6组播报文中， mAFTR并不对 收到的 IPv4组播 ^艮文的源地址和目的地址做任何的 NAT转换， mAFTR将 IPv4-in-IPv6组播报文沿着 IPv6组播分布树发送到相应的 mB4; 当 mB4收 到 IPv4-in-IPv6组播报文时， mB4首先检查 IPv4-in-IPv6组播报文的组播地 址是否在预先分配的 mPrefix范围内、 以及源地址是否在分配的 uPrefix范 围内， 如果不在， 则会丟弃该 IPv4-in-IPv6组播报文， 如果都在， 则解封装 该 IPv4-in-IPv6组播报文， 从而得到原始的 IPv4组播报文， 并且将这个报 文组播到下游的 IPv4组播接收者。
上述 draft-qin-softwire-dslite-multicast主要描述了当网络为 4-6-4时，使 用 Ds-lite 网络架构作为过渡方案时的组播情形， 其中， 使用 IPv4-in-IPv6 的隧道技术通过 IPv6网络来发送 IPv4组播报文， 虽然可以减轻 mAFTR的 负担并且能够利用 IPv6网络的组播能力，但是， 这种方案只是将 IPv4组播 报文中的 IPv4地址映射到相应的 IPv4-embedded IPv6地址，仅相当于在 IPv4 组播报文上增加了用于在 IPv6 网络传送的报文头， IPv4组播报文仍旧为 IPv4格式， 这样不利于该 IPv4组播报文在 IPv6网络中的传送效率， 不能 最大的利用 IPv6网络的组播能力。 发明内容
有鉴于此， 本发明的主要目的在于提供一种 DS-lite网络架构承载组播 业务的方法、 系统和网络节点，提高 IPv4组播报文在 IPv6网络中的传送效 率， 最大的利用 IPv6网络的组播能力。
为达到上述目的， 本发明的技术方案是这样实现的：
本发明提供的一种 DS-lite网络架构承载组播业务的方法，该方法包括： 当 mAFTR接收到组播源发送的 IPv4组播报文时，将所述 IPv4组播报 文翻译成 IPv6组播 4艮文， 并将所述 IPv6组播 4艮文发送到 mB4;
当 mB4接收到所述 IPv6组播报文时，将所述 IPv6组播报文翻译成 IPv4 组播艮文， 并将所述 IPv4组播艮文组播到组播接收者。
上述方案中， 所述 mAFTR将 IPv4组播报文翻译成 IPv6组播报文为： 新建 IPv6组播报文，将所述 IPv6组播报文报头中的所有字段基于所述 IPv4 组播报文报头填写， 报文内容不变。
上述方案中， 所述 mAFTR将 IPv4组播报文翻译成 IPv6组播报文为： 所述 mAFTR新建 IPv6组播报文， 将新建的 IPv6组播报文报头中的版本 ( Version )字段置为 6; 传输种类 （ Traffic Class ) 字段值置为与 IPv4组播 报文中的服务类型 （TOS, Type Of Service )相同； 流量标签（ Flow Label ) 字段值置为 0; 有效荷载长度（ Playload Length )字段值为 IPv4组播报文的 完整长度（ Total Length )值减去 IPv4头的长度值；下一个报头（ Next Header ) 的值从 IPv4组播报文报头中的协议（protocol )字段获得； 跳数限制 （Hop Limit )字段的值与 IPv4组播报文中的生存时间 （ TTL, Time to Live )字段 值相同； 源地址（ Source Address )字段的值从 IPv4组播报文的源地址获得； 目的地址（ Destination Address )字段的值从 IPv4组播 4艮文的目的地址获得； 所述 IPv6组播报文中的内容与 IPv4组播报文中的内容相同。
上述方案中，所述 mB4将所述 IPv6组播报文翻译成 IPv4组播报文为： 新建 IPv4组播报文，将所述 IPv4组播报文报头中的所有字段基于所述 IPv6 组播报文报头填写， 报文内容不变。
上述方案中，所述 mB4将所述 IPv6组播报文翻译成 IPv4组播报文为： 所述 mB4新建 IPv4组播报文， 将所述 IPv4组播报文报头中的 Version 字 段置为 4; 互联网头文件长度 ( Internet Header Length )值置为 5; TOS值 置为 IPv6组播报文中的 Traffic Class的值； Total Length值置为 IPv6组播报 文中 playload值力口上 IPv4头长度的值； Identification, Flags, Fragment Off 字段值都置为 0; TTL字段的值为 IPv6组播报文中的 Hop Limit字段的值； Source Address字段的值为 IPv6组播报文中的源地址映射到 IPv4组播报文 的源地址； Destination Address字段的值为 IPv6组播报文中的组播地址映射 到 IPv4组播报文中的组播地址； 所述 IPv4组播报文中的内容与 IPv6组播 报文中的内容相同。
上述方案中， 该方法进一步包括： 在任意信源组播（ASM, Any-Source
Multicast )模式中， mAFTR接收到 IPv4组播报文为注册报文时， mAFTR 解封装注册报文后得到 IPv4组播报文。
本发明提供的一种 DS-lite网络架构承载组播业务的系统，该系统包括： mAFTR, mB4; 其中，
所述 mAFTR,用于接收到组播源发送的 IPv4组播 4艮文时，将所述 IPv4 组播报文翻译成 IPv6组播报文， 并将所述 IPv6组播报文发送到 mB4; 所述 mB4, 用于接收到所述 IPv6组播 4艮文时， 将所述 IPv6组播 4艮文 翻译成 IPv4组播报文， 并将所述 IPv4组播报文组播到组播接收者。
上述方案中， 所述 mAFTR, 具体用于接收到组播源发送的 IPv4组播 报文时，新建 IPv6组播报文，将该 IPv6组播报文报头中的所有字段基于所 述 IPv4组播报文报头填写， 报文内容不变。
上述方案中， 所述 mB4, 具体用于接收到 mAFTR发送的 IPv6组播报 文时，新建 IPv4组播报文，将该 IPv4组播报文报头中的所有字段基于所述 IPv6组播报文报头填写， 报文内容不变。
本发明提供的一种 DS-lite网络承载组播业务的网络节点， 所述网络节 点包括 mAFTR, 所述 mAFTR接收到组播源发送的 IPv4组播报文时，将所 述 IPv4组播报文翻译成 IPv6组播报文， 并将所述 IPv6组播报文发送到 mB4。
本发明提供了一种 DS-lite网络架构承载组播业务的方法、 系统和网络 节点， 当 mAFTR接收到组播源发送的 IPv4组播报文时 , 将该 IPv4组播报 文翻译成 IPv6组播报文， 并将该 IPv6组播报文发送到 mB4; 当 mB4接收 到该 IPv6组播报文时， 将该 IPv6组播报文翻译成 IPv4组播报文， 并将该 IPv4组播报文组播到下游的组播接收者； 如此， 能够将 IPv4组播报文完全 转化为 IPv6组播报文在 IPv6网络中传送， 提高 IPv4组播报文在 IPv6网络 中的传送效率， 最大的利用 IPv6网络的组播能力。 附图说明
图 1为现有技术中 DS-lite组播网络拓朴示意图；
图 2为本发明实现一种 DS-lite网络架构承载组播业务的方法的流程示 意图；
图 3为本发明配置 uPrefix和 mPrefix64的网络架构示意图；
图 4为本发明地址映射示意图；
图 5为本发明实例一中 IPv6组播分布树的建立的网络架构示意图； 图 6为本发明实例二中 IPv6组播分布树的建立的网络架构示意图； 图 7为本发明 SSM模式的网络架构示意图；
图 8为本发明在 SSM模式中实现 DS-lite网络架构承载组播业务的方法 的流程示意图；
图 9为本发明 ASM模式的网络架构示意图；
图 10为本发明在 ASM模式中实现 DS-lite网络架构承载组播业务的方 法的流程示意图。 具体实施方式
本发明的基本思想是： 当 mAFTR接收到组播源发送的 IPv4组播报文 时， 将该 IPv4组播报文翻译成 IPv6组播报文， 并将该 IPv6组播报文发送 到 mB4;当 mB4接收到该 IPv6组播报文时，将该 IPv6组播报文翻译成 IPv4 组播 4艮文， 并将该 IPv4组播 ^艮文组播到下游的组播接收者。
下面通过附图及具体实施例对本发明做进一步的详细说明。
本发明实现一种 DS-lite网络架构承载组播业务的方法， 如图 2所示， 该方法包括以下几个步驟：
步驟 101 : 当 mAFTR接收到组播源发送的 IPv4组播报文时，将该 IPv4 组播报文翻译成 IPv6组播报文， 并将该 IPv6组播报文发送到 mB4;
具体的， 当 mAFTR接收到组播源发送的 IPv4组播报文时， mAFTR根 据 IPv4组播报文的地址在 IPv4组播路由表中进行查找， 如果在 IPv4组播 路由表中找到匹配的接口地址，则 mAFTR将 IPv4组播报文翻译成 IPv6组 播才艮文， 并通过 IPv6组播分布树将该 IPv6组播才艮文发送到 mB4;
所述 mAFTR将 IPv4组播报文翻译成 IPv6组播报文 ,一般是新建 IPv6 组播报文，将该 IPv6组播报文报头中的所有字段基于所述 IPv4组播报文报 头填写， 报文内容不变， 具体为： 所述 mAFTR新建 IPv6组播报文， 将该 IPv6组播报文报头中的 Version字段置为 6; Traffic Class字段值置为与 IPv4 组播报文中的 TOS相同； Flow Label 字段值置为 0; Playload Length字段 值为 IPv4组播报文减去 IPv4头的长度值； Next Header的值从 IPv4组播报 文报头中的 protocol字段获得； Hop Limit字段的值与 IPv4组播报文中的 TTL字段值相同； Source Address字段的值从 IPv4组播报文的源地址获得； Destination Address字段的值从 IPv4组播报文的目的地址获得、 忽略 IPv4 组播报文中的 IPv4选项字段； 该 IPv6组播报文中的内容与 IPv4组播报文 中的内容相同。 所述 Source Address字段的值从 IPv4组播报文的源地址获得， 一般是 mAFTR根据配置的单播前缀（uPrefix, unicast Prefix ) 以及利用无状态映 射算法， 将 IPv4组播报文的源地址映射到 IPv6组播报文的源地址。
所述 Destination Address字段的值从 IPv4组播 4艮文的目的地址获得， 一般是 mAFTR根据配置的组播前缀（ mPrefix64 , multicast Prefix )利用无 状态映射算法，将 IPv4组播报文的组播地址映射到 IPv6组播报文的组播地 址。
进一步的，本步驟还包括：若在 IPv4组播报文的负载中存在 TCP、 UDP 和 ICMP的校验和 ( checksum ), 则根据映射得到的 IPv6组播报文的源和组 播地址重新计算校验和。
本步驟中， 所述 uPrefix和 mPrefix64的配置方法， 结合图 3所示， 包 括：
( 1 ) CPE和 mAFTR向动态主机配置协议 6 ( DHCPv6 )服务器发送 DHCPv6请求报文， 请求获取 uPrefix和 mPrefix64;
( 2 ) DHCPv6服务器收到所述 DHCPv6请求才艮文后， 将 mPrefix64
( ff00:abc::/96 )和 uPrefix ( 2001 :db8::/96 ) 附带在 DHCPv6应答报文的选 项中发送到 CPE和 mAFTR;
( 3 ) CPE和 mAFTR收到 DHCPv6应答报文后，记录选项中的 uPrefix 和 mPrefix64, 完成配置。
当然， 上述 CPE和 mAFTR的 uPrefix和 mPrefix64的配置也可以通过 其他方法配置， 比如直接通过管理员手动给 CPE和 mAFTR配置， 但必须 保证给 CPE和 mAFTR所配置的前缀必须相同； 这里， 所述 CPE上一般有 mB4 , 即给 CPE配置的 uPrefix和 mPrefix64也同时配置在 mB4上。
在 CPE和 mAFTR获得前缀后，所述将 IPv4组播报文的源地址映射到 IPv6组播 4艮文的源地址和将 IPv4组播 ^艮文的组播地址映射到 IPv6组播报 文的组播地址， 其具体映射过程如图 4所示：
在图 4 中， IPv4 组播报文的组播地址 （ 230.1.2.3 ) 与 mPrefix64 ( ff00:abc::/96 )映射到 IPv6组播报文的组播地址（ ff00:abc::230.1.2.3 ), IPv4 组播 4艮文的源地址（192.1.2.3 ) 与 uPrefix ( 2001:db8::/96 ) 映射到 IPv6组 播报文的源地址（ 2001:db8:: 192.1.2.3 )。
下面用实例一和二对本步驟中所述 IPv6组播分布树的建立进行详细描 述。
实例一：如图 5所示， mAFTR位于 MLD Querier/ΡΙΜνό指定路由器（ DR Designated Router ) 时， 如果部署指定信源组播 （SSM , Source-Specific Multicast )模式， 假设 IPv4组播源为 S ( 192.1.2.3 ), IPv4接收者 A要接受 S的组播报文时， 需要加入相应的 IPv4组播组， IPv6组播分布树的建立的 具体步驟如下：
( 1 ) IPv4接收者 A发送 IGMP报告报文给 CPE1 , 在 IGMP报告报文 中指示需要加入 IPv4组播组的地址 G ( 230.1.2.3 );
( 2 )位于 CPE1上的 mB4接收到所述 IGMP报文后，根据预先配置的 mPrefix64 和 uPrefix 以及无状态映射算法生成 IPv4 组播组的地址 G ( 230.1.2.3 )相对应的 IPv6组播组地址 G， ( ff00:abc::230.1.2.3 ),即：将 IPv4 组播组的地址 G映射到 IPv6组播组地址 G， ( ff00:abc: :230.1.2.3 )、 IPv4源
S映射到 IPv6源 S，( 2001 :db8::192.1.2.3 ),之后 mB4发送 MLD 4艮文到 MLD Querier/PIMv6 DR , 在所述 MLD 报文中 包含 IPv6 组播组地址
G'(ff00:abc::230.1.2.3);
( 3 )mAFTR对 MLD中的 IPv6组播组地址 G，检验通过后 ,生成 PIMv4 加入（ Join )报文，所述 PIMv4 Join报文包含 IPv4接收者 A想要加入的 IPv4 组播组的地址 G ( 230.1.2.3 );
具体的， 由于 mAFTR位于 MLD Querier/ΡΙΜνό DR上， 当 mAFTR收 到这个 MLD报文后， 根据所述 IPv6组播组地址 G，检查相应的记录并将接 收到这个 MLD报文的端口加入到 Out-Interface-List中， 如果没有相应的记 录， mAFTR生成与这个 IPv6组播组地址 G，对应的新的记录。 mAFTR检验 MLD报文中的 IPv6组播组地址 G， ( ff00:abc: :230.1.2.3 )的前缀是否属于配 置的 mPrefix64 , 如果检验通过， 那么 mAFTR 从 IPv6 组播组 G， ( ff00:abc::230.1.2.3 ) 中映射出相应的 IPv4组播组的地址 G ( 230.1.2.3 ), 并检验相对应的 IPv4组播路由表，将隧道接口添加到 Out-Interface-List中， mAFTR还生成一个 PIMv4 Join报文， 所述 PIMv4 Join报文包含想要加入 的 IPv4组播组的地址 G ( 230.1.2.3 )。
( 4 ) mAFTR将 PIMv4 Join报文发送到 RP ( Rendezvous Point )或者
IPv4组播源。
这样， 一条 IPv6组播分布树就已经建立， IPv4组播源的组播报文可以 通过这个组播分布树发送数据到 IPv4接收者 A。
实例二： 如图 6所示， mAFTR位于更上游的 PIMv6路由器中， 如果部 署 SSM模式， 假设 IPv4组播源为 S ( 192.1.2.3 )。 IPv4接收者 A要接受 S 的组播数据时， 需要加入相应的 IPv4组播组， IPv6组播分布树的建立的具 体步驟如下：
( 1 ) IPv4接收者 A发送 IGMP报告报文给 mB4, 在 IGMP报告报文 中指示需要加入 IPv4组播组的地址 G ( 230.1.2.3 );
( 2 )位于 CPE1上的 mB4接受到所述 IGMP报告报文后，根据预先配 置的 mPrefix64和 uPrefix以及无状态映射算法生成 IPv4组播组的地址 G ( 230.1.2.3 )相对应的 IPv6组播组地址 G， ( ff00:abc::230.1.2.3 ),即：将 IPv4 组播组的地址 G映射到 IPv6组播组地址 G， ( ff00:abc: :230.1.2.3 )、 IPv4源 S映射到 IPv6源 S，( 2001 :db8::192.1.2.3 ),之后 mB4发送 MLD 4艮文到 MLD Querier/PIMv6 DR , 在所述 MLD 报文中 包含 IPv6 组播组地址 G'(ff00:abc::230.1.2.3);
( 3 ) PIM DR收到所述报文 MLD报文后 , 经过 MLD Querier 的处理 生成 PIMv6 Join报文， 在 PIMv6 Join报文中包含 IPv6组播组地址 G， ( ff00:abc::230.1.2.3 ), PIM DR将生成的 PIMv6 Join才艮文发送到 mAFTR;
( 4 ) mAFTR对所述 PIMv6 Join报文中的 IPv6组播组地址 G，检验通 过后， 生成 PIMv4 Join报文， 所述 PIMv4 Join报文包含 IPv4接收者 A想 要加入的 IPv4组播组的地址 G ( 230.1.2.3 );
具体的， mAFTR收到所述 PIMv6 Join报文后， 根据所述 PIMv6 Join 报文中的 IPv6组播组地址 G， ( ff00:abc: :230.1.2.3 )检查相应的记录并将接 收到所述 PIMv6 Join报文的端口加入到 Out-Interface-List中， 如果没有相 应的记录， mAFTR生成与 IPv6组播组地址 G，对应的新的记录，之后 mAFTR 检验 PIMv6 Join报文中的 IPv6组播组地址 G， ( ff00:abc::230.1.2.3 )的前缀 是否属于配置的 mPrefix64 ( ff00:abc::/96 ), 如果检险通过， 那么 mAFTR 从 IPv6组播组地址 G， ( ff00:abc: :230.1.2.3 )中映射出相应的 IPv4组播组的 地址 G ( 230.1.2.3 ) , 并检险相对应的 IPv4组播路由表， 将隧道接口添加到 Out-Interface-List中， mAFTR还生成一个 PIMv4 Join报文，所述 PIMv4 Join 报文包含想要加入的 IPv4组播组的地址 G ( 230.1.2.3 )。
( 5 ) mAFTR将 PIMv4 Join报文发送到 RP或者 IPv4组播源。
这样， 一条 IPv6组播分布树就已经建立， IPv4组播源的组播报文可以 通过这个组播分布树发送数据到 IPv4接收者 A。
步驟 102: 当 mB4接收到该 IPv6组播才艮文时， 将该 IPv6组播才艮文翻 译成 IPv4组播报文， 并将该 IPv4组播报文组播到下游的组播接收者；
具体的， 当 mB4收到 IPv6组播报文后， 检验该 IPv6组播报文的组播 地址是否与配置的 mPrefix64匹配、 源地址是否与配置的 uPrefix匹配， 在 均匹配时， mB4将该 IPv6组播报文翻译成 IPv4组播报文， 并根据该 IPv4 组播报文中的组播成员信息将该 IPv4组播报文组播到下游的组播接收者； 所述 mB4将该 IPv6组播报文翻译成 IPv4组播报文， 一般是新建 IPv4 组播报文，将该 IPv4组播报文报头中的所有字段基于所述 IPv6组播报文报 头填写， 报文内容不变， 具体为： 所述 mB4新建 IPv4组播报文， 将该 IPv4 组播报文报头中的 Version 字段置为 4; Internet Header Length值置为 5; TOS值置为 IPv6组播报文中的 Traffic Class的值； Total Length值置为 IPv6 组播报文中 playload值加上 IPv4头长度的值； Identification、 Flags、 Fragment Off字段值都置为 0; Time to Live字段的值为 IPv6组播报文中的 Hop Limit 字段的值； Source Address字段的值为 IPv6组播报文中的源地址映射到 IPv4 组播报文的源地址； Destination Address字段的值为 IPv6组播报文中的组播 地址映射到 IPv4组播报文中的组播地址；该 IPv4组播报文中的内容与 IPv6 组播报文中的内容相同。
为了实现上述方法， 本发明还提供一种 DS-lite网络架构承载组播业务 的系统， 该系统包括： mAFTR、 mB4; 其中，
所述 mAFTR, 用于接收到组播源发送的 IPv4组播报文时， 将该 IPv4 组播报文翻译成相应的 IPv6组播报文， 并将该 IPv6组播报文发送到 mB4; 所述 mB4, 用于接收到该 IPv6组播报文时， 将该 IPv6组播报文翻译 成相应的 IPv4组播报文， 并将该 IPv4组播报文组播到下游的组播接收者； 所述 mAFTR, 具体用于接收到组播源发送的 IPv4组播报文时， 新建 IPv6组播报文， 将该 IPv6组播报文报头中的所有字段基于所述 IPv4组播 报文报头填写， 报文内容不变；
具体的 ,所述 mAFTR接收到组播源发送的 IPv4组播报文时，新建 IPv6 组播报文， 将该 IPv6组播报文报头中的 Version字段置为 6; Traffic Class 字段值置为与 IPv4组播报文中的 TOS相同； Flow Label字段值置为 0; Playload Length字段值为 IPv4组播 4艮文减去 IP头的长度值； Next Header 的值从 IPv4组播报文报头中的 protocol获得； Hop Limit的值与 IPv4组播 报文中的 TTL值相同； Source Address字段的值从 IPv4组播报文的源地址 获得； Destination Address字段的值从 IPv4组播报文的目的地址获得、 忽略 IPv4组播报文中的 IPv4选项字段； 该 IPv6组播报文中的内容与 IPv4组播 报文中的内容相同；
所述 mB4,具体用于接收到 mAFTR发送的 IPv6组播报文时 ,新建 IPv4 组播报文，将该 IPv4组播报文报头中的所有字段基于所述 IPv6组播报文报 头填写， 报文内容不变；
具体的 , 所述 mB4接收到 mAFTR发送的 IPv6组播报文时，新建 IPv4 组播报文，将该 IPv4组播报文报头中的 Version字段置为 4; Internet Header Length值置为 5; TOS值置为 IPv6组播报文中的 Traffic Class的值； Total Length 值置为 IPv6 组播报文中 playload 值加上 IPv4 头长度的值； Identification, Flags、 Fragment Off字段值都置为 0; Time to Live字段的值 为 IPv6组播报文中的 Hop Limit字段的值； Source Address字段的值为 IPv6 组播报文中的源地址映射到 IPv4组播报文的源地址； Destination Address 字段的值为 IPv6组播报文中的组播地址映射到 IPv4组播报文中的组播地 址。
所述 mAFTR, 具体用于通过 IPv6组播分布树将所述 IPv6组播艮文发 送到 mB4o
进一步的， 所述 mAFTR, 还用于接收到 IPv4组播 4艮文为注册 4艮文时， 解封装所述注册报文后得到 IPv4组播报文。
基于上述系统， 本发明还实现一种 DS-lite网络架构承载组播业务的网 络节点 , 该网络节点包括 mAFTR , 所述 mAFTR接收到组播源发送的 IPv4 组播报文时， 将所述 IPv4组播报文翻译成 IPv6组播报文， 并将所述 IPv6 组播 4艮文发送到 mB4; 所述 mAFTR, 具体用于接收到组播源发送的 IPv4组播 ^艮文时， 新建 IPv6组播报文， 将该 IPv6组播报文报头中的所有字段基于所述 IPv4组播 报文报头填写， 报文内容不变；
具体的 ,所述 mAFTR接收到组播源发送的 IPv4组播报文时 ,新建 IPv6 组播报文， 将该 IPv6组播报文报头中的 Version字段置为 6; Traffic Class 字段值置为与 IPv4组播报文中的 TOS相同； Flow Label字段值置为 0; Playload Length字段值为 IPv4组播 4艮文减去 IP头的长度值； Next Header 的值从 IPv4组播报文报头中的 protocol获得； Hop Limit的值与 IPv4组播 报文中的 TTL值相同； Source Address字段的值从 IPv4组播报文的源地址 获得； Destination Address字段的值从 IPv4组播才艮文的目的地址获得、 忽略 IPv4组播报文中的 IPv4选项字段； 该 IPv6组播报文中的内容与 IPv4组播 报文中的内容相同。 实施例一：
本实施例如图 7所示， SSM模式中， IPv4 network中的主机^ 192.1.2.3 ) 要通过 IPv6网络向 IPv4接收者 A所在的 IPv4组播组发送 IPv4组播报文， 则实现 DS-lite网络架构承载组播业务的方法， 如图 8所示， 该方法包括以 下几个步驟：
步驟 201: 主机 B生成 IPv4组播艮文， 并将该 IPv4组播艮文发送到 mAFTR, 其中源地址为主机 B的地址 S ( 192.1.2.3 ), 目的地址为 IPv4组 播组的地址 G ( 230.1.2.3 );
步驟 202: 当 mAFTR接收到所述 IPv4组播才艮文后， 将该 IPv4组播报 文翻译成 IPv6组播艮文， 并通过 IPv6组播分布树将该 IPv6组播 文发送 到 mB4;
具体的， 当 mAFTR接收到所述 IPv4组播报文后， mAFTR根据 IPv4 组播报文的地址在 IPv4组播路由表中进行查找，如果在 IPv4组播路由表中 找到匹配的接口地址 , 则 mAFTR将 IPv4组播报文翻译成相应的 IPv6组播 报文， 并通过 IPv6组播分布树将该 IPv6组播报文发送到 mB4;
所述 mAFTR将 IPv4组播 4艮文翻译成相应的 IPv6组播报文， 具体为： 所述 mAFTR新建 IPv6组播报文， 将该 IPv6组播报文报头中的 Version字 段置为 6; Traffic Class字段的值置为与 IPv4组播报文中的 TOS相同； Flow Label 字段值置为 0; Playload Length字段值置为 IPv4组播报文减去去 IP 头的长度值； Next Header的值从 IPv4组播报文报头中的 protocol获得； Hop Limit的值与 IPv4组播报文中的 TTL值相同； Source Address的值为根据配 置的 uPrefix前缀以及利用无状态映射算法， 将 IPv4组播报文的源地址 S ( 192.1.2.3 ) 映射到 IPv6 组播报文的源地址 S， ( 2001:db8::192.1.2.3 ); Destination Address字段的值为根据配置的 mPrefix64利用无状态映射算法， 将 IPv4 组播 ^艮文的组播地址映射到 IPv6 组播 ^艮文的组播地址 G， ( ff00:abc::230.1.2.3 ); 忽略 IPv4组播报文中的 IPv4选项字段； 该 IPv6组 播报文中的内容与 IPv4组播报文中的内容相同。
步驟 203: 当 mB4收到该 IPv6组播报文时， 将该 IPv6组播报文翻译 成 IPv4组播报文， 并将该 IPv4组播报文组播到下游的 IPv4接收者 A; 具体的， 当 mB4收到 IPv6组播报文后， 检验该 IPv6组播报文的组播 地址 G， ( ff00:abc: :230.1.2.3 )是否与配置的 mPrefix64 ( ff00:abc::/96 )匹配、 源地址 S， ( 2001:db8::192.1.2.3 )是否与配置的 uPrefix ( 2001:db8::/96 ) 匹 配， 在均匹配时， mB4将该 IPv6组播报文翻译成 IPv4组播报文， 并根据 该 IPv4组播报文中的组播成员信息将该 IPv4组播报文组播到下游的 IPv4 接收者 A;
所述 mB4将该 IPv6组播报文翻译成 IPv4组播报文，具体为：所述 mB4 新建 IPv4组播报文，将该 IPv4组播报文报头中的 Version字段置为 4; Internet Header Length值置为 5; Type Of Service值置为 IPv6组播报文中的 Traffic Class的值； Total Length值置为 IPv6组播报文中 playload加上 IPv4头长度 的值； Identification, Flags、 Fragment Off字段值都置为 0; Time to Live字 段的值 0为 IPv6组播报文中的 Hop Limit字段的值； Source Address的值为 IPv6组播报文中的源地址 S， ( 2001:db8::192.1.2.3 )映射到 IPv4组播报文中 的源地址 S ( 192.1.2.3 ); Destination Address的值为 IPv6组播报文中的组播 地址 G， ( ff00:abc::230.1.2.3 ) 映射到 IPv4 组播报文中的组播地址 G ( 230.1.2.3 )。
实施例二：
本实施例如图 9所示， ASM中， IPv4 network中的某一主机 B( 192.1.2.3 ) 要通过 IPv6网络向 IPv4接收者 A所在的 IPv4组播组发送 IPv4组播报文， 则实现 DS-lite网络架构承载组播业务的方法，如图 10所示，该方法包括以 下几个步驟：
步驟 301 : 主机 B生成 IPv4组播报文， 并将该 IPv4组播报文发送到主 机 B所在的 DR, DR将该 IPv4组播报文发送到 mAFTR, 其中源地址为主 机 B的地址 S ( 192.1.2.3 ), 目的地址为 IPv4组播组的地址 G ( 230.1.2.3 ); 这里， 如果主机 B是第一次向外组播， 那么 DR封装该 IPv4组播报文 为注册报文， 并且发送给作为 RP的 mAFTR; 如果已经存在从 RP到 DR 所在的 SPT,那么 DR则把该 IPv4组播报文直接发送给作为 RP的 mAFTR。
步驟 302: 当 mAFTR接收到所述 IPv4组播报文后， 将该 IPv4组播报 文翻译成 IPv6组播艮文， 并通过 IPv6组播分布树将该 IPv6组播 文发送 到 mB4;
具体的， 当 mAFTR接收到所述 IPv4组播报文后， 如果所述 IPv4组播 报文为注册报文， 那么 mAFTR解封装注册报文后得到 IPv4组播报文， 并 向主机 B发送加入 ^艮文； 如果 mAFTR收到为封装的 IPv4组播报文， 那么 mAFTR则向主机 B所在的 DR发送注册停止报文（ Register-Stop Message ); mAFTR根据 IPv4组播报文的地址在 IPv4组播路由表中进行查找， 如果在 IPv4组播路由表中找到匹配的接口地址， 则 mAFTR将 IPv4组播报文翻译 成 IPv6组播 4艮文，并通过 IPv6组播分布树将该 IPv6组播 4艮文发送到 mB4; 所述 mAFTR将 IPv4组播报文翻译成 IPv6组播报文的方法与步驟 202 类似， 这里不再赘述。
步驟 303: 当 mB4收到该 IPv6组播报文时， 将该 IPv6组播报文翻译 成 IPv4组播报文， 并将该 IPv4组播报文组播到下游的 IPv4接收者 A; 这里， 所述 mB4将该 IPv6组播报文翻译成 IPv4组播报文的方法与步 驟 203类似， 这里不再赘述。
综上所述，本发明的方案通过 mAFTR和 mB4对组播 4艮文进行 IPv4与 IPv6的转换， 能够将 IPv4组播报文完全转化为 IPv6组播报文在 IPv6网络 中传送， 提高 IPv4组播报文在 IPv6网络中的传送效率， 最大的利用 IPv6 网络的组播能力。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种轻量级双协议栈（DS-lite ) 网络架构承载组播业务的方法， 其 特征在于， 该方法包括：
当组播地址族翻译路由器（ mAFTR )接收到组播源发送的 IPv4组播报 文时， 将所述 IPv4组播报文翻译成 IPv6组播报文， 并将所述 IPv6组播报 文发送到 mB4;
当 mB4接收到所述 IPv6组播报文时，将所述 IPv6组播报文翻译成 IPv4 组播艮文， 并将所述 IPv4组播艮文组播到组播接收者。
2、 根据权利要求 1所述的方法， 其特征在于， 所述 mAFTR将 IPv4组 播报文翻译成 IPv6组播报文为： 新建 IPv6组播报文， 将所述 IPv6组播报 文报头中的所有字段基于所述 IPv4组播报文报头填写， 报文内容不变。
3、 根据权利要求 1所述的方法， 其特征在于， 所述 mAFTR将 IPv4组 播报文翻译成 IPv6组播报文为：
所述 mAFTR新建 IPv6组播报文，将新建的 IPv6组播报文报头中的版 本（ Version ) 字段置为 6; 传输种类 （ Traffic Class )字段值置为与 IPv4组 播报文中的服务类型 （ TOS )相同； 流量标签（ Flow Label )字段值置为 0; 有效荷载长度（ Playload Length )字段值为 IPv4组播报文的完整长度（ Total Length )值减去 IPv4头的长度值； 下一个报头 （ Next Header ) 的值从 IPv4 组播报文报头中的协议 ( protocol )字段获得； 跳数限制 （Hop Limit )字段 的值与 IPv4组播报文中的生存时间 （TTL )字段值相同； 源地址（Source Address )字段的值从 IPv4组播 4艮文的源地址获得； 目的地址（ Destination Address )字段的值从 IPv4组播 4艮文的目的地址获得； 所述 IPv6组播 4艮文 中的内容与 IPv4组播报文中的内容相同。
4、 根据权利要求 1所述的方法， 其特征在于， 所述 mB4将所述 IPv6 组播报文翻译成 IPv4组播报文为： 新建 IPv4组播报文， 将所述 IPv4组播 报文报头中的所有字段基于所述 IPv6组播报文报头填写， 报文内容不变。
5、 根据权利要求 1所述的方法， 其特征在于， 所述 mB4将所述 IPv6 组播报文翻译成 IPv4组播报文为：
所述 mB4新建 IPv4组播报文， 将所述 IPv4组播报文报头中的 Version 字段置为 4; 互联网头文件长度（Internet Header Length )值置为 5; TOS 值置为 IPv6组播报文中的 Traffic Class的值； Total Length值置为 IPv6组播 报文中 playload值力口上 IPv4头长度的值； Identification, Flags, Fragment Off 字段值都置为 0; TTL字段的值为 IPv6组播报文中的 Hop Limit字段的值； Source Address字段的值为 IPv6组播报文中的源地址映射到 IPv4组播报文 的源地址； Destination Address字段的值为 IPv6组播报文中的组播地址映射 到 IPv4组播报文中的组播地址； 所述 IPv4组播报文中的内容与 IPv6组播 报文中的内容相同。
6、 根据权利要求 1至 5任一项所述的方法， 其特征在于， 该方法进一 步包括： 在任意信源组播（ASM )模式中， mAFTR接收到 IPv4组播报文 为注册报文时， mAFTR解封装注册报文后得到 IPv4组播报文。
7、一种 DS-lite网络架构承载组播业务的系统， 其特征在于， 该系统包 括： mAFTR, mB4; 其中，
所述 mAFTR,用于接收到组播源发送的 IPv4组播 4艮文时，将所述 IPv4 组播报文翻译成 IPv6组播报文， 并将所述 IPv6组播报文发送到 mB4; 所述 mB4, 用于接收到所述 IPv6组播 4艮文时， 将所述 IPv6组播 4艮文 翻译成 IPv4组播报文， 并将所述 IPv4组播报文组播到组播接收者。
8、 根据权利要求 7所述的系统， 其特征在于， 所述 mAFTR, 具体用 于接收到组播源发送的 IPv4组播报文时， 新建 IPv6组播报文， 将该 IPv6 组播报文报头中的所有字段基于所述 IPv4组播报文报头填写， 报文内容不 变。
9、 根据权利要求 7所述的系统， 其特征在于， 所述 mB4, 具体用于接 收到 mAFTR发送的 IPv6组播报文时， 新建 IPv4组播报文， 将该 IPv4组 播报文报头中的所有字段基于所述 IPv6组播报文报头填写，报文内容不变。
10、 一种 DS-lite网络承载组播业务的网络节点， 其特征在于， 所述网 络节点包括 mAFTR, 所述 mAFTR接收到组播源发送的 IPv4组播 4艮文时 , 将所述 IPv4组播报文翻译成 IPv6组播报文， 并将所述 IPv6组播报文发送 到 mB4。
PCT/CN2012/074551 2011-05-09 2012-04-23 Ds-lite网络架构承载组播业务的方法、系统和网络节点 WO2012152180A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110118636.2 2011-05-09
CN2011101186362A CN102780567A (zh) 2011-05-09 2011-05-09 一种DS-lite网络架构承载组播业务的方法、系统和网络节点

Publications (1)

Publication Number Publication Date
WO2012152180A1 true WO2012152180A1 (zh) 2012-11-15

Family

ID=47125333

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/074551 WO2012152180A1 (zh) 2011-05-09 2012-04-23 Ds-lite网络架构承载组播业务的方法、系统和网络节点

Country Status (2)

Country Link
CN (1) CN102780567A (zh)
WO (1) WO2012152180A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105306227A (zh) * 2014-06-16 2016-02-03 中兴通讯股份有限公司 家庭网关DS-Lite组播方法及设备
CN107547376B (zh) * 2017-07-21 2020-07-07 新华三技术有限公司 路由探测方法和装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1897575A (zh) * 2000-04-03 2007-01-17 株式会社日立制作所 多址传送通信方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101771605B (zh) * 2008-12-30 2012-11-28 华为技术有限公司 基于轻量级双栈的业务流管理方法、装置及系统

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1897575A (zh) * 2000-04-03 2007-01-17 株式会社日立制作所 多址传送通信方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Q. WANG ET AL.: "Multicast Extensions to DS-Lite Technique in Broadband Deployments", IETF INTERNET-DRAFT DRAFT-QIN-SOFTWIRE-DSLITE-MULTICAST-03.TXT, 14 March 2011 (2011-03-14), Retrieved from the Internet <URL:http://tools.ietf.org/id/draft-qin-softwire-dslite-multicast-03.txt> *

Also Published As

Publication number Publication date
CN102780567A (zh) 2012-11-14

Similar Documents

Publication Publication Date Title
US6907037B2 (en) Multicast routing method and an apparatus for routing a multicast packet
US7483439B2 (en) VPN services using address translation over an IPv6 network
US8054766B2 (en) Method and tool for IP multicast network address translation (MNAT)
EP1737164A1 (en) A method for realizing multicasting in a virtual private network using a virtual router
WO2010075771A1 (zh) 一种组播虚拟私有网络的外联网组网方法、系统和装置
WO2018214809A1 (zh) 消息发送方法及装置、存储介质
JP2004531143A (ja) 仮想マルチキャストネットワーク方法及びそのシステム
US9036633B2 (en) Multicast support for internet protocol version four residual deployment via encapsulation or translation
WO2008131634A1 (fr) Procédé et appareil permettant d&#39;envoyer et de recevoir des paquets multidiffusion
WO2018171396A1 (zh) 一种数据传输方法、装置及系统
WO2014082414A1 (zh) 业务转发的方法及设备
WO2022021818A1 (zh) 数据报文的处理方法及装置、存储介质、电子装置
WO2007079632A1 (fr) PROCÉDÉ DE DISPOSITION DE MULTIDIFFUSION, PROCÉDÉ DE MULTIDIFFUSION ET APPAREIL DANS LES ÎLOTS IPv6
US9356801B2 (en) Apparatus and method for establishing connections with a plurality of virtual networks
WO2019075674A1 (zh) 传输组播报文的方法、网络设备和系统
WO2012152180A1 (zh) Ds-lite网络架构承载组播业务的方法、系统和网络节点
WO2008154796A1 (fr) Procédé et équipement permettant de commander la transmission de paquets de données de multidiffusion dans la station de base et la passerelle du système wimax
Rosen et al. Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs
KR20120011803A (ko) 이동 통신 시스템에서 이동 노드에 대한 멀티캐스트 서비스 제공 방법 및 장치
CN103222246A (zh) 互联网协议版本IPv6组播地址生成的方法和装置
CN103095585B (zh) 一种IPv4和IPv6之间组播控制流信息互通的方法和系统
WO2023082377A1 (zh) 阶层式6LoWPAN网状网络的数据传送方法
WO2024001221A1 (zh) 一种组播信息转发方法、装置、组播信息汇聚节点及介质
Jeon et al. Transmission of IP over Ethernet over IEEE 802.16 Networks
WO2022205908A1 (zh) 组播信令传递方法和系统

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: 12781604

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12781604

Country of ref document: EP

Kind code of ref document: A1