WO2013189346A2

WO2013189346A2 - Multicast address conversion method and device

Info

Publication number: WO2013189346A2
Application number: PCT/CN2013/081651
Authority: WO
Inventors: 曹亚林; 葛崇志; 韩杰
Original assignee: 中兴通讯股份有限公司
Priority date: 2013-01-08
Filing date: 2013-08-16
Publication date: 2013-12-27
Also published as: CN103051744B; WO2013189346A3; CN103051744A

Abstract

A multicast address conversion method and device. The multicast address conversion method comprises: obtaining a conversion rule corresponding to a multicast address to be converted, the conversion rule comprising a multicast address prefix, an IPv4 multicast address type and an IPv4 multicast address offset location; and according to the conversion rule, converting the multicast address to a target multicast address.

Description

Method and device for converting multicast address

Technical field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for converting a multicast address.

Background technique

With the depletion of the IPv4 (Internet Protocol version 4) address pool, it is imperative to transition to an IPv6 network. However, there is still a long time for the existing network to fully transition to the IPv6 network. The coexistence of the IPv4 network and the IPv6 network will exist for a long time. On the other hand, multicast technology is widely used in traditional modes such as IPTV (Internet Protocol Television), video on demand, and video conferencing, as well as emerging modes such as mobile terminal advertising, online stores, and cloud computing. Therefore, how to solve the multicast application problem in the transition network environment becomes very necessary. At present, the parties use the tunnel and translation technologies to solve the multicast problem in the transition scenario. Inevitably, the conversion relationship between the IPv4 multicast address and the IPv6 multicast address needs to be established. For multicast communication, the conversion of multicast addresses between IPv4 and IPv6 becomes the application basis.

The conversion method between the IPv4 multicast address and the IPv6 multicast address in the related art is mainly the conversion method specified in the draft draft-ietf-mboned-64-multicast-address-format. In this method, the ASM (Any Source Multicast) prefix FFXX:8000::/20 and the SSM (Source Specific Multicast) prefix FF3X:0:8000::/96 are defined. The address is used as the last 32 bits of the IPv6 multicast address, and is combined with the defined multicast prefix to perform multicast address translation. This method of multicast address translation is simple and easy to implement, but it has certain disadvantages: Because the IPv6 multicast prefix used is fixed, there is a unified prefix for the ASM multicast address and the SSM multicast address, and the IPv4 address is not distinguished. Scope, so all IPv4 SSM multicast addresses are mapped to the same IPv6 SSM multicast prefix. All IPv4 ASM multicast addresses are mapped to the same IPv6 ASM multicast prefix. Take the ASM multicast address as an example. That is, if a fixed IPv6 ASM prefix is used on the device, all IPv4 ASM multicast addresses are translated into a unified multicast address with an IPv6 ASM multicast prefix. All multicast applications that want to communicate with the IPv4 network must also use the specified multicast prefix. This limits the usage and flexibility of the IPv6 multicast prefix and the IPv4 multicast address space. Also survive The disadvantage is that the IPv6 multicast prefix can be up to 96 bits because at least 32 bits are reserved for IPv4 multicast addresses.

In summary, the multicast address translation method in the related art cannot make good use of the IPv6 multicast address space, and can not more accurately divide the IPv4 multicast address space and the IPv6 multicast address space, and the application is diverse and flexible. There is a lack of sex and safety.

Summary of the invention

The embodiment of the invention provides a method and a device for converting a multicast address, which can better utilize an IPv6 address space to implement conversion between an IPv4 multicast address and an IPv6 multicast address in the network.

An embodiment of the present invention provides a method for converting a multicast address, including:

Obtaining a conversion rule corresponding to the multicast address to be converted, where the conversion rule includes a multicast address prefix, an IPv4 multicast address type, and an IPv4 multicast address offset position;

Converting the multicast address to a target multicast address according to the conversion rule.

Optionally, when the multicast address to be converted is an Internet Protocol version 4 (IPv4) multicast address, the conversion rule includes an Internet Protocol version 6 (IPv6) multicast address prefix and an IPv4 multicast address prefix;

When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv4 multicast address suffix, the step of converting the multicast address to the target multicast address according to the conversion rule includes:

Calculating the IPv4 multicast address suffix according to the IPv4 multicast address prefix and the IPv4 multicast address;

The IPv6 multicast address prefix is placed at the beginning of the IPv6 multicast address, and the IPv4 multicast address suffix is placed at the position indicated by the IPv4 multicast address offset position, and other empty positions are 0, forming a target IPv6 multicast. address.

Optionally, when the conversion rule includes an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indicates that the location parameter is offset from the IPv4 multicast address in the IPv6 multicast address. The latter bit of the defined starting offset position begins to place the IPv4 multicast address suffix; and when the conversion rule does not include an IPv4 multicast address offset location parameter, the IPv4 multicast The address offset location indicates placement of the IPv4 multicast address suffix at the last location of the IPv6 multicast address.

Optionally, when the multicast address to be converted is an IPv4 multicast address, the conversion rule includes an IPv6 multicast address prefix and an IPv4 multicast address prefix.

When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv4 multicast address, the step of converting the multicast address to the target multicast address according to the conversion rule includes:

The IPv6 multicast address prefix is placed at the beginning of the IPv6 multicast address, and the IPv4 multicast address is placed at the location indicated by the IPv4 multicast address offset location, and other empty locations are 0, forming the target IPv6 group. Broadcast address.

Optionally, when the conversion rule includes an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indicates that the location parameter is offset from the IPv4 multicast address in the IPv6 multicast address. The next bit of the defined starting offset position begins to place the IPv4 multicast address;

When the conversion rule does not include an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indicates that the IPv4 multicast address is placed in the last 32 bits of the IPv6 multicast address.

