CN102780567A - Multicast service bearing method and system for DS-lite network architecture as well as network node - Google Patents
Multicast service bearing method and system for DS-lite network architecture as well as network node Download PDFInfo
- Publication number
- CN102780567A CN102780567A CN2011101186362A CN201110118636A CN102780567A CN 102780567 A CN102780567 A CN 102780567A CN 2011101186362 A CN2011101186362 A CN 2011101186362A CN 201110118636 A CN201110118636 A CN 201110118636A CN 102780567 A CN102780567 A CN 102780567A
- Authority
- CN
- China
- Prior art keywords
- multicast message
- ipv4
- ipv6
- message
- multicast
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
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
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a multicast service bearing method for a DS-lite network architecture. The method comprises the following steps that when receiving an IPv4 (Internet Protocol version 4) multicast message sent by a multicast source, an mAFTR (multicast Address Family Translation Router) translates the IPv4 multicast message into an IPv6 (Internet Protocol version 6) multicast message and sends the IPv6 multicast message to an mB4; and when receiving the IPv6 multicast message, the mB4 translates the IPv6 multicast message into the IPv4 multicast message and multicasts the IPv4 multicast message to a downstream multicast receiver. The invention simultaneously discloses a multicast service bearing system for the DS-lite network architecture as well as a network node. By utilizing the scheme adopted by the invention, the IPv4 multicast message can be completely translated into the IPv6 multicast message so as to be transmitted in an IPv6 network, the transmission efficiency of the IPv4 multicast message in the IPv6 network can be improved, and the multicasting capability of the IPv6 network can be maximally utilized.
Description
Technical field
The present invention relates to the multicasting technology of network service, relate in particular to a kind of lightweight dual stack (DS-lite, Dual-Stack-lite) method of network architecture bearing multicast service, system and network node.
Background technology
At IPv4 in the evolution of IPv6; A lot of business remain the IPv4 form, and the renewal that a lot of client device can't be very fast or be upgraded to IPv6, so IPv4 and IPv6 will coexist a very long time; In this section evolution time; When advancing IPv6 to serve, need to guarantee that the IPv4 service needs not interrupted, the DS-lite network architecture is a good solution.But professional like Web TV (IPTV) etc. more existing, exists the demand of multicast, and the application that the present stage DS-lite network architecture has only covered unicast services.
Draft-qin-softwire-delite-multicast has realized adopting the DS-lite network architecture to carry out the demand of 4-6-4 multicast; Its network topological diagram is as shown in Figure 1; Wherein mB4 (Multicast Basic BridgingBroadBand element) module is one of two basic function module in the DS-lite network architecture multicast; Generally be positioned at client device (CPE); Be mainly used in Internet igmpinternet (IGMP; Internet GroupManagement Protocol) dresses up corresponding IPv4 multicast message to the conversion of multicast listener discovery protocol (MLD, Multicast Listener Discover) and with IPv4-in-IPv6 multicast message deblocking, and send to suitable IPv4 multicast recipient; Translation route (the mAFTR of multicast address family; Multicast AddressFamily Transition Router element) be the another one functional module; The IPv4 multicast message that is mainly used in the IPv4 multicast source is packaged into corresponding IPv4-in-IPv6 multicast message, and in the suitable IPv6 multicast distribution tree of IPv6 Access Network, sends.
After the foundation of IPv6 multicast distribution tree finished, the IPv4 multicast source sent the IPv4 multicast message and arrives mAFTR; After mAFTR receives this IPv4 multicast message; MAFTR searches in the IPv4 multicast routing table according to the address of IPv4 multicast message; If in the IPv4 multicast routing table, find the address of Interface Matching, mAFTR encapsulates this IPv4 multicast message so, in encapsulation process, uses the prefix that disposes to mAFTR in advance; Utilize the stateless mapping algorithm; With the IPv4 map addresses in the IPv4 multicast message to corresponding IPv4-embedded IPv6 address, and with these IPv4-embedded IPv6 addresses as source address and multicast address, the IPv4 multicast message is encapsulated as the IPv4-in-IPv6 multicast message; Wherein, In the IPv4-in-IPv6 multicast message, mAFTR does not do any NAT conversion to the source address and the destination address of the IPv4 multicast message received, and mAFTR sends to corresponding mB4 with the IPv4-in-IPv6 multicast message along IPv6 multicast distribution tree; When mB4 receives the IPv4-in-IPv6 multicast message; The multicast address that mB4 at first checks the IPv4-in-IPv6 multicast message whether in pre-assigned mPrefix scope and source address whether in the uPrefix scope of distributing, if do not exist, then can abandon this IPv4-in-IPv6 multicast message; If all exist; This IPv4-in-IPv6 multicast message of decapsulation then, thus original IPv4 multicast message obtained, and this message is multicast to the IPv4 multicast recipient in downstream.
Above-mentioned draft-qin-softwire-dslite-multicast has mainly described when network is 4-6-4; Multicast situation when using the Ds-lite network architecture as transition scheme; Wherein, use the tunneling technique of IPv4-in-IPv6 to send the IPv4 multicast message, though can alleviate the burden of mAFTR and can utilize the multicast-capable of IPv6 network through the IPv6 network; But; This scheme just arrives corresponding IPv4-embedded IPv6 address with the IPv4 map addresses in the IPv4 multicast message, only is equivalent on the IPv4 multicast message, increase the heading that is used in the transmission of IPv6 network, and the IPv4 multicast message is still the IPv4 form; Be unfavorable for the transmission efficiency of this IPv4 multicast message in the IPv6 network like this, can not the maximum multicast-capable of utilizing the IPv6 network.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of method, system and network node of DS-lite network architecture bearing multicast service, improves the transmission efficiency of IPv4 multicast message in the IPv6 network, the maximum multicast-capable of utilizing the IPv6 network.
For achieving the above object, technical scheme of the present invention is achieved in that
The method of a kind of DS-lite network architecture bearing multicast service provided by the invention, this method comprises:
When mAFTR receives the IPv4 multicast message of multicast source transmission, said IPv4 multicast message is translated into the IPv6 multicast message, and said IPv6 multicast message is sent to mB4;
When mB4 receives said IPv6 multicast message, said IPv6 multicast message is translated into the IPv4 multicast message, and said IPv4 multicast message is multicast to the multicast recipient in downstream.
In the such scheme, said mAFTR translates into the IPv6 multicast message with the IPv4 multicast message and is: newly-built IPv6 multicast message, all fields in the said IPv6 multicast message header to be filled in based on said IPv4 multicast message header, and message content is constant.
In the such scheme, said mAFTR translates into the IPv6 multicast message with the IPv4 multicast message and is: the newly-built IPv6 multicast message of said mAFTR is changed to 6 with version (Version) field in the newly-built IPv6 multicast message header; Transmission kind (Traffic Class) field value be changed to the IPv4 multicast message in COS (TOS, Type Of Service) identical; Flow label (Flow Label) field value is changed to 0; Useful load length (Playload Length) field value is that complete length (Total Length) value of IPv4 multicast message deducts the length value of IPv4 head; Agreement (protocol) field of the value of next header (Next Header) from IPv4 multicast message header obtains; The value of jumping limit (Hop Limit) field and the life span in the IPv4 multicast message (TTL, Time to Live) field value is identical; The value of source address (Source Address) field obtains from the source address of IPv4 multicast message; The value of destination address (Destination Address) field obtains from the destination address of IPv4 multicast message; Content in the said IPv6 multicast message is identical with content in the IPv4 multicast message.
In the such scheme, said mB4 translates into the IPv4 multicast message with said IPv6 multicast message and is: newly-built IPv4 multicast message, all fields in the said IPv4 multicast message header to be filled in based on said IPv6 multicast message header, and message content is constant.
In the such scheme, said mB4 translates into the IPv4 multicast message with said IPv6 multicast message and is: the newly-built IPv4 multicast message of said mB4 is changed to 4 with the Version field in the said IPv4 multicast message header; The Internet header file length (Internet Header Length) value is changed to 5; The TOS value is changed to the value of the Traffic Class in the IPv6 multicast message; Total Length value is changed to the value that playload value in the IPv6 multicast message adds IPv4 head length degree; Identification, Flags, Fragment Off field value all are changed to 0; The value of ttl field is the value of the Hop Limit field in the IPv6 multicast message; The value of Source Address field is the source address that the source address in the IPv6 multicast message is mapped to the IPv4 multicast message; The value of Destination Address field is that the multicast address in the IPv6 multicast message is mapped to the multicast address in the IPv4 multicast message; Content in the said IPv4 multicast message is identical with content in the IPv6 multicast message.
In the such scheme, this method further comprises: (ASM, Any-SourceMulticast) in the pattern, mAFTR receives the IPv4 multicast message when being logon message, obtains the IPv4 multicast message behind the mAFTR decapsulation logon message in any-source multicast.
The system of a kind of DS-lite network architecture bearing multicast service provided by the invention, this system comprises: mAFTR, mB4; Wherein,
Said mAFTR when being used to receive the IPv4 multicast message of multicast source transmission, translating into the IPv6 multicast message with said IPv4 multicast message, and said IPv6 multicast message is sent to mB4;
Said mB4 when being used to receive said IPv6 multicast message, translating into the IPv4 multicast message with said IPv6 multicast message, and said IPv4 multicast message is multicast to the multicast recipient in downstream.
In the such scheme, said mAFTR, when specifically being used to receive the IPv4 multicast message of multicast source transmission, newly-built IPv6 multicast message is filled in all fields in this IPv6 multicast message header based on said IPv4 multicast message header, and message content is constant.
In the such scheme, said mB4, when specifically being used to receive the IPv6 multicast message of mAFTR transmission, newly-built IPv4 multicast message is filled in all fields in this IPv4 multicast message header based on said IPv6 multicast message header, and message content is constant.
The network node of a kind of DS-lite network carrying multicast service provided by the invention; Said network node comprises mAFTR; When said mAFTR receives the IPv4 multicast message of multicast source transmission; Said IPv4 multicast message is translated into the IPv6 multicast message, and said IPv6 multicast message is sent to mB4.
The invention provides a kind of method, system and network node of DS-lite network architecture bearing multicast service; When mAFTR receives the IPv4 multicast message of multicast source transmission; This IPv4 multicast message is translated into the IPv6 multicast message, and this IPv6 multicast message is sent to mB4; When mB4 receives this IPv6 multicast message, this IPv6 multicast message is translated into the IPv4 multicast message, and this IPv4 multicast message is multicast to the multicast recipient in downstream; So, can the IPv4 multicast message be converted into the IPv6 multicast message fully and in the IPv6 network, transmit, improve the transmission efficiency of IPv4 multicast message in the IPv6 network, the maximum multicast-capable of utilizing the IPv6 network.
Description of drawings
Fig. 1 is a DS-lite multicast network topology sketch map in the prior art;
Fig. 2 realizes a kind of schematic flow sheet of method of DS-lite network architecture bearing multicast service for the present invention;
Fig. 3 disposes the network architecture sketch map of uPrefix and mPrefix64 for the present invention;
Fig. 4 is a map addresses sketch map of the present invention;
Fig. 5 is the network architecture sketch map of the foundation of IPv6 multicast distribution tree in the instance one of the present invention;
Fig. 6 is the network architecture sketch map of the foundation of IPv6 multicast distribution tree in the instance two of the present invention;
Fig. 7 is the network architecture sketch map of SSM pattern of the present invention;
Fig. 8 realizes the schematic flow sheet of the method for DS-lite network architecture bearing multicast service in the SSM pattern for the present invention;
Fig. 9 is the network architecture sketch map of ASM pattern of the present invention;
Figure 10 realizes the schematic flow sheet of the method for DS-lite network architecture bearing multicast service in the ASM pattern for the present invention.
Embodiment
Basic thought of the present invention is: when mAFTR receives the IPv4 multicast message of multicast source transmission, this IPv4 multicast message is translated into the IPv6 multicast message, and this IPv6 multicast message is sent to mB4; When mB4 receives this IPv6 multicast message, this IPv6 multicast message is translated into the IPv4 multicast message, and this IPv4 multicast message is multicast to the multicast recipient in downstream.
Through accompanying drawing and specific embodiment the present invention is done further detailed description below.
The present invention realizes a kind of method of DS-lite network architecture bearing multicast service, and is as shown in Figure 2, and this method comprises following step:
Step 101: when mAFTR receives the IPv4 multicast message of multicast source transmission, this IPv4 multicast message is translated into the IPv6 multicast message, and this IPv6 multicast message is sent to mB4;
Concrete; When mAFTR receives the IPv4 multicast message of multicast source transmission; MAFTR searches in the IPv4 multicast routing table according to the address of IPv4 multicast message; If in the IPv4 multicast routing table, find the interface IP address of coupling, then mAFTR translates into the IPv6 multicast message with the IPv4 multicast message, and through IPv6 multicast distribution tree this IPv6 multicast message is sent to mB4;
Said mAFTR translates into the IPv6 multicast message with the IPv4 multicast message; It generally is newly-built IPv6 multicast message; All fields in this IPv6 multicast message header are filled in based on said IPv4 multicast message header; Message content is constant, is specially: the newly-built IPv6 multicast message of said mAFTR is changed to 6 with the Version field in this IPv6 multicast message header; Traffic Class field value be changed to the IPv4 multicast message in TOS identical; Flow Label field value is changed to 0; Playload Length field value deducts the length value of IPv4 head for the IPv4 multicast message; The protocol field of the value of Next Header from IPv4 multicast message header obtains; Ttl field value in the value of Hop Limit field and the IPv4 multicast message is identical; The value of SourceAddress field obtains from the source address of IPv4 multicast message; The value of Destination Address field obtains, ignores the IPv4 Option Field the IPv4 multicast message from the destination address of IPv4 multicast message; Content in this IPv6 multicast message is identical with content in the IPv4 multicast message.
The value of said Source Address field obtains from the source address of IPv4 multicast message; Generally be the clean culture prefix (uPrefix of mAFTR according to configuration; Unicast Prefix) and utilize the stateless mapping algorithm, the source address of IPv4 multicast message is mapped to the source address of IPv6 multicast message.
The value of said Destination Address field obtains from the destination address of IPv4 multicast message; Generally be the multicast prefix (mPrefix64 of mAFTR according to configuration; Multicast Prefix) utilizes the stateless mapping algorithm, the multicast address of IPv4 multicast message is mapped to the multicast address of IPv6 multicast message.
Further, this step also comprises: if in the load of IPv4 multicast message, there is the verification of TCP, UDP and ICMP and (checksum), the source of the IPv6 multicast message that then obtains according to mapping and multicast address recomputate verification and.
In this step, the collocation method of said uPrefix and mPrefix64 in conjunction with shown in Figure 3, comprising:
(1) CPE and mAFTR send DHCPv6 request message, acquisition request uPrefix and mPrefix64 to DHCP 6 (DHCPv6) server;
/ 96) and uPrefix (2001:db8: :/96) attach and in the option of DHCPv6 response message, send to CPE and mAFTR (2) after the DHCPv6 server is received said DHCPv6 request message, with mPrefix64 (ff00:abc::;
(3) after CPE and mAFTR received the DHCPv6 response message, uPrefix and mPrefix64 in the record option accomplished configuration.
Certainly, the uPrefix of above-mentioned CPE and mAFTR and the configuration of mPrefix64 also can be passed through the additive method configuration, give CPE and mAFTR configuration such as directly passing through administrator hand, but it are necessary identical with the prefix that mAFTR is disposed to ensure to CPE; Here, mB4 is arranged generally on the said CPE, promptly uPrefix and the mPrefix64 to the CPE configuration also is configured on the mB4 simultaneously.
After CPE and mAFTR obtained prefix, said source address with the IPv4 multicast message was mapped to the source address of IPv6 multicast message and the multicast address of IPv4 multicast message is mapped to the multicast address of IPv6 multicast message, and its concrete mapping process is as shown in Figure 4:
In Fig. 4; The multicast address of IPv4 multicast message (230.1.2.3) and mPrefix64 (ff00:abc: :/96) be mapped to the multicast address (ff00:abc::230.1.2.3) of IPv6 multicast message, the source address of IPv4 multicast message (192.1.2.3) and uPrefix (2001:db8: :/96) be mapped to the source address (2001:db8::192.1.2.3) of IPv6 multicast message.
Foundation with IPv6 multicast distribution tree described in the instance one and two pairs of these steps is described in detail below.
Instance one: as shown in Figure 5; When mAFTR is positioned at MLD Querier/PIMv6 Designated Router (DRDesignated Router), if dispose source-specific multicast (SSM, Source-Specific Multicast) pattern; Suppose that the IPv4 multicast source is S (192.1.2.3); When IPv4 recipient A will accept the multicast message of S, need to add corresponding IPv4 multicast group, the concrete steps of the foundation of IPv6 multicast distribution tree are following:
(1) IPv4 recipient A sends the IGMP report message and gives CPE1, and indication needs to add the address G (230.1.2.3) of IPv4 multicast group in the IGMP report message;
(2) be positioned at mB4 on the CPE1 and receive said IGMP message after; The corresponding IPv6 multicast group address of address G (230.1.2.3) G ' that generates the IPv4 multicast group according to pre-configured mPrefix64 and uPrefix and stateless mapping algorithm (ff00:abc::230.1.2.3); That is: with the address G of IPv4 multicast group be mapped to IPv6 multicast group address G ' (ff00:abc::230.1.2.3), IPv4 source S is mapped to IPv6 source S ' (2001:db8::192.1.2.3); MB4 sends the MLD message to MLD Querier/PIMv6DR afterwards, in said MLD message, comprises IPv6 multicast group address G ' (ff00:abc::230.1.2.3);
(3) after mAFTR upchecks to the IPv6 multicast group address G ' among the MLD, generate the PIMv4Join message, said PIMv4Join message comprises the address G (230.1.2.3) of the IPv4 multicast group that IPv4 recipient A wants to add;
Concrete; Because mAFTR is positioned on the MLD Querier/PIMv6DR; After mAFTR receives this MLD message; Join among the Out-Interface-List according to the corresponding port that writes down and will receive this MLD message of said IPv6 multicast group address G ' inspection, if there is not corresponding record, mAFTR generates and the corresponding new record of this IPv6 multicast group address G '.Whether the IPv6 multicast group address G ' prefix (ff00:abc::230.1.2.3) in the mAFTR check MLD message belongs to the mPrefix64 of configuration; If upcheck; MAFTR shines upon the address G (230.1.2.3) of corresponding IPv4 multicast group (ff00:abc::230.1.2.3) from IPv6 multicast group G ' so; And check corresponding IPv4 multicast routing table; Tunnel interface is added among the Out-Interface-List, and mAFTR also generates a PIMv4Join message, and said PIMv4Join message comprises the address G (230.1.2.3) of the IPv4 multicast group of wanting to add.
(4) mAFTR sends to RP (Rendezvous Point) or IPv4 multicast source with the PIMv4Join message.
Like this, an IPv6 multicast distribution tree is just set up, and the multicast message of IPv4 multicast source can send data to IPv4 recipient A through this multicast distribution tree.
Instance two: as shown in Figure 6, mAFTR is arranged in the more PIMv6 router at the upper reaches, if dispose the SSM pattern, supposes that the IPv4 multicast source is S (192.1.2.3).When IPv4 recipient A will accept the multicast packet of S, need to add corresponding IPv4 multicast group, the concrete steps of the foundation of IPv6 multicast distribution tree are following:
(1) IPv4 recipient A sends the IGMP report message and gives mB4, and indication needs to add the address G (230.1.2.3) of IPv4 multicast group in the IGMP report message;
(2) be positioned at mB4 on the CPE1 and receive said IGMP report message after; The corresponding IPv6 multicast group address of address G (230.1.2.3) G ' that generates the IPv4 multicast group according to pre-configured mPrefix64 and uPrefix and stateless mapping algorithm (ff00:abc::230.1.2.3); That is: with the address G of IPv4 multicast group be mapped to IPv6 multicast group address G ' (ff00:abc::230.1.2.3), IPv4 source S is mapped to IPv6 source S ' (2001:db8::192.1.2.3); MB4 sends the MLD message to MLDQuerier/PIMv6DR afterwards, in said MLD message, comprises IPv6 multicast group address G ' (ff00:abc::230.1.2.3);
(3) after PIM DR receives said message MLD message; Processing through MLD Querier generates the PIMv6Join message; In the PIMv6Join message, comprise IPv6 multicast group address G ' (ff00:abc::230.1.2.3), PIM DR sends to mAFTR with the PIMv6Join message that generates;
(4) after mAFTR upchecks to the IPv6 multicast group address G ' in the said PIMv6Join message, generate the PIMv4Join message, said PIMv4Join message comprises the address G (230.1.2.3) of the IPv4 multicast group that IPv4 recipient A wants to add;
Concrete; After mAFTR receives said PIMv6Join message; (ff00:abc::230.1.2.3) check that the corresponding port that writes down and will receive said PIMv6Join message joins among the Out-Interface-List according to the IPv6 multicast group address G ' in the said PIMv6Join message; If there is not corresponding record; MAFTR generates the new record corresponding with IPv6 multicast group address G '; Whether the IPv6 multicast group address G ' prefix (ff00:abc::230.1.2.3) in the mAFTR check PIMv6Join message belongs to the mPrefix64 of configuration (ff00:abc: :/96), if upcheck, mAFTR shines upon the address G (230.1.2.3) of corresponding IPv4 multicast group (ff00:abc::230.1.2.3) from IPv6 multicast group address G ' so afterwards; And check corresponding IPv4 multicast routing table; Tunnel interface is added among the Out-Interface-List, and mAFTR also generates a PIMv4Join message, and said PIMv4Join message comprises the address G (230.1.2.3) of the IPv4 multicast group of wanting to add.
(4) mAFTR sends to RP or IPv4 multicast source with the PIMv4Join message.
Like this, an IPv6 multicast distribution tree is just set up, and the multicast message of IPv4 multicast source can send data to IPv4 recipient A through this multicast distribution tree.
Step 102: when mB4 receives this IPv6 multicast message, this IPv6 multicast message is translated into the IPv4 multicast message, and this IPv4 multicast message is multicast to the multicast recipient in downstream;
Concrete; After mB4 receives the IPv6 multicast message; Check the multicast address of this IPv6 multicast message whether whether to mate with the uPrefix that disposes with mPrefix64 coupling, the source address of configuration; When all mating, mB4 translates into the IPv4 multicast message with this IPv6 multicast message, and this IPv4 multicast message is multicast to the multicast recipient in downstream according to the multicast member information in this IPv4 multicast message;
Said mB4 translates into the IPv4 multicast message with this IPv6 multicast message; It generally is newly-built IPv4 multicast message; All fields in this IPv4 multicast message header are filled in based on said IPv6 multicast message header; Message content is constant, is specially: the newly-built IPv4 multicast message of said mB4 is changed to 4 with the Version field in this IPv4 multicast message header; Internet Header Length value is changed to 5; The TOS value is changed to the value of the Traffic Class in the IPv6 multicast message; Total Length value is changed to the value that playload value in the IPv6 multicast message adds IPv4 head length degree; Identification, Flags, Fragment Off field value all are changed to 0; The value of Time to Live field is the value of the Hop Limit field in the IPv6 multicast message; The value of SourceAddress field is the source address that the source address in the IPv6 multicast message is mapped to the IPv4 multicast message; The value of Destination Address field is that the multicast address in the IPv6 multicast message is mapped to the multicast address in the IPv4 multicast message; Content in this IPv4 multicast message is identical with content in the IPv6 multicast message.
In order to realize said method, the present invention also provides a kind of system of DS-lite network architecture bearing multicast service, and this system comprises: mAFTR, mB4; Wherein,
Said mAFTR when being used to receive the IPv4 multicast message of multicast source transmission, translating into corresponding IPv6 multicast message with this IPv4 multicast message, and this IPv6 multicast message is sent to mB4;
Said mB4 when being used to receive this IPv6 multicast message, translates into corresponding IPv4 multicast message with this IPv6 multicast message, and this IPv4 multicast message is multicast to the multicast recipient in downstream;
Said mAFTR, when specifically being used to receive the IPv4 multicast message of multicast source transmission, newly-built IPv6 multicast message is filled in all fields in this IPv6 multicast message header based on said IPv4 multicast message header, and message content is constant;
Concrete, when said mAFTR received the IPv4 multicast message of multicast source transmission, newly-built IPv6 multicast message was changed to 6 with the Version field in this IPv6 multicast message header; Traffic Class field value be changed to the IPv4 multicast message in TOS identical; Flow Label field value is changed to 0; The PlayloadLength field value deducts the length value of IP head for the IPv4 multicast message; The protocol of the value of Next Header from IPv4 multicast message header obtains; The value of Hop Limit is identical with ttl value in the IPv4 multicast message; The value of Source Address field obtains from the source address of IPv4 multicast message; The value of DestinationAddress field obtains, ignores the IPv4 Option Field the IPv4 multicast message from the destination address of IPv4 multicast message; Content in this IPv6 multicast message is identical with content in the IPv4 multicast message;
Said mB4, when specifically being used to receive the IPv6 multicast message of mAFTR transmission, newly-built IPv4 multicast message is filled in all fields in this IPv4 multicast message header based on said IPv6 multicast message header, and message content is constant;
Concrete, when said mB4 received the IPv6 multicast message of mAFTR transmission, newly-built IPv4 multicast message was changed to 4 with the Version field in this IPv4 multicast message header; Internet Header Length value is changed to 5; The TOS value is changed to the value of the Traffic Class in the IPv6 multicast message; Total Length value is changed to the value that playload value in the IPv6 multicast message adds IPv4 head length degree; Identification, Flags, Fragment Off field value all are changed to 0; The value of Time to Live field is the value of the HopLimit field in the IPv6 multicast message; The value of Source Address field is the source address that the source address in the IPv6 multicast message is mapped to the IPv4 multicast message; The value of Destination Address field is that the multicast address in the IPv6 multicast message is mapped to the multicast address in the IPv4 multicast message.
Said mAFTR specifically is used for through IPv6 multicast distribution tree said IPv6 multicast message being sent to mB4.
Further, said mAFTR when also being used to receive the IPv4 multicast message and being logon message, obtains the IPv4 multicast message behind the said logon message of decapsulation.
Based on said system; The present invention also realizes a kind of network node of DS-lite network architecture bearing multicast service; This network node comprises mAFTR; When said mAFTR receives the IPv4 multicast message of multicast source transmission, said IPv4 multicast message is translated into the IPv6 multicast message, and said IPv6 multicast message is sent to mB4;
Said mAFTR, when specifically being used to receive the IPv4 multicast message of multicast source transmission, newly-built IPv6 multicast message is filled in all fields in this IPv6 multicast message header based on said IPv4 multicast message header, and message content is constant;
Concrete, when said mAFTR received the IPv4 multicast message of multicast source transmission, newly-built IPv6 multicast message was changed to 6 with the Version field in this IPv6 multicast message header; Traffic Class field value be changed to the IPv4 multicast message in TOS identical; Flow Label field value is changed to 0; The PlayloadLength field value deducts the length value of IP head for the IPv4 multicast message; The protocol of the value of Next Header from IPv4 multicast message header obtains; The value of Hop Limit is identical with ttl value in the IPv4 multicast message; The value of Source Address field obtains from the source address of IPv4 multicast message; The value of DestinationAddress field obtains, ignores the IPv4 Option Field the IPv4 multicast message from the destination address of IPv4 multicast message; Content in this IPv6 multicast message is identical with content in the IPv4 multicast message.
Specify the implementation procedure and the principle of method of the present invention below in conjunction with specific embodiment.
Embodiment one:
Present embodiment is as shown in Figure 7; In the SSM pattern; Host B among the IPv4network (192.1.2.3) will send the IPv4 multicast message to the IPv4 multicast group at IPv4 recipient A place through the IPv6 network; Then realize the method for DS-lite network architecture bearing multicast service, as shown in Figure 8, this method comprises following step:
Step 201: host B generates the IPv4 multicast message, and this IPv4 multicast message is sent to mAFTR, and wherein source address is the address S (192.1.2.3) of host B, and destination address is the address G (230.1.2.3) of IPv4 multicast group;
Step 202: after mAFTR receives said IPv4 multicast message, this IPv4 multicast message is translated into the IPv6 multicast message, and this IPv6 multicast message is sent to mB4 through IPv6 multicast distribution tree;
Concrete; After mAFTR receives said IPv4 multicast message; MAFTR searches in the IPv4 multicast routing table according to the address of IPv4 multicast message; If in the IPv4 multicast routing table, find the interface IP address of coupling, then mAFTR translates into corresponding IPv6 multicast message with the IPv4 multicast message, and through IPv6 multicast distribution tree this IPv6 multicast message is sent to mB4;
Said mAFTR translates into corresponding IPv6 multicast message with the IPv4 multicast message, is specially: the newly-built IPv6 multicast message of said mAFTR is changed to 6 with the Version field in this IPv6 multicast message header; The value of Traffic Class field be changed to the IPv4 multicast message in TOS identical; Flow Label field value is changed to 0; Playload Length field value is changed to the length value that the IPv4 multicast message deducts the IP head; The protocol of the value of Next Header from IPv4 multicast message header obtains; The value of Hop Limit is identical with ttl value in the IPv4 multicast message; The value of Source Address is for according to the uPrefix prefix of configuration and utilize the stateless mapping algorithm, and the source address S ' that the source address S (192.1.2.3) of IPv4 multicast message is mapped to the IPv6 multicast message (2001:db8::192.1.2.3); The value of Destination Address field is utilized the stateless mapping algorithm for the mPrefix64 according to configuration, and the multicast address G ' that the multicast address of IPv4 multicast message is mapped to the IPv6 multicast message (ff00:abc::230.1.2.3); Ignore the IPv4 Option Field in the IPv4 multicast message; Content in this IPv6 multicast message is identical with content in the IPv4 multicast message.
Step 203: when mB4 receives this IPv6 multicast message, this IPv6 multicast message is translated into the IPv4 multicast message, and this IPv4 multicast message is multicast to the IPv4 recipient A in downstream;
Concrete; After mB4 receives the IPv6 multicast message; The multicast address G ' that checks this IPv6 multicast message (ff00:abc::230.1.2.3) whether with the mPrefix64 of configuration (ff00:abc: :/96) coupling, source address S ' (2001:db8::192.1.2.3) whether with the uPrefix (2001:db8: :/96) coupling of configuration; When all mating; MB4 translates into the IPv4 multicast message with this IPv6 multicast message, and this IPv4 multicast message is multicast to the IPv4 recipient A in downstream according to the multicast member information in this IPv4 multicast message;
Said mB4 translates into the IPv4 multicast message with this IPv6 multicast message, is specially: the newly-built IPv4 multicast message of said mB4 is changed to 4 with the Version field in this IPv4 multicast message header; InternetHeader Length value is changed to 5; Type Of Service value is changed to the value of the Traffic Class in the IPv6 multicast message; Total Length value is changed to the value that playload in the IPv6 multicast message adds IPv4 head length degree; Identification, Flags, Fragment Off field value all are changed to 0; The value 0 of Time to Live field is the value of the Hop Limit field in the IPv6 multicast message; The value of Source Address is that the source address S ' in the IPv6 multicast message (2001:db8::192.1.2.3) is mapped to source address S (192.1.2.3) in the IPv4 multicast message; The value of Destination Address is that the multicast address G ' in the IPv6 multicast message (ff00:abc::230.1.2.3) is mapped to multicast address G (230.1.2.3) in the IPv4 multicast message.
Embodiment two:
Present embodiment is as shown in Figure 9; Among the ASM; A certain host B (192.1.2.3) among the IPv4network will send the IPv4 multicast message to the IPv4 multicast group at IPv4 recipient A place through the IPv6 network; Then realize the method for DS-lite network architecture bearing multicast service, shown in figure 10, this method comprises following step:
Step 301: host B generates the IPv4 multicast message; And this IPv4 multicast message sent to the DR at host B place; DR sends to mAFTR with this IPv4 multicast message, and wherein source address is the address S (192.1.2.3) of host B, and destination address is the address G (230.1.2.3) of IPv4 multicast group;
Here, if host B is for the first time outside multicast, this IPv4 multicast message of DR encapsulation is a logon message so, and sends to the mAFTR as RP; If there has been the SPT at place from RP to DR, DR then directly sends to the mAFTR as RP to this IPv4 multicast message so.
Step 302: after mAFTR receives said IPv4 multicast message, this IPv4 multicast message is translated into the IPv6 multicast message, and this IPv6 multicast message is sent to mB4 through IPv6 multicast distribution tree;
Concrete, after mAFTR receives said IPv4 multicast message,, obtain the IPv4 multicast message behind the mAFTR decapsulation logon message so, and join message to the host B transmission if said IPv4 multicast message is a logon message; If mAFTR receives the IPv4 multicast message into encapsulation, mAFTR then sends stopped registration messages (Register-Stop Message) to the DR at host B place so; MAFTR searches in the IPv4 multicast routing table according to the address of IPv4 multicast message; If in the IPv4 multicast routing table, find the interface IP address of coupling; Then mAFTR translates into the IPv6 multicast message with the IPv4 multicast message, and through IPv6 multicast distribution tree this IPv6 multicast message is sent to mB4;
Method and step 202 that said mAFTR translates into the IPv6 multicast message with the IPv4 multicast message are similar, repeat no more here.
Step 303: when mB4 receives this IPv6 multicast message, this IPv6 multicast message is translated into the IPv4 multicast message, and this IPv4 multicast message is multicast to the IPv4 recipient A in downstream;
Here, method and step 203 that said mB4 translates into the IPv4 multicast message with this IPv6 multicast message are similar, repeat no more here.
The above is merely preferred embodiment of the present invention, is not to be used to limit protection scope of the present invention.
Claims (10)
1. the method for a lightweight dual stack (DS-lite) network architecture bearing multicast service is characterized in that this method comprises:
When multicast address family translation route (mAFTR) receives the IPv4 multicast message of multicast source transmission, said IPv4 multicast message is translated into the IPv6 multicast message, and said IPv6 multicast message is sent to mB4;
When mB4 receives said IPv6 multicast message, said IPv6 multicast message is translated into the IPv4 multicast message, and said IPv4 multicast message is multicast to the multicast recipient in downstream.
2. method according to claim 1; It is characterized in that; Said mAFTR translates into the IPv6 multicast message with the IPv4 multicast message: newly-built IPv6 multicast message, all fields in the said IPv6 multicast message header to be filled in based on said IPv4 multicast message header, and message content is constant.
3. method according to claim 1; It is characterized in that; Said mAFTR translates into the IPv6 multicast message with the IPv4 multicast message: the newly-built IPv6 multicast message of said mAFTR is changed to 6 with version (Version) field in the newly-built IPv6 multicast message header; Transmission kind (Traffic Class) field value be changed to the IPv4 multicast message in COS (TOS) identical; Flow label (Flow Label) field value is changed to 0; Useful load length (Playload Length) field value is that complete length (Total Length) value of IPv4 multicast message deducts the length value of IPv4 head; Agreement (protocol) field of the value of next header (Next Header) from IPv4 multicast message header obtains; The value of jumping limit (Hop Limit) field is identical with life span (TTL) field value in the IPv4 multicast message; The value of source address (SourceAddress) field obtains from the source address of IPv4 multicast message; The value of destination address (DestinationAddress) field obtains from the destination address of IPv4 multicast message; Content in the said IPv6 multicast message is identical with content in the IPv4 multicast message.
4. method according to claim 1; It is characterized in that; Said mB4 translates into the IPv4 multicast message with said IPv6 multicast message: newly-built IPv4 multicast message, all fields in the said IPv4 multicast message header to be filled in based on said IPv6 multicast message header, and message content is constant.
5. method according to claim 1 is characterized in that, said mB4 translates into the IPv4 multicast message with said IPv6 multicast message and is: the newly-built IPv4 multicast message of said mB4 is changed to 4 with the Version field in the said IPv4 multicast message header; The Internet header file length (Internet HeaderLength) value is changed to 5; The TOS value is changed to the value of the Traffic Class in the IPv6 multicast message; Total Length value is changed to the value that playload value in the IPv6 multicast message adds IPv4 head length degree; Identification, Flags, Fragment Off field value all are changed to 0; The value of ttl field is the value of the Hop Limit field in the IPv6 multicast message; The value of Source Address field is the source address that the source address in the IPv6 multicast message is mapped to the IPv4 multicast message; The value of Destination Address field is that the multicast address in the IPv6 multicast message is mapped to the multicast address in the IPv4 multicast message; Content in the said IPv4 multicast message is identical with content in the IPv6 multicast message.
6. according to each described method of claim 1 to 5; It is characterized in that; This method further comprises: in any-source multicast (ASM) pattern, mAFTR receives the IPv4 multicast message when being logon message, obtains the IPv4 multicast message behind the mAFTR decapsulation logon message.
7. the system of a DS-lite network architecture bearing multicast service is characterized in that, this system comprises: mAFTR, mB4; Wherein,
Said mAFTR when being used to receive the IPv4 multicast message of multicast source transmission, translating into the IPv6 multicast message with said IPv4 multicast message, and said IPv6 multicast message is sent to mB4;
Said mB4 when being used to receive said IPv6 multicast message, translating into the IPv4 multicast message with said IPv6 multicast message, and said IPv4 multicast message is multicast to the multicast recipient in downstream.
8. system according to claim 7; It is characterized in that; Said mAFTR, when specifically being used to receive the IPv4 multicast message of multicast source transmission, newly-built IPv6 multicast message; All fields in this IPv6 multicast message header are filled in based on said IPv4 multicast message header, and message content is constant.
9. system according to claim 7 is characterized in that, said mB4; When specifically being used to receive the IPv6 multicast message of mAFTR transmission; Newly-built IPv4 multicast message is filled in all fields in this IPv4 multicast message header based on said IPv6 multicast message header, message content is constant.
10. the network node of a DS-lite network carrying multicast service; It is characterized in that; Said network node comprises mAFTR; When said mAFTR receives the IPv4 multicast message of multicast source transmission, said IPv4 multicast message is translated into the IPv6 multicast message, and said IPv6 multicast message is sent to mB4.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011101186362A CN102780567A (en) | 2011-05-09 | 2011-05-09 | Multicast service bearing method and system for DS-lite network architecture as well as network node |
| PCT/CN2012/074551 WO2012152180A1 (en) | 2011-05-09 | 2012-04-23 | Method, system and network node for ds-lite network architecture to bear multicast service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011101186362A CN102780567A (en) | 2011-05-09 | 2011-05-09 | Multicast service bearing method and system for DS-lite network architecture as well as network node |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102780567A true CN102780567A (en) | 2012-11-14 |
Family
ID=47125333
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011101186362A Pending CN102780567A (en) | 2011-05-09 | 2011-05-09 | Multicast service bearing method and system for DS-lite network architecture as well as network node |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102780567A (en) |
| WO (1) | WO2012152180A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3133770A4 (en) * | 2014-06-16 | 2017-09-20 | ZTE Corporation | Home gateway ds-lite multicast method and device |
| CN107547376A (en) * | 2017-07-21 | 2018-01-05 | 新华三技术有限公司 | routing detection method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1270485C (en) * | 2000-04-03 | 2006-08-16 | 株式会社日立制作所 | Multiple access transmission communication method |
| WO2010075735A1 (en) * | 2008-12-30 | 2010-07-08 | 华为技术有限公司 | Service flow managing method, device and system based on ds-lite |
-
2011
- 2011-05-09 CN CN2011101186362A patent/CN102780567A/en active Pending
-
2012
- 2012-04-23 WO PCT/CN2012/074551 patent/WO2012152180A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1270485C (en) * | 2000-04-03 | 2006-08-16 | 株式会社日立制作所 | Multiple access transmission communication method |
| WO2010075735A1 (en) * | 2008-12-30 | 2010-07-08 | 华为技术有限公司 | Service flow managing method, device and system based on ds-lite |
Non-Patent Citations (2)
| Title |
|---|
| Q.WANG等: "《Mulitcast Extensions to DS-Lite Technique in Broadband Deployments》", 14 March 2011 * |
| X.LI等: "《IP/ICMP Translation Algorithm》", 18 September 2010 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3133770A4 (en) * | 2014-06-16 | 2017-09-20 | ZTE Corporation | Home gateway ds-lite multicast method and device |
| CN107547376A (en) * | 2017-07-21 | 2018-01-05 | 新华三技术有限公司 | routing detection method and device |
| CN107547376B (en) * | 2017-07-21 | 2020-07-07 | 新华三技术有限公司 | Route detection method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012152180A1 (en) | 2012-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8774038B2 (en) | Multicast support for dual stack-lite and internet protocol version six rapid deployment on internet protocol version four infrastructures | |
| CN1266913C (en) | Tunneling through access network | |
| US8054766B2 (en) | Method and tool for IP multicast network address translation (MNAT) | |
| US20060209831A1 (en) | VPN services using address translation over an IPv6 network | |
| US8848609B2 (en) | Forwarding internet protocol version 6 link-local multicast to support roaming of wireless mobile client devices | |
| CN1988507B (en) | Method, system and router for repeating multicast data | |
| US9344382B2 (en) | Multicast support for internet protocol version four residual deployment via encapsulation or translation | |
| US20080002727A1 (en) | Packet relay device | |
| WO2015143879A1 (en) | Method for sending multicast packet and switch | |
| CN103227787A (en) | Automatic 4over6 tunnel establishment method based on ARP proxy | |
| CN102780567A (en) | Multicast service bearing method and system for DS-lite network architecture as well as network node | |
| CN103222246B (en) | The method and apparatus that internet protocol version IPv6 multicast address generates | |
| CN105516382A (en) | Communication method and system for IPV4 network and IPV6 Internet of Things (IOT) node | |
| CN103095585B (en) | The method and system of multicast control stream information intercommunication between a kind of IPv4 and IPv6 | |
| Venaas et al. | An IPv4-IPv6 multicast translator | |
| Kovacshazi et al. | Host identity specific multicast | |
| Chmielewski et al. | Application of IP multicast in embedded systems with openWRT | |
| McAuley et al. | Mobile multicast proxy | |
| WO2010056105A2 (en) | A method and system for encapsulating multicast packets into unicast packets | |
| Park et al. | Deployment strategy and performance evaluation of the IPv6 home network using the home server | |
| Li et al. | A home gateway based multicast transit solution and implementation on DS-Lite | |
| CN115314463A (en) | Data transmission method of hierarchical 6LoWPAN mesh network | |
| Boucadair et al. | Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network | |
| CN117097587A (en) | Method and equipment for two-layer interconnection of remote Ethernet | |
| Boucadair et al. | RFC 8114: Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20121114 |
|
| RJ01 | Rejection of invention patent application after publication |