IPv4 routing information processing method, device, system, IPv4 data packet processing method, device and system

A processing method and technology of a processing device, which are applied in the field of communication applications

CN105577544AActive Publication Date: 2016-05-11CHINA MOBILE COMM GRP CO LTD
2 Cites 2 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Publication Date
2016-05-11

Smart Images

  • Figure 1
    Figure 1
  • Figure 2
    Figure 2
  • Figure 3
    Figure 3
Patent Text Reader

Abstract

The invention provides an IPv4 routing information processing method, device, system as well as an IPv4 data packet processing method, device and system. The objective of the invention is to solve the problem of the incapability of an existing IPv4 site to realize intercommunication through the IPv6 network operating multiple protocol label switching (MPLS). The processing method includes the step that the routing information of IPv4 routing is transferred to an egress 4PE router through extending a sub address family identifier (SAFI) in a multi-protocol border gateway protocol (MP-BGP), wherein the routing information contains an MPLS label corresponding to the IPv4 routing, the next hop of the IPv4 routing and the next hop of IPv6 routing. According to the IPv4 routing information processing method and the IPv4 data packet processing method of the invention, the SAFI in the multi-protocol border gateway protocol is extended, so that the IPv4 routing can be transferred through the IPv6 network, and an IPv4 data packet can be forwarded through the IPv6 network operating the multiple protocol label switching (MPLS).
Need to check novelty before this filing date? Find Prior Art

Description

technical field

[0001] The present invention relates to the technical field of communication applications, in particular to a processing method, device and system for IPv4 routing information and IPv4 data packets. Background technique

[0002] After the IPv6 protocol (RFC2460) is widely used, the network protocol and traffic will be dominated by IPv6 single-site, how a small number of IPv4 sites can communicate through the IPv6 single-site network running Multi-Protocol Label Switching MPLS will become a problem, draft-ietf-mpls The problem is also clearly pointed out in -ldp-IPv6, and there is no solution yet.

[0003] To solve this problem, the following two aspects need to be solved: first, how to transmit the IPv4 route through the IPv6 network; second, how to forward the IPv4 data packet through the IPv6 network.

[0004] RFC5512, Border Gateway Protocol Encapsulation Subaddress Family Identifier and Tunnel Encapsulation BGPEncapsulationSAFIandTunnelEncapsulation, a t...

Examples

Embodiment 1

[0116] When a 4PE router announces an IPv4 route to other 4PE routers, it passes the IPv4 address of the interface receiving the IPv4 route and its global global IPv6 address reachable in the IPv6 network to the egress 4PE router (that is, the peer 4PE router) through the nexthop domain. . Among them, MP-BGPupdate message such as figure 2 shown. NLRI contains the IPv4 routes to be delivered and their corresponding MPLS labels. The format and definition of NLRI are consistent with RFC3107, such as image 3 shown.

[0117] The above-described embodiment one transmits the IPv4 next hop and the IPv6 next hop to the egress 4PE router by extending the next hop nexthop domain in the SAFI; by extending the network layer reachable message in the SAFI The NLRI domain transfers the IPv4 route and the MPLS label corresponding to the IPv4 route to the egress 4PE router.

Embodiment 2

[0119] When a 4PE router announces an IPv4 route to other 4PE routers, it passes the IPv4 address of the interface receiving the IPv4 route to the other side through the extended community attribute, and passes one of its own global IPv6 addresses to the other side through the nexthop domain. MP-BGPupdate packets such as Figure 4 shown.

[0120] The NLRI contains the IPv4 routes to be delivered and their corresponding MPLS labels. The format and definition of the NLRI are consistent with RFC3107.

[0121] Define a new Extendedcommunity domain for delivering IPv4 next hops. The format of Extendedcommunity is consistent with RFC4360. The specific value of type needs to be applied to IANA International Organization for Standardization, and the value is the IPv4 address. like Figure 5 shown.

[0122] The second embodiment above transmits the IPv4 next hop to the egress 4PE router by extending the extended community attribute Extendedcommunity domain in the SAFI; transmits th...

Embodiment 3

[0124] When a 4PE router announces an IPv4 route to other 4PE routers, it passes the IPv4 address of the interface receiving the IPv4 route to the other party through the nexthop domain, and passes one of its own globalIPv6 addresses to the other party through the NLRI. Among them, MP-BGPupdate message such as Image 6 shown.

[0125] Update RFC3107, define a new NLRI format, transfer content includes IPv4 route, MPLS label corresponding to IPv4 route and corresponding IPv6 next hop. The position of the IPv6 next hop can be before or after the MPLS label, depending on standardization. Figure 7 An example is given where the IPv6 next hop is before the MPLS label.

[0126] The third embodiment above transmits the IPv4 next hop to the egress 4PE router by extending the nexthop domain in the SAFI; transfers the IPv4 route and the MPLS corresponding to the IPv4 route by extending the NLRI domain in the SAFI The label and the IPv6 next hop are passed to the egress 4PE router.