Optionally, when the multicast address to be converted is an IPv6 multicast address, the conversion rule includes an IPv4 multicast address prefix;

Calculating a length of the IPv4 multicast address suffix according to the length of the IPv4 multicast address prefix;

And obtaining, in the IPv6 multicast address, the IPv4 multicast address suffix according to the length of the IPv4 multicast address suffix at a location indicated by the IPv6 multicast address offset location;

The IPv4 multicast address prefix and the IPv4 multicast address suffix are spliced to form a target IPv4 multicast address.

Optionally, when the conversion rule includes an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indicates that the IPv4 multicast address offset bit is in the IPv6 multicast address. The next bit of the starting offset position defined by the parameter starts to acquire the IPv4 multicast address suffix; and when the conversion rule does not include an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location Instructing to obtain the IPv4 multicast address suffix at the last location of the IPv6 multicast address.

When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv4 multicast address, the step of converting the multicast address into a target multicast address according to the conversion rule includes: in the IPv6 group In the broadcast address, a 32-bit address is acquired as the target IPv4 multicast address at the location indicated by the IPv6 multicast address offset position.

Optionally, when the conversion rule includes an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indication is defined in the IPv6 multicast address from the IPv4 multicast address offset location parameter. The next bit of the starting offset position begins to acquire the IPv4 multicast address;

When the conversion rule does not include an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indicates that the IPv4 multicast address is obtained in the last 32 bits of the IPv6 multicast address.

The embodiment of the present invention further provides a device for converting a multicast address that implements the foregoing method, including: an obtaining module, configured to: obtain a conversion rule corresponding to a multicast address to be converted, where the conversion rule includes multicast Address prefix, IPv4 multicast address type, and IPv4 multicast address offset location;

a conversion module, configured to: convert the multicast address to a target multicast address according to the conversion rule.

When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv4 multicast address suffix, the converting module converts the multicast address into a target multicast address according to the conversion rule by:

Calculating the IPv4 multicast according to the IPv4 multicast address prefix and the IPv4 multicast address Address suffix;

Optionally, when the conversion rule includes an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indication is defined in the IPv6 multicast address from the IPv4 multicast address offset location parameter. The next bit of the initial offset position begins to place the IPv4 multicast address suffix; and when the conversion rule does not include an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indication The IPv4 multicast address suffix is placed at the last position of the IPv6 multicast address.

Optionally, when the multicast address to be converted is an IPv4 multicast address, the conversion rule includes an IPv6 multicast address prefix and an IPv4 multicast address prefix;

When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv4 multicast address, the converting module converts the multicast address into a target multicast address according to the conversion rule by:

Optionally, when the conversion rule includes an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indication is defined in the IPv6 multicast address from the IPv4 multicast address offset location parameter. The next bit of the starting offset position begins to place the IPv4 multicast address;

When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv4 multicast address suffix, the converting module converts the multicast address into a target multicast address according to the conversion rule by: Calculating a length of the IPv4 multicast address suffix according to the length of the IPv4 multicast address prefix;

Optionally, when the conversion rule includes an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indication is defined in the IPv6 multicast address from the IPv4 multicast address offset location parameter. The latter bit of the initial offset position begins to acquire the IPv4 multicast address suffix; and when the conversion rule does not include an IPv4 multicast address offset location parameter, the IPv4 multicast address offset location indication The last location of the IPv6 multicast address obtains the IPv4 multicast address suffix.

Optionally, when the multicast address to be converted is an IPv6 multicast address, when the IPv4 multicast address type indicates that the target multicast address is formed based on an IPv4 multicast address, the converting module is configured according to the following manner: The conversion rule converts the multicast address into a target multicast address:

In the IPv6 multicast address, a 32-bit address is obtained as the target IPv4 multicast address at the location indicated by the IPv6 multicast address offset position.

With the above solution of the embodiment of the present invention, each conversion rule is configured with an address prefix, and multiple conversion rules can be set, so that each area or organization within a network can obtain its own address prefix, which can make By maintaining the address translation process within the specified address range, the multicast address range can be divided more finely within the service scope, enhancing service flexibility and security, and facilitating network management. In addition, in the technical solution of the embodiment of the present invention, the support is based on the IPv4 group. The IPv6 multicast address composition method of the broadcast address suffix has no prefix length limitation, and can better utilize the IPv6 multicast address space to implement conversion between the IPv4 multicast address and the IPv6 multicast address in the network. BRIEF abstract

1 is a schematic flowchart of a method for converting a multicast address according to an embodiment of the present invention;

2 is a structural block diagram of a multicast address conversion apparatus according to an embodiment of the present invention;

3 is a schematic diagram of a format of an IPv6 multicast address suffix based on an IPv4 multicast address suffix according to an embodiment of the present invention;

4 is a schematic diagram of an IPv6 multicast address composition format based on an IPv4 multicast address according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of converting an IPv4 multicast address into an IPv6 multicast address according to an embodiment of the present invention;

6 is a schematic flow chart of converting an IPv6 multicast address into an IPv4 multicast address according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a scenario of a device for converting a multicast address according to an embodiment of the present invention; FIG. 8 is a schematic diagram of another scenario of a device for converting a multicast address according to an embodiment of the present invention.

Preferred embodiment of the invention

The embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of non-conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

The embodiments of the present invention are directed to the related art that the multicast address translation method cannot make good use of the IPv6 multicast address space, and can not more accurately divide the IPv4 multicast address space and the IPv6 multicast address space, and the diversity of applications. The problem of insufficient flexibility and security provides a method and device for converting a multicast address, which can better utilize the IPv6 address space to implement conversion between an IPv4 multicast address and an IPv6 multicast address in the network. The conversion method can be implemented by the router.

FIG. 1 is a schematic flowchart of a method for converting a multicast address according to an embodiment of the present invention, as shown in FIG. The embodiment includes the following steps:

Step 101: Obtain a conversion rule corresponding to the multicast address to be converted, where the conversion rule includes a multicast address prefix, an IPv4 multicast address type, and an IPv4 multicast address offset position.

Step 102: Convert the multicast address to a target multicast address according to the conversion rule. In the embodiment of the present invention, one or more conversion rules may be preset, and each conversion rule is defined as follows:

Rule_ipv6_m_prefix ,

Rule_ipv4_m_prefix ,

< rule — ipv4 — offset > ,

< rule— ipv4— type >

Where rule - ipv6 - m_prefix indicates the IPv6 multicast address prefix in the conversion rule, including the mask length; rule - ipv4 - m_prefix indicates the IPv4 multicast address prefix in the conversion rule, including the mask length; such a pair of prefix representations The conversion relationship between an IPv6 multicast address and an IPv4 multicast address.

Rule—ipv4—offset is the IPv4 multicast address offset location parameter, which is an optional parameter in the conversion rule. It is used to indicate the IPv4 multicast address or the offset of the IPv4 multicast address suffix in the IPv6 multicast address. That is, the IPv4 multicast address or the IPv4 multicast address suffix is offset from the start bit in the IPv6 multicast address. If the conversion rule does not include this parameter, it means that an IPv4 multicast address or an IPv4 multicast address suffix is placed in the last digit of the IPv6 multicast address.

Rule—ipv4—type is an IPv4 multicast address type parameter, which is also an optional parameter in the conversion rule. It is used to indicate whether the IPv6 multicast address contains the IPv4 multicast address suffix (ipv4_m_suffix) or the complete IPv4 multicast. The address ( ipv4_m_addr ) can also be understood as an IPv6 multicast address format based on an IPv4 multicast address or an IPv4 multicast address suffix. If the conversion rule does not include this parameter or if the value of rule_ipv4_type is 0, it means that the IPv6 multicast address is based on the IPv4 multicast address suffix. If the value of rule-ipv4_type is 1, it means IPv6 multicast address format of an IPv4 multicast address. In the embodiment of the present invention, two IPv6 multicast address composition formats are defined, one is an IPv6 multicast address composition format based on an IPv4 multicast address suffix, and the other is an IPv6 multicast address composition format based on an IPv4 multicast address. Which format is used by rule-ipv4-type, when rule-ipv4-type is 0, it means that the IPv6 multicast address based on the IPv4 multicast address suffix is used in the format, when rule-ipv4-type is 1 Indicates that the IPv6 multicast address based on the IPv4 multicast address is used in the format. When the conversion rule does not include rule_ipv4_type, the default format is IPv6 multicast address based on the IPv4 multicast address suffix.

In the IPv6 multicast address format based on the suffix of the IPv4 multicast address, the IPv6 multicast address consists of the IPv6 multicast address prefix and the IPv4 multicast address suffix in the conversion rule and the 0 added in the case of a vacancy. The IPv6 multicast address prefix is placed from the start bit of the IPv6 multicast address. The IPv4 multicast address suffix is placed from the last bit of the starting offset defined by the conversion rule. If the conversion rule does not contain rule_ipv4— Offset, the default IPv4 multicast address suffix is placed in the last part of the IPv6 multicast address; the remaining positions are padded with 0.

Where ipv4—m—suffix refers to the remaining part of the IPv4 multicast address to be converted after rule_ipv4_m_prefix is removed, and its length is 32 minus the length of rule—ipv4—m_prefix.

Figure 3 is a schematic diagram of a format of an IPv6 multicast address suffix based on an IPv4 multicast address suffix. As shown in Figure 3, starting from the left end 0 of the IPv6 multicast address, the n-bit rule-ipv6-m_prefix is included, where n is also It indicates the mask length of rule-ipv6-m_prefix; the offset from the 0 position is rule_ipv4_offset, the IPv4 multicast address suffix ipv4_m_suffix, the suffix occupies m bits; the remaining slots are padded with 0s.

Where ipv4_m_suffix is the remaining part after the rule_ipv4_m_prefix is removed from the IPv4 multicast address, and the length of the ipv4_m_suffix is obtained by subtracting the length of the rule_ipv4_m_prefix from the IPv4 address length 32, that is, the m value. The portion other than the determined rule_ipv6_m_prefix and ipv4_m_suffix, that is, the portion occupied by the p-bit and the q-bit in Fig. 3, is padded with 0. Here, the values of p and q can be 0, that is, it means that there is no such space, which is determined by the determined two-scores rule_ipv6_m_prefix and ipv4-m-suffix and the parameter rule-ipv4-offset. Rule—ipv4—offset is an optional parameter. If the parameter is not included in the conversion rule, then ipv4—m—suffix is placed in the last part of the IPv6 multicast address, that is, the part before the 128th bit. q is 0. In this address format, the sum of the length n of the IPv6 multicast address prefix and the length m of the IPv4 multicast address suffix in the conversion rule may not exceed 128, that is, n + m 128. The maximum value of n can be 128. In this case, m is required to be 0. Such a conversion rule means that a certain IPv6 multicast address corresponds to a certain IPv4 multicast address. If the conversion rule contains rule_ipv4_offset, the value of rule_ipv4_offset cannot be greater than 128-m, that is, it must be reserved for ipv4-m-suffix.

In an IPv6 multicast address-based IPv6 multicast address format, an IPv6 multicast address consists of an IPv6 multicast address prefix and a complete IPv4 multicast address and a zero supplement in the case of a vacancy. The IPv6 multicast address prefix is placed from the start bit of the IPv6 multicast address. The complete IPv4 multicast address is placed from the last bit of the start offset defined by the conversion rule. If the conversion rule does not contain rule-ipv4 — offset, by default, the IPv4 multicast address is placed directly in the 32-bit part of the last part of the IPv6 multicast address; the remaining positions are padded with 0.

Figure 4 shows the IPv6 multicast address composition format based on the IPv4 multicast address. As shown in Figure 4, starting from the left end 0 of the IPv6 multicast address, the n-bit rule-ipv6-m_prefix is included, where n also indicates Rule—ipv6—The mask length of m_prefix; offset from the 0 position to rule-ipv4—offset, placing the complete ipv4—m—addr, occupying 32 bits; the rest of the position is padded with 0s.

Wherein, in the determined rule - ipv6 - m_prefix and ipv4_m_addr, the portion occupied by p bits and q bits in Fig. 4 is padded with 0. Here, the values of p and q can be 0, that is, there is no such part of the space, which is determined by the determined two parts rule - ipv6 - m_prefix and ipv4_m_addr and the parameter rule - ipv4 - offset. Rule—ipv4—offset is an optional parameter. If the parameter is not included in the conversion rule, then ipv4—m—addr is placed in the last part of the IPv6 multicast address, occupying 32 bits, and q is 0.

In this address format, the sum of the length n of the IPv6 multicast address prefix and the length 32 of the IPv4 multicast address in the conversion rule may not exceed 128, that is, n + 32 128, that is, n 96. In addition, if rule_ipv4_offset is included, the rule_ipv4_offset value cannot be greater than 128 - 32 = 96, that is, it must be reserved for ip _V 4 - m - addr.

When performing the conversion between multicast addresses, first obtain a set of conversion rules to be used on the device that needs to perform multicast address translation, which may include one or more conversion rules.

In the process of converting an IPv4 multicast address to an IPv6 multicast address, IPv4 that needs to be converted The multicast address is matched with the IPv6 multicast address prefix in the conversion rule. After the longest match is matched to the appropriate IPv6 multicast address prefix, a conversion rule is obtained and the appropriate IPv6 multicast address prefix is obtained. If no suitable IPv6 multicast address prefix is matched, no conversion processing is performed. The IPv6 multicast address type parameter based on the IPv4 multicast address suffix or the IPv4 multicast address is selected according to the optional IPv4 multicast address type parameter in the conversion rule. If the IPv4 multicast address type parameter is not defined in the conversion rule, By default, the IPv6 multicast address suffix based on the IPv4 multicast address suffix is selected. The IPv4 multicast address offset parameter is used to determine the offset of the IPv4 multicast address or IPv4 multicast address suffix in the IPv6 multicast address. Location: If the IPv4 multicast address offset location is not defined in the translation rule, the IPv4 multicast address or IPv4 multicast address suffix is placed in the last position of the IPv6 multicast address by default. Then, the target IPv6 multicast address ( ipv6_m_addr ) is constructed according to the IPv6 multicast address format.

During the process of converting an IPv6 multicast address to an IPv4 multicast address, match the IPv6 multicast address to be translated with the IPv4 multicast address prefix in the conversion rule, and match the appropriate IPv4 multicast according to the longest matching method. After the address prefix, that is, a conversion rule is obtained and the appropriate IPv4 multicast address prefix is obtained. If no suitable IPv4 multicast address prefix is matched, no conversion processing is performed. If the IPv4 multicast address type parameter is not specified in the conversion rule, the IPv4 multicast address type parameter is not specified in the conversion rule. By default, the IPv6 multicast address suffix is configured based on the IPv4 multicast address suffix. The IPv4 multicast address offset position parameter is used to determine the offset position of the IPv4 multicast address or IPv4 multicast address suffix in the IPv6 multicast address. . If the IPv4 multicast address suffix is used, the length of the IPv4 multicast address suffix is calculated according to the length of the IPv4 multicast address prefix in the conversion rule, and then calculated according to the location specified by the IPv4 multicast address offset location parameter. _ιρ ν 4 multicast address suffix length acquired IPv4 multicast address suffix; IPv4 multicast address in case no offset parameter, the IPv6 multicast address acquired directly from the last stage according to the calculated address of the IPv4 multicast group suffix length IPv4 The broadcast suffix, the IPv4 address prefix in the splicing conversion rule, and the obtained IPv4 multicast address suffix, obtain the target IPv4 multicast address. If the IPv6 multicast address is based on the IPv4 multicast address, the complete IPv4 multicast address is obtained directly from the next bit of the offset. If the IPv4 multicast address offset location parameter is not included, the IPv6 group is directly obtained. The last 32 bits of the broadcast address get the full IPv4 multicast address. The embodiment of the present invention further provides a device for converting a multicast address, and the device may be a router. As shown in FIG. 2, the embodiment includes:

The obtaining module 20 is configured to: obtain a conversion rule corresponding to the multicast address to be converted, where the conversion rule includes a multicast address prefix, an IPv4 multicast address type, and an IPv4 multicast address offset position;

The conversion module 21 is configured to: convert the multicast address into a target multicast address according to the conversion rule.

When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv4 multicast address suffix, the converting module 21 converts the multicast address into a target multicast address according to the conversion rule by:

Forming, at the IPv4 multicast address type, the target multicast location based on an IPv4 multicast address At the time of the address, the conversion module 21 converts the multicast address into a target multicast address according to the conversion rule by:

Optionally, when the multicast address to be converted is an IPv6 multicast address, the IPv4 multicast When the address type indicates that the target multicast address is formed based on the IPv4 multicast address, the converting module 21 converts the multicast address into a target multicast address according to the conversion rule by:

The conversion device supports the conversion between the IPv4 multicast address and the IPv6 multicast address, and can obtain an IPv4 multicast address that can be matched to a conversion rule into an IPv6 multicast address after obtaining a defined set of conversion rules. The IPv6 multicast address that can be matched to a conversion rule is converted into an IPv4 multicast address, and the multicast protocol packet and the data packet are forwarded, and the multicast application between the IPv4 network and the IPv6 network is communicated.

The conversion rule defined in the embodiment of the present invention can be matched according to the multicast address prefix, and only the address that can match the multicast address prefix is converted, otherwise the conversion is not performed. In a certain range, you only need to obtain services of certain multicast addresses, so that the corresponding address prefixes of these multicast addresses are configured in a conversion rule, and the multicast addresses that do not want to be served cannot be traversed because they cannot match. The boundaries of IPv4 networks and/or IPv6 networks provide better flexibility and security in the use of devices. In the technical solution of the embodiment of the present invention, multiple conversion rules may be set, so that each area or organization within a network can obtain its own address prefix, and the address conversion process is maintained within a specified address range, so that the service can be served. The division of the multicast address range is finer in the scope, which enhances the flexibility and security of the service and is beneficial to network management.

In addition, in the related art, since the 32-bit of the complete IPv4 multicast address is to be guaranteed, the length of the IPv6 multicast address prefix is up to 96, and the IPv6 multicast address composition method based on the IPv4 address suffix is supported in the embodiment of the present invention. Without the limitation of the prefix length, it can even be extended to 128 bits of the IPv6 limit, which can better utilize the IPv6 multicast address space. Embodiment 1 of the method for converting a multicast address according to an embodiment of the present invention is described below with reference to the accompanying drawings and embodiments.

In this embodiment, the IPv4 multicast address can be translated into an IPv6 multicast address. As shown in FIG. 5, the embodiment includes the following steps:

Step 501: First, a predefined set of conversion rules needs to be obtained, and the set of rules may include one or more conversion rules.

Enter ipv4—m—addr to be converted, and match in the set of conversion rules. You can match according to the principle that the IPv4 group has the longest matching of the address prefixes.

Step 502: If the conversion rule is not matched, the end processing is performed; if a conversion rule is matched, the process proceeds to step 3.

Step 503: Obtain a matching conversion rule, which includes rule_ipv6-m_prefix and other parameters.

Step 504: Determine whether there is a rule-ipv4_type in the conversion rule. If the conversion rule does not include the parameter or the value of the parameter is 0, go to step 5. If the conversion rule includes the parameter and the parameter value is 1, enter the step. 9.

Step 505: Calculate ipv4_m_suffix according to rule-ipv4_m_prefix and the input IPv4 multicast address in the conversion rule, including calculating the length of ipv4_m_suffix.

Step 506: Determine whether the rule_ipv4_offset parameter exists in the conversion rule. If not, go to step 7. If yes, go to step 8.

Step 507: The IPv6 multicast address is in the first place according to rule-ipv6-m_prefix, and ipv4-m-suffix is composed in the last mode, and other slots are filled with 0. To form the target ipv6—m—addr, go to step 12.

Step 508: In the IPv6 multicast address, put rule-ipv6-m_prefix at the forefront, and place ipv4-m_suffix from the last digit of the position specified by rule-ipv4-offset, and the remaining slots are filled with 0. Go to step 12.

Step 509: Determine whether the rule jpv4_offset parameter exists in the conversion rule, if not, proceed to step 10, and if yes, proceed to step 11. Step 510: The IPv6 multicast address is in front of rule-ipv6 m_prefix, and ipv4_m_addr is composed in the last 32-bit mode, and other slots are filled with 0. To form the target ipv6-m-addr, go to step 12.

Step 511: In the IPv6 multicast address, the rule_ipv6_m_prefix is first, and the ipv4_m_addr is placed from the last bit of the position specified by rule-ipv4-offset, and the remaining slots are filled with 0. Go to step 12.

Step 512: Output the conversion result, that is, output the target ipv6_m_addr.

The above process only shows a process of converting from an IPv4 multicast address to an IPv6 multicast address, wherein the order of the optional parameters rule ipv4_type and rule_ipv4_offset can be changed. The above process is to determine the rule-ipv4-type after determining the rule-ipv4-type, or judge the rule-ipv4-type after determining the rule-ipv4-offset to adjust the process, which involves a slightly different step, in the process. The steps performed can also be easily split or merged without affecting the output.

Embodiment 2

In this embodiment, the IPv6 multicast address can be converted into an IPv4 multicast address. As shown in FIG. 6, the embodiment includes the following steps:

Step 601: The precondition is to obtain a predefined set of conversion rules, and the set of rules may include one or more conversion rules.

Enter the ipv6-m-addr to be converted, and match in the conversion rule. You can match according to the principle that the IPv6 address prefix is the longest match.

Step 602: If the conversion rule is not matched, the end processing is performed; if a conversion rule is matched, the process proceeds to step 3.

Step 603: Obtain a matching conversion rule, which includes rule—ipv4—m_prefix and other parameters.

Step 604: Determine whether there is a rule-ipv4_type in the conversion rule. If there is no such parameter in the conversion rule or the value of the parameter is 0, go to step 5. If the parameter exists and the parameter value is 1, go to step 10.

Step 605: Calculate the length of ipv4_m_suffix according to rule_ipv4_m_prefix in the conversion rule. Step 606: Determine whether the rule_ipv4_offset parameter exists in the conversion rule. If not, go to step 7. If yes, go to step 8.

Step 607: Obtain ipv4_m_suffix according to the length of ipv4_m_suffix at the last part of the input IPv6 multicast address, and go to step 9.

Step 608: According to the position specified by rule-ipv4-offset, offset the rule-ipv4-offset bit from the input IPv6 multicast address, and obtain ipv4_m_suffix from the next bit according to the length of ipv4-m_suffix. Go to step 9.

Step 609, splicing rule_ipv4_m_prefix and ipv4_m_suffix to get the J target ipv4_m_addr, and proceed to step 13.

Step 610: Determine whether the rule_ipv4_offset parameter exists in the conversion rule. If not, go to step 11. If yes, go to step 12.

Step 611: Obtain a 32-bit ipv4_m_addr from the last part of the input IPv6 multicast address, and proceed to step 13.

Step 612: According to the position specified by rule-ipv4-offset, offset the rule-ipv4-offset bit from the input IPv6 multicast address, and obtain the 32-bit ipv4_m-addr from the next bit, and proceed to step 13.

Step 613, outputting the conversion result, that is, outputting the target ipv4_m_addr.

The above process only shows a process of converting from an IPv6 multicast address to an IPv4 multicast address, wherein the order of the optional parameters rule ipv4_type and rule_ipv4_offset can be changed. In the above process, the rule-ipv4_type is judged first and then the rule-ipv4_offset is judged. The rule_ipv4_type can be judged first to determine the rule_ipv4_type to adjust the process, which involves slightly different step details. The steps performed in the process can also be simply split or merged without affecting the output.

The device for converting a multicast address according to an embodiment of the present invention is described below in conjunction with an application scenario. FIG. 7 is a schematic diagram of an application scenario of a multicast address translation apparatus according to an embodiment of the present invention. In FIG. 7, the conversion apparatus is connected to an IPv6 network and an IPv4 network. There is a computer 1 in the IPv6 network, which wants to obtain multicast data sent by the computer 2 in the IPv4 network.

The conversion rules obtained by the conversion device contain two conversion rules:

{ ffl8:5::/40, 235.0.0.0/24, 104, 0}; { ffl8:6::/40, 235.1.0.0/24, 96, 1 };

Assume that the multicast address of the multicast data that the computer 1 wants to acquire is ffl8:5::6:0; the destination address of the multicast data that the computer 2 needs to send is 235.0.0.6.

When the computer 1 makes a data request to the computer 2, the computer 1 sends a report to the multicast address ffl 8: 5:: 6: 0, for example, an MLD (Multicast Listener Discover) report. The message is transmitted to the conversion device via a network multicast protocol.

The conversion device uses ffl8:5::6:0 to match the conversion rule, which matches the ffl8:5::/40 of rule-ipv6-m_prefix to get the conversion rule. In the conversion rule, rule_ipv4_type is 0, which means that the IPv6 multicast address format is based on the IPv4 multicast address suffix. In the conversion rule rule - ipv4 - m_prefix corresponds to 235.0.0.0/24, then you can know that ipv4 - m - suffix length is 8 bits. Then get rule-ipv4_offset from the conversion rule is 104, you can get 8 bits of data from the 105th bit of ffl8:5::6:0, that is, 0x06, according to the decimal is 6, splicing Rule_ipv4_m_prefix and ipv4—m—suffix can get the IPv4 multicast address 235.0.0.6. In this way, the multicast protocol packet passing through the conversion device converts the request multicast address ffl8:5::6:0 used in the IPv6 packet into 235.0.0.6 used in the IPv4 network.

In the IPv4 network part, the multicast protocol for the 235.0.0.6 sent by the switching device to the IPv4 network is added, and the PIM-SM (Protocol Independent Multicast-Sparse Mode) is added. The message is sent to the first hop multicast routing device connected to the computer 2, and the network forwarding path of the cross-address family is established, and the multicast data of 235.0.0.6 is directed to the conversion device.

The multicast data flow arrival conversion device uses 235.0.0.6 to match the conversion rule, which matches the 235.0.0.0/24 of rule-ipv4-m_prefix, and obtains the conversion rule. rule_ipv6_m_prefix is ffl8:5::/40 . The rule-ipv4_type in the conversion rule is 0, which means that the IPv6 multicast address format is based on the IPv4 multicast address suffix. According to 235.0.0.0/24 and 235.0.0.6, ipv4_m_suffix is 6 and the length is 8 bits. The part before the target ipv6_m_addr is filled with rule_ipv6_m_prefix, that is, ffl8:5::/40, the rule-ipv4_offset in the conversion rule is 104, which is to place ipv4_m_suffix in the 105th position of ipv6_m_addr, rule — ipv6—m_prefix and ipv4—m—Between suffix and ipv4—m—the vacant bits after suffix are padded with 0, resulting in ffl8:5::6:0. In this way, through the conversion device, the multicast data stream using 235.0.0.6 in the IPv4 network reaches the IPv6 network and is converted into the multicast data using the ffl8:5::6:0. Thereby, the multicast forwarding entry established according to the multicast protocol sends the multicast data to the computer 1. The above solution is only used to explain the process of address translation, and does not limit how the multicast protocol message and data part are converted.

FIG. 8 is a schematic diagram of another application scenario of a multicast address translation apparatus according to an embodiment of the present invention. In FIG. 8, the conversion apparatus 1 is connected to an IPv6 network A and an IPv4 network B, and the conversion apparatus 2 is connected to an IPv4 network B and an IPv6 network. C. In the IPv6 network A, there is a computer 1 that wants to obtain the multicast data sent by the computer 2 in the IPv6 network C through the IPv4 network B.

The conversion rules acquired by the conversion device 1 and the conversion device 2 include two conversion rules:

{ ffl8:5::/40, 235.0.0.0/24, 104, 0};

{ ffl8:6::/40, 235.1.0.0/24, 96, 1 };

Assume that the multicast address of the multicast data that the computer 1 wants to acquire is ffl8:5::6:0; the destination address of the multicast data that the computer 2 needs to send is ffl8:5::6:0.

The computer 1 sends the multicast request information about ffl8:5::6:0, and reaches the conversion device 1 through network transmission and protocol conversion. According to the conversion mode illustrated in FIG. 7, the ffl8:5::6:0 is converted according to the conversion rule. Into 235.0.0.6, and sent to network B. The transmission to the conversion device 2 is carried out via the transmission of the network B. Similarly, according to the conversion method illustrated in Fig. 7, 235.0.0.6 is converted into ffl8:5::6:0 according to the conversion rule, and ffl8:5::6:0 is used in the network C. Perform multicast join. Establish a network forwarding path across address families. On the network C, the computer 2 transmits the multicast data of ffl8:5::6:0, and the multicast data converted into 235.0.0.6 after the conversion device 2 continues to propagate in the network B, and then converted into the converted device 1 and converted into The multicast data of ffl8:5::6:0 is sent to the computer 1 in the network A.

FIG. 7 and FIG. 8 are only used to describe the usage scenarios of the multicast address conversion apparatus in the embodiment of the present invention. The usage scenarios of the multicast address conversion apparatus in the embodiment of the present invention are not limited to the two scenarios, for example, The scenario in which the IPv4 network obtains the multicast data of the IPv6 network and the IPv4 network obtains the IPv4 network multicast data across the IPv6 network can also be used.

The technical solution of the embodiment of the present invention provides a method for converting between an IPv4 multicast address and an IPv6 multicast address, and a conversion device for performing the conversion method, which has a wide application scenario, and can set an existing multicast by using a conversion rule. Address translation technology is compatible. The use of the suffix of the IPv4 multicast address fully releases the length of the IPv6 prefix. The use of the multi-prefix rule can finer the use of the multicast address within the service range, and enhance the flexibility and security of the multicast service. Easier Management.

Many of the functional components described in this specification are referred to as modules to more particularly emphasize the independence of their implementation.

In an embodiment of the invention, the modules may be implemented in software for execution by various types of processors. For example, an identified executable code module can comprise one or more physical blocks or logical blocks of computer instructions, which can be constructed, for example, as an object, procedure, or function. Nonetheless, the executable code of the identified modules need not be physically located together, but may include different instructions stored on different physical blocks that, when logically combined, constitute the module and implement the provisions of the module purpose.

In fact, the executable code module can be a single instruction or a number of instructions, and can even be distributed over multiple different code segments, distributed among different programs, and distributed across multiple memory devices. Likewise, operational data may be identified within the module, implemented in any suitable form, and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations (including different storage devices), and may in part exist as an electronic signal only on the system or network.

When the module can be implemented by software, considering the level of the existing hardware process, the module can be implemented in software, and those skilled in the art can construct a hardware circuit to implement the module function without considering the cost. The circuit includes conventional Very Large Scale Integrated (VLSI) circuits, gate arrays, existing semiconductors such as logic chips, transistors, or other discrete components. Modules can also be implemented with programmable hardware devices, such as field programmable gate arrays, programmable array logic, or programmable logic devices.

In the method embodiments of the present invention, the sequence numbers of the steps are not used to limit the sequence of the steps. For those skilled in the art, the steps of the steps are changed without any creative work. It is also within the scope of the invention.

The above is a preferred embodiment of the embodiments of the present invention. It should be noted that those skilled in the art can make some improvements to the embodiments of the present invention without departing from the principles of the embodiments of the present invention. And retouching, these improvements and retouchings should also be considered as Within the scope of protection.

Industrial Applicability The technical solution of the embodiment of the present invention can enhance the flexibility and security of the multicast service, and is beneficial to network management. The IPv6 multicast address space can be better utilized, and the IPv4 multicast address and the network can be implemented in the network. Conversion between IPv6 multicast addresses.

Claims

j . jj -^* j$

1. A multicast address translation method, including:

Obtain the conversion rules corresponding to the multicast address to be converted, the conversion rules include multicast address prefix, IPv4 multicast address type and IPv4 multicast address offset position; and

Convert the multicast address into a target multicast address according to the conversion rule.

2. The method according to claim 1, wherein,

When the multicast address to be converted is an Internet Protocol version 4 (IPv4) multicast address, the conversion rules include an Internet Protocol version 6 (IPv6) multicast address prefix and an IPv4 multicast address prefix; and

When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv multicast address suffix, the step of converting the multicast address into the target multicast address according to the conversion rule includes:

Calculate the IPv4 multicast address suffix based on the IPv multicast address prefix and the IPv4 multicast address; and

The IPv6 multicast address prefix is placed at the starting position of the IPv6 multicast address, the IPv4 multicast address suffix is placed at the position indicated by the IPv4 multicast address offset position, and other empty positions are 0 to form the target IPv6 multicast address

3. The method according to claim 2, wherein,

When the conversion rule includes an IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indicates a starting offset defined by the IPv multicast address offset position parameter in the IPv6 multicast address. The IPv4 multicast address suffix is placed starting from the last bit of the shifted position; and

When the conversion rule does not include an IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indication places the IPv4 multicast address suffix at the last position of the IPv6 multicast address.

4. The method according to claim 1, wherein,

When the multicast address to be converted is an IPv4 multicast address, the conversion rules include an IPv6 multicast address prefix and an IPv4 multicast address prefix; and When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv4 multicast address, the step of converting the multicast address into the target multicast address according to the conversion rule includes:

The IPv6 multicast address prefix is placed at the starting position of the IPv6 multicast address, the IPv4 multicast address is placed at the position indicated by the IPv4 multicast address offset position, and other empty positions are 0 to form the target IPv6 group. broadcast address.

5. The method according to claim 4, wherein,

When the conversion rule includes an IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indicates a starting offset defined by the IPv4 multicast address offset position parameter in the IPv6 multicast address. The IPv4 multicast address is placed starting from the last bit of the shifted position; and

When the conversion rule does not include an IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indication places the IPv4 multicast address in the last 32 bits of the IPv6 multicast address.

6. The method according to claim 1, wherein,

When the multicast address to be converted is an IPv6 multicast address, the conversion rule includes an IPv4 multicast address prefix;

The length of the IPv4 multicast address suffix is calculated based on the length of the IPv4 multicast address prefix. In the IPv6 multicast address, the position indicated by the IPv6 multicast address offset position is based on the length of the IPv4 multicast address suffix. The length to obtain the IPv4 multicast address suffix; and

The IPv4 multicast address prefix and the IPv4 multicast address suffix are spliced together to form a target IPv4 multicast address.

7. The method according to claim 6, wherein,

When the conversion rule includes an IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indicates the starting point defined by the IPv4 multicast address offset position parameter in the IPv6 multicast address. The last bit of the offset position starts to obtain the IPv4 multicast address suffix; and When the conversion rule does not include an IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indication obtains the IPv4 multicast address suffix at the last position of the IPv6 multicast address.

8. The method according to claim 1, wherein,

When the multicast address to be converted is an IPv6 multicast address, and the IPv4 multicast address type indication forms the target multicast address based on the IPv4 multicast address, the multicast address is converted to the multicast address based on the conversion rule. The steps for address translation to a target multicast address include:

In the IPv6 multicast address, a 32-bit address is obtained at the position indicated by the IPv6 multicast address offset position as the target IPv multicast address.

9. The method according to claim 8, wherein,

When the conversion rule includes an IPv4 multicast address offset position parameter, the IPv multicast address offset position indicates a starting offset defined by the IPv4 multicast address offset position parameter in the IPv6 multicast address. Start obtaining the IPv4 multicast address from the last bit of the shifted position; and

When the conversion rule does not include the IPv4 multicast address offset position parameter, the IPv multicast address offset position indication is to obtain the IPv4 multicast address from the last 32 bits of the IPv6 multicast address.

10. A multicast address translation device, including:

The acquisition module is configured to: acquire the conversion rules corresponding to the multicast address to be converted, where the conversion rules include multicast address prefix, IPv4 multicast address type and IPv4 multicast address offset position; and

A conversion module, which is configured to: convert the multicast address into a target multicast address according to the conversion rule.

11. The conversion device according to claim 10, wherein,

When the IPv4 multicast address type indication forms the target multicast address based on the IPv4 multicast address suffix, the conversion module converts the multicast address into a target multicast address according to the conversion rules in the following manner: Calculate the IPv4 multicast address suffix based on the IPv multicast address prefix and the IPv4 multicast address; and

The IPv6 multicast address prefix is placed at the starting position of the IPv6 multicast address, the IPv4 multicast address suffix is placed at the position indicated by the IPv4 multicast address offset position, and other empty positions are set to 0 to form the target IPv6 multicast address.

12. The conversion device according to claim 11, wherein,

When the conversion rule includes an IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indicates a starting offset defined by the IPv4 multicast address offset position parameter in the IPv6 multicast address. The IPv4 multicast address suffix is placed starting from the last bit of the shifted position; and

13. The conversion device according to claim 10, wherein,

When the multicast address to be converted is an IPv4 multicast address, the conversion rules include an IPv6 multicast address prefix and an IPv4 multicast address prefix; and

When the IPv4 multicast address type indicates that the target multicast address is formed based on the IPv4 multicast address, the conversion module converts the multicast address into a target multicast address according to the conversion rules in the following manner:

The IPv6 multicast address prefix is placed at the starting position of the IPv6 multicast address, the IPv4 multicast address is placed at the position indicated by the IPv4 multicast address offset position, and other empty positions are set to 0 to form the target IPv6 group. broadcast address.

14. The conversion device according to claim 13, wherein,

When the conversion rule does not include the IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indication places the IPv4 multicast address in the last 32 bits of the IPv6 multicast address.

15. The conversion device according to claim 0, wherein, When the multicast address to be converted is an IPv6 multicast address, the conversion rule includes an IPv4 multicast address prefix;

When the IPv4 multicast address type indication forms the target multicast address based on the IPv4 multicast address suffix, the conversion module converts the multicast address into a target multicast address according to the conversion rules in the following manner:

Calculate the length of the IPv4 multicast address suffix based on the length of the IPv4 multicast address prefix;

In the IPv6 multicast address, the IPv multicast address suffix is obtained according to the length of the IPv4 multicast address suffix at the position indicated by the IPv6 multicast address offset position; and

The IPv4 multicast address prefix and the IPv4 multicast address suffix are combined to form a target IPv4 multicast address.

16. The conversion device according to claim 15, wherein,

When the conversion rule includes an IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indicates a starting offset defined by the IPv4 multicast address offset position parameter in the IPv6 multicast address. Start obtaining the IPv4 multicast address suffix from the last bit of the shifted position; and

When the conversion rule does not include the IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indication obtains the IPv4 multicast address suffix at the last position of the IPv6 multicast address.

17. The conversion device according to claim 10, wherein,

When the multicast address to be converted is an IPv6 multicast address, and the IPv4 multicast address type indication forms the target multicast address based on the IPv multicast address, the conversion module uses the conversion rules in the following manner Convert the multicast address to the target multicast address:

In the IPv6 multicast address, a 32-bit address is obtained as the target IPv4 multicast address at the position indicated by the IPv6 multicast address offset position.

18. The conversion device according to claim 17, wherein,

When the conversion rule includes an IPv4 multicast address offset position parameter, the IPv4 multicast address offset position indicates the starting point defined by the IPv4 multicast address offset position parameter in the IPv6 multicast address. The last bit of the offset position starts to obtain the IPv4 multicast address; and

When the conversion rule does not include the IPv multicast address offset position parameter, the IPv4 multicast address offset position indication is to obtain the IPv4 multicast address from the last 32 bits of the IPv6 multicast address.