WO2013178051A1

WO2013178051A1 - Method of communicating for multiple address families and network apparatus

Info

Publication number: WO2013178051A1
Application number: PCT/CN2013/076322
Authority: WO
Inventors: Shetty M RAJESH; Lokabiraman SRINIVASAN; M R Ravi; A K Keshava
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2012-05-28
Filing date: 2013-05-28
Publication date: 2013-12-05

Abstract

The embodiments of the present invention provide a method of communicating for multiple address families, the method comprising: receiving a packet by a common network apparatus, wherein an instance identifier for multiple address families in OSPFv3 is included in the packet; dispatching the packet to one of specific network apparatus according to the instance identifier; wherein the specific network apparatus and the common network apparatus are distributed. Through the embodiments of the present invention, multiple address families can be supported in OSPFv3 such that scalability and reliability can be improved.

Description

METHOD OF COMMUNICATING FOR MULTIPLE ADDRESS FAMILIES AND NETWORK APPARATUS

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to India Application No. IN2113/CHE/2012, entitled "METHOD OF COMMUNICATING FOR MULTIPLE ADDRESS FAMILIES AND NETWORK APPARATUS " and filed on May 28, 2012, the content of which is incorporated by reference herein.

FIELD OF THE INVENTION This application relates to Open Shortest Path First version 3 (OSPFv3) and in particular, to a method of communicating for multiple address families and a network apparatus.

BACKGROUND

Open Shortest Path First (OSPF) is a link-state routing protocol designed to be used as an Interior Gateway Protocol (IGP). This means that it distributes routing information between routers belonging to a single Autonomous System (AS). The OSPF protocol is based on link-state or SPF (Shortest Path First) technology.

OSPF for IPv6, henceforth named as OSPF version 3 (OSPFv3), included some modifications due to changes in protocol semantics from IPv4 (Internet Protocol version 4) to IPv6 (Internet Protocol version 6), however the fundamental mechanism of OSPF remains same as OSPF for IPv4. OSPFv3 is a designed to be an IPv6 unicast routing protocol, but there are requirements where OSPFv3 needs to advertise other Address Families (AFs) in OSPFv3, including multicast IPv6, unicast IPv4, and multicast IPv4.

However, the applicant found that the above implementation leads to scalability issues where OSPFv3 running on a single processing unit supports multiple address families.

[Reference 1 ] "OSPF Version 2" , RFC 2328.

[Reference 2 ] "OSPF for IPv6", RFC 5340.

[Reference 3 ] "Support of Address Families in OSPFv3", RFC 5838.

SUMMARY

Embodiments of the present invention pertain to a method of communicating for multiple address families and network apparatus. The aim is to support multiple address families in OSPFv3 to improve scalability and reliability. According a first aspect of the embodiments of the present invention, there is provided a method of communicating for multiple address families, the method comprising:

Receiving a packet by a common network apparatus, wherein an instance identifier for multiple address families in OSPFv3 (Open Shortest Path First version 3) is included in the packet;

Dispatching the packet to one of specific network apparatus according to the instance identifier; wherein the specific network apparatus and the common network apparatus are distributed.

According a second aspect of the embodiments of the present invention, there is provided a method of communicating for multiple address families, the method comprising:

Receiving a packet from a common network apparatus by a specific network apparatus; wherein the packet is dispatched by a common network apparatus according to an instance identifier for multiple address families included in the packet;

Handling the packet by the specific network apparatus; wherein the specific network apparatus and the common network apparatus are distributed.

According a third aspect of the embodiments of the present invention, there is provided a common network apparatus, the common network apparatus comprising:

A first receiver, configured to receive a packet, wherein an instance identifier for multiple address families in OSPFv3 is included in the packet;

A first dispatcher, configured to dispatch the packet to one of specific network apparatus according to the instance identifier; wherein the specific network apparatus and the common network apparatus are distributed.

According a fourth aspect of the embodiments of the present invention, there is provided a specific network apparatus, the specific network apparatus comprising:

A third receiver, configured to receive a packet from a common network apparatus; wherein the packet is dispatched by a common network apparatus according to an instance identifier for multiple address families included in the packet;

A handler, configured to handle the packet; wherein the specific network apparatus and the common network apparatus are distributed.

According a fifth aspect of the embodiments of the present invention, there is provided a computer-readable program, wherein when the program is executed in a network apparatus, the program enables the computer to carry out the method of communicating for multiple address families.

According a sixth aspect of the embodiments of the present invention, there is provided a storage medium in which a computer-readable program is stored, wherein the computer-readable program enables the computer to carry out the method of communicating for multiple address families.

The advantages of the present invention exist in that multiple address families can be supported in OSPFv3 such that scalability and reliability can be improved.

These and further aspects and features of the present invention will be apparent with reference to the following description and attached drawings. In the description and drawings, particular embodiments of the invention have been disclosed in detail as being indicative of some of the ways in which the principles of the invention may be employed, but it is understood that the invention is not limited correspondingly in scope. Rather, the invention includes all changes, modifications and equivalents coming within the spirit and terms of the appended claims.

Features that are described and/or illustrated with respect to one embodiment may be used in the same way or in a similar way in one or more other embodiments and/or in combination with or instead of the features of the other embodiments.

It should be emphasized that the term "comprises/comprising" when used in this specification is taken to specify the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.

Many aspects of the invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. To facilitate illustrating and describing some parts of the invention, corresponding portions of the drawings may be exaggerated in size, e.g., made larger in relation to other parts than in an exemplary device actually made according to the invention. Elements and features depicted in one drawing or embodiment of the invention may be combined with elements and features depicted in one or more additional drawings or embodiments. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views and may be used to designate like or similar parts in more than one embodiment.

BRIEF DESCRIPTION OF THE DRAWING The drawings are included to provide further understanding of the present invention, which constitute a part of the specification and illustrate the preferred embodiments of the present invention, and are used for setting forth the principles of the present invention together with the description. The same element is represented with the same reference number throughout the drawings.

In the drawings:

Figure 1 is a topology diagram showing a typical example of multiple address families supporting for OSPFv3 ;

Figure 2 is another topology diagram showing a typical example of multiple address families supporting for OSPFv3 ;

Figure 3 is flowchart of the method of an embodiment of the present invention;

Figure 4 is a schematic diagram of the specific network apparatus and the common network apparatus are distributed;

Figure 5 is a schematic diagram of the packet receiving flow;

Figure 6 is flowchart of the method of another embodiment of the present invention; Figure 7 is a schematic diagram of the command processing;

Figure 8 is flowchart of the method of an embodiment of the present invention;

Figure 9 is flowchart of the method of another embodiment of the present invention;

Figure 10 is a sequence diagram of the packet sending flow;

Figure 11 is a schematic diagram of the packet sending flow;

Figure 12 is flowchart of the method of another embodiment of the present invention;

Figure 13 is a schematic diagram of the common network apparatus of an embodiment of the present invention;

Figure 14 is a schematic diagram of the common network apparatus of another embodiment of the present invention;

Figure 15 is a schematic diagram of the specific network apparatus of an embodiment of the present invention;

Figure 16 is a schematic diagram of the specific network apparatus of another embodiment of the present invention;

Figure 17 is a schematic diagram of the specific network apparatus of another embodiment of the present invention.

DETAILED DESCRIPTION

The many features and advantages of the embodiments are apparent from the detailed specification and, thus, it is intended by the appended claims to cover all such features and advantages of the embodiments that fall within the true spirit and scope thereof. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the inventive embodiments to the exact construction and operation illustrated and described, and accordingly all suitable modifications and equivalents may be resorted to, falling within the scope thereof.

The preferred embodiments of the present invention are described as follows in reference to the drawings.

Nowadays, RFC detailed background has mentioned how to support multiple address families in OSPFv3. Specifically, OSPFv3 protocol has instance identifier (Instance ID) which enables it to run multiple OSPFv3 instances on a single link. Currently, the entire Instance ID number space (0-255) is used for IPv6 unicast.

In order to support multiple address families in OSPFv3, the Instance ID can be used, please refer to [reference 3] for the detail description. Group of Instance ID is mapped to a specific OSPFv3 address family with its own neighbor adjacency, link state database, protocol data structure, SPF Tree, and Routing table.

Instance ID zero is already defined by default for the IPv6 unicast address family, rest Instance ID number space has been segregated into multiple address ranges, as listed below in table 1, wherein the first value of each range is the default value for the corresponding address family. Table 1

Instance ID # 0 - # 31 IPv6 unicast address family

Instance ID # 32 - # 63 IPv6 multicast address family

Instance ID # 64 - # 95 IPv4 unicast address family

Instance ID # 96 - # 127 IPv4 multicast address family

Instance ID # 128 - # 255 Unassigned

Currently 0SPFv3 running in single location (such as in one network apparatus) supports base IPv6 unicast address family IPv6 multicast address family IPv4 unicast address family, and IPv4 multicast address family. When simultaneously there is a need to achieve IPv4 unicast/multicast routing protocol performance parameter as well as IPv6 unicast/multicast routing protocol performance parameter, scalability is a concern.

Few among the possible concerns during transition are described below. Such as achieve the routing convergence for unicast ipv4 and ipv6 routes, accommodate huge number of unicast IPv4 and unicast IPv6 routes, incorporate IK neighbors for each of IPv4 and IPv6 protocols, and so on.

Figure 1 is a topology diagram showing a typical example of multiple address families supporting for OSPFv3. As shown in Figure 1, in the deployment scenario, OSPFv3 is running in single location (in DUT router), and the DUT supports multiple address families.

Wherein, the DUT enables three separate OSPFv3 instances on the same interface with instance id 64, 1 and 32 to support IPv4 unicast, IPv6 unicast and IPv6 multicast AF, respectively. In such type of scenario where OSPFv3 (in DUT) running in a single processing unit, supporting multiple address families scalability is a concern.

In this scenario, unicast routing information is relatively very huge. It's possible that RTB router (it supports unicast IPv4 address families) and RTC router (it supports unicast IPv6 address family) advertise a huge number of routing information to DUT. In such case DUT may reach or exceed the threshold of system resources (such as memory and CPU).

Figure 2 is another topology diagram showing a typical example of multiple address families supporting for OSPFv3. As shown in Figure 2, in the deployment scenario, OSPFv3 is also running in single location (in DUT router), and the DUT supports multiple address families.

Wherein, the DUT enables multiple address families for supporting IPv4 and IPv6 Neighbors. In such type of scenario where OSPFv3 (In DUT) running in a single processing unit, supporting multiple address families scalability is a concern.

In this scenario, if there are IK Unicast IPv4 neighbors and IK unicast IPv6 neighbors,

DUT might not able to serve all of them.

Embodiment 1

The embodiments of the present invention provide a method of communicating for multiple address families, and the method applied for a common network apparatus. Figure 3 is flowchart of the method of an embodiment of the present invention. As shown in Figure 3, the method comprising:

Step 301, the common network apparatus receives a packet, wherein an instance identifier for multiple address families in OSPFv3 is included in the packet;

Step 302, the common network apparatus dispatches the packet to one of specific network apparatus according to the instance identifier; wherein the specific network apparatus and the common network apparatus are distributed.

In the present application, based on the address family, OSPFv3 functionality is distributed across different locations or processing units, such that each functionality related address family can be maintained in different and independent locations or processing units. So that scalability of system is improved.

Specifically, the instance identifier may be used for IPv6 unicast address family, IPv6 multicast address family, IPv4 unicast address family, or IPv4 unicast address family; and the specific network apparatus may include: a network apparatus for IPv6 unicast address family, a network apparatus for IPv6 multicast address family, a network apparatus for IPv4 unicast address family, or a network apparatus for IPv4 multicast address family.

It should be noted that the specific network apparatus may include one or more apparatus. For example, in a scenario, the specific network apparatus may include two apparatus: a network apparatus for IPv6 unicast address family and a network apparatus for IPv6 multicast address family. In another scenario, the specific network apparatus may include four apparatus: a network apparatus for IPv6 unicast address family, a network apparatus for IPv6 multicast address family, a network apparatus for IPv4 unicast address family, and a network apparatus for IPv4 multicast address family. However, it is not limited thereto, and particular manner may be determined as actually required.

Figure 4 is a schematic diagram of the specific network apparatus and the common network apparatus are distributed. As shown in Figure 4, an abstract module within OSPFv3, hereafter named as Common OSPFv3, has been introduced. And each functionality related address family can be maintained in different locations.

In the present application, this abstract module (Common OSPFv3) will hide OSPFv3 internal implementation from surrounding modules. Some function of the Common OSPFv3 is listed below.

For example, the Common OSPFv3 will deal with received packet and dispatch the packet to a specific OSPFv3 address family based on the instance id in the packet header. And as we described below, the Common OSPFv3 will dispatch the command issued from System Management Plane (SMP) to particular OSPFv3 address family based upon the address family.

In this present application, the Common Ospfv3 can run in any processing unit or location. This is a light weight module which just dispatches.

In this present application, the functionalities performed by each of the address family are listed below. Such as, performing authentication, maintaining neighbor relationship, maintaining Link state database, maintaining the protocol specific data structure, calculating shortest path first (SPF) tree, calculating route, downloading and maintain routing table, sending packet and sending command response.

In this application, to implement this solution, OSPF packet receiving flow, packet sending flow, and/or configuration flow need to be changed, however the other protocol-related changes and defined behaviors need no change. The detail will be described as below.

In an embodiment of the present invention, packet receiving flow is changed. Figure 5 is a schematic diagram of the packet receiving flow. As shown in Figure 5, the Common OSPFv3 creates a socket along with OSPFv3 protocol ID (such as 89) in order to receive all OSPFv3 packets.

When a packet arrives on the socket, the Common OSPFv3 dispatches the packet to a specific OSPFv3 (such as OSPFv3 unicast IPv6, OSPFv3 multicast IPv6, OSPFv3 unicast IPv4, or OSPFv3 multicast IPv4) based on the OSPFv3 instance ID present in packet.

In an embodiment of the present invention, SMP (system management plane) command processing is changed. Figure 6 is flowchart of the method of another embodiment of the present invention. As shown in Figure 6, the method comprising:

Step 601, the common network apparatus receives a packet, wherein an instance identifier for multiple address families in OSPFv3 is included in the packet;

Step 602, the common network apparatus dispatches the packet to one of specific network apparatus according to the instance identifier; wherein the specific network apparatus and the common network apparatus are distributed.

As shown in Figure 6, the method further comprising:

Step 603, the common network apparatus receives a command for OSPFv3 from a

SMP;

Step 604, the common network apparatus dispatches the command to one of the specific network apparatus according to an address family if the address family is mentioned in the command; and dispatches the command to the network apparatus for IPv6 unicast address family if any address family is not mentioned in the command.

In this embodiment, OSPFv3 command processing needed to be changed for address family support. To make the implementation simple, this invention may mandate address family MUST be mentioned along with the IGP process creation, also change of address family is not allowed.

In this embodiment, if the address family is not mentioned then the default address family would be IPv6 unicast address family. The processing is mentioned below.

Such as, the command first arrives to the Common OSPFv3 when the command is executed. For OSPFv3 configuration command, the command is dispatched to specific address family if the address family is mentioned; otherwise, the command is dispatched to IPv6 unicast address family.

Figure 7 is a schematic diagram of the command processing. As shown in Figure 7, after the command is executed by the specific network apparatus (the OSPFv3 address family module) unsuccessfully or successfully, the specific network apparatus sends the response to the SMP directly.

It can be seen from the above embodiments that this invention provides OSPFv3 to support multiple address families by distributing of the common network apparatus and the specific network apparatus. Multiple address families can be supported in OSPFv3 such that scalability and reliability can be improved.

Embodiment 2

The embodiments of the present invention further provide a method of communicating for multiple address families, and the method applied for a specific network apparatus. And the same content in embodiment 1 will not be described.

Figure 8 is flowchart of the method of an embodiment of the present invention. As shown in Figure 8, the method comprising:

Step 801, the specific network apparatus receives a packet from a common network apparatus; wherein the packet is dispatched by the common network apparatus according to an instance identifier for multiple address families included in the packet;

Step 802, the specific network apparatus handles the packet; wherein the specific network apparatus and the common network apparatus are distributed.

In the present application, the instance identifier is used for IPv6 unicast address family, IPv6 multicast address family, IPv4 unicast address family, or IPv4 unicast address family; and

The specific network apparatus may include: a network apparatus for IPv6 unicast address family, a network apparatus for IPv6 multicast address family, a network apparatus for IPv4 unicast address family, or a network apparatus for IPv4 multicast address family.

In this present application, the specific network apparatus handles the packet may include: performing authentication, maintaining neighbor relationship, maintaining Link state database, maintaining the protocol specific data structure, calculating shortest path first (SPF) tree, calculating route, downloading and maintaining routing table, sending packet and sending command response.

In an embodiment of the present invention, packet sending flow is changed. Figure 9 is flowchart of the method of another embodiment of the present invention. As shown in Figure 9, the method comprising:

Step 901, the specific network apparatus receives a packet from a common network apparatus; wherein the packet is dispatched by the common network apparatus according to an instance identifier for multiple address families included in the packet;

Step 902, the specific network apparatus handles the packet; wherein the specific network apparatus and the common network apparatus are distributed.

As shown in Figure 9, the method further comprising:

Step 903, the specific network apparatus creates a socket without protocol identifier such that the specific network apparatus does not receive packet on the socket;

Step 904, the specific network apparatus creates a RAW IP packet; and sends the RAW

IP packet by using the socket. In this embodiment, each OSPFv3 instance should separately create and send packet independently. Any OSPFv3 address family packet send does not interact with Common-OSPFv3.

In this embodiment, when a packet is received by a specific network apparatus (specific OSPFv3), the specific network apparatus performs necessary packet checks, sends LS-Request, sends LS-Ack, floods to other neighbors, performs route calculation and downloads the route to route manager.

In this embodiment, the specific network apparatus creates a socket without protocol id such that it does not receive packet on the socket. If the specific OSPFv3 need to send packet, it makes the packet and sends directly as RAW IP protocol packet.

Figure 10 is a sequence diagram of the packet sending flow, and Figure 11 is a schematic diagram of the packet sending flow. As shown in Figure 10 and Figure 11, the specific network apparatus will send packet directly.

In an embodiment of the present invention, SMP command processing is changed. Figure 12 is flowchart of the method of another embodiment of the present invention. As shown in Figure 12, the method comprising:

Step 1201, the specific network apparatus receives a packet from a common network apparatus; wherein the packet is dispatched by the common network apparatus according to an instance identifier for multiple address families included in the packet;

Step 1202, the specific network apparatus handles the packet; wherein the specific network apparatus and the common network apparatus are distributed.

As shown in Figure 12, the method further comprising:

Step 1203, the specific network apparatus receives a command for OSPFv3 ; wherein the command is from a SMP and dispatched by the common network apparatus;

Step 1204, the specific network apparatus executes the command, and sends a response to the SMP directly.

Embodiment 3

This embodiment of the present invention further provides a common network apparatus. This embodiment is correspondes to the method in embodiment 1, and the same content will not be described.

Figure 13 is a schematic diagram of the common network apparatus of an embodiment of the present invention. As shown in Figure 13, the common network apparatus 1300 comprising: a first receiver 1301 and a first dispatcher 1302;

Wherein, the first receiver 1301 is configured to receive a packet, wherein an instance identifier for multiple address families in OSPFv3 is included in the packet; the first dispatcher 1302 is configured to dispatch the packet to one of specific network apparatus according to the instance identifier; wherein the specific network apparatus and the common network apparatus are distributed.

In this embodiment, the instance identifier is used for IPv6 unicast address family, IPv6 multicast address family, IPv4 unicast address family, or IPv4 unicast address family; and

The specific network apparatus comprising: a network apparatus for IPv6 unicast address family, a network apparatus for IPv6 multicast address family, a network apparatus for IPv4 unicast address family, a network apparatus for IPv4 multicast address family.

Figure 14 is a schematic diagram of the common network apparatus of another embodiment of the present invention. As shown in Figure 14, the common network apparatus 1400 comprising: a first receiver 1301 and a first dispatcher 1302, as above described.

As shown in Figure 14, the common network apparatus further comprising: A second receiver 1403 and a second dispatcher 1404; wherein the second receiver 1403 is configured to receive a command for OSPFv3 from a SMP; the second dispatcher 1404 is configured to dispatch the command to one of the specific network apparatus according to an address family if the address family is mentioned in the command; and dispatch the command to the network apparatus for IPv6 unicast address family if any address family is not mentioned in the command.

It can be seen from the above embodiments that this invention provides OSPFv3 to support multiple address families by distributing of the common network apparatus and the specific network apparatus. Multiple address families can be supported in OSPFv3 without any scalability issues.

Embodiment 4

This embodiment of the present invention further provides a specific network apparatus. This embodiment is correspondes to the method in embodiment 2, and the same content will not be described.

Figure 15 is a schematic diagram of the specific network apparatus of an embodiment of the present invention. As shown in Figure 15, the specific network apparatus 1500 comprising: a third receiver 1501 and a handler 1502;

Wherein, the third receiver 1501 is configured to receive a packet from a common network apparatus; wherein the packet is dispatched by the common network apparatus according to an instance identifier for multiple address families included in the packet; the handler 1502 is configured to handle the packet; wherein the specific network apparatus and the common network apparatus are distributed.

Figure 16 is a schematic diagram of the specific network apparatus of another embodiment of the present invention. As shown in Figure 16, the common network apparatus 1600 comprising: a third receiver 1501 and a handler 1502, as above described.

As shown in Figure 16, the specific network apparatus further comprising: a first creator 1603, a second creator 1604 and a first sender 1605; wherein, the first creator 1603 is configured to create a socket without protocol identifier such that the specific network apparatus does not receive packet on the socket; the second creator 1604 is configured to create a RAW IP packet; and the first sender 1605 is configured to send the RAW IP packet by using the socket.

Figure 17 is a schematic diagram of the specific network apparatus of another embodiment of the present invention. As shown in Figure 17, the common network apparatus 1700 comprising: a third receiver 1501 and a handler 1502, as above described.

As shown in Figure 17, the specific network apparatus further comprising: a fourth receiver 1703, an executor 1704 and a second sender 1705; wherein, the fourth receiver 1703 is configured to receive a command for OSPFv3; wherein the command is from a SMP and dispatched by the common network apparatus; the executor 1704 is configured to execute the command; and the second sender 1705 is configured to send a response to the SMP directly.

It can be seen from the above embodiments that this invention provides OSPFv3 to support multiple address families by distributing of the common network apparatus and the specific network apparatus. Multiple address families can be supported in OSPFv3 such that scalability and reliability can be improved .

The embodiments of the present invention further provide a computer- readable program, wherein when the program is executed in a network apparatus; the program enables the computer to carry out the method of communicating for multiple address families.

The embodiments of the present invention further provide a storage medium in which a computer-readable program is stored, wherein the computer-readable program enables the computer to carry out the method of communicating for multiple address families.

It should be understood that each of the parts of the present invention may be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods may be realized by software or firmware that is stored in the memory and executed by an appropriate instruction executing system. For example, if it is realized by hardware, it may be realized by any one of the following technologies known in the art or a combination thereof as in another embodiment: a discrete logic circuit having a logic gate circuit for realizing logic functions of data signals, application-specific integrated circuit having an appropriate combined logic gate circuit, a programmable gate array (PGA), and a field programmable gate array (FPGA), etc.

The description or blocks in the flowcharts or of any process or method in other manners may be understood as being indicative of comprising one or more modules, segments or parts for realizing the codes of executable instructions of the steps in specific logic functions or processes, and that the scope of the preferred embodiments of the present invention comprise other implementations, wherein the functions may be executed in manners different from those shown or discussed, including executing the functions according to the related functions in a substantially simultaneous manner or in a reverse order, which should be understood by those skilled in the art to which the present invention pertains.

The logic and/or steps shown in the flowcharts or described in other manners here may be, for example, understood as a sequencing list of executable instructions for realizing logic functions, which may be implemented in any computer readable medium, for use by an instruction executing system, device or apparatus (such as a system including a computer, a system including a processor, or other systems capable of extracting instructions from an instruction executing system, device or apparatus and executing the instructions), or for use in combination with the instruction executing system, device or apparatus.

The above literal description and drawings show various features of the present invention. It should be understood that those skilled in the art may prepare appropriate computer codes to carry out each of the steps and processes as described above and shown in the drawings. It should be also understood that all the terminals, computers, servers, and networks may be any type, and the computer codes may be prepared according to the disclosure to carry out the present invention by using the apparatus.

Particular embodiments of the present invention have been disclosed herein. Those skilled in the art will readily recognize that the present invention is applicable in other environments. In practice, there exist many embodiments and implementations. The appended claims are by no means intended to limit the scope of the present invention to the above particular embodiments. Furthermore, any reference to "a device to..." is an explanation of device plus function for describing elements and claims, and it is not desired that any element using no reference to "a device to..." is understood as an element of device plus function, even though the wording of "device" is included in that claim.

Although a particular preferred embodiment or embodiments have been shown and the present invention has been described, it is obvious that equivalent modifications and variants are conceivable to those skilled in the art in reading and understanding the description and drawings. Especially for various functions executed by the above elements (portions, assemblies, apparatus, and compositions, etc.), except otherwise specified, it is desirable that the terms (including the reference to "device") describing these elements correspond to any element executing particular functions of these elements (i.e. functional equivalents), even though the element is different from that executing the function of an exemplary embodiment or embodiments illustrated in the present invention with respect to structure. Furthermore, although the a particular feature of the present invention is described with respect to only one or more of the illustrated embodiments, such a feature may be combined with one or more other features of other embodiments as desired and in consideration of advantageous aspects of any given or particular application.

Claims

WE CLAIM:

1. A method of communicating for multiple address families, the method comprising: Receiving a packet by a common network apparatus, wherein an instance identifier for multiple address families in OSPFv3 (Open Shortest Path First version 3) is included in the packet;

Dispatching the packet to a specific network apparatus according to the instance identifier; wherein the specific network apparatus and the common network apparatus are distributed.

2. The method as claimed in claim 1, wherein the instance identifier is used for IPv6 unicast address family, IPv6 multicast address family, IPv4 unicast address family, or IPv4 unicast address family; and

The specific network apparatus comprises: a network apparatus for IPv6 unicast address family, a network apparatus for IPv6 multicast address family, a network apparatus for IPv4 unicast address family, or a network apparatus for IPv4 multicast address family.

3. The method as claimed in claim 2, wherein the method further comprising:

Receiving a command for OSPFv3 from a SMP (system management plane) by the common network apparatus;

Dispatching the command to one of the specific network apparatus according to an address family if the address family is mentioned in the command; and dispatching the command to the network apparatus for IPv6 unicast address family if any address family is not mentioned in the command.

4. A method of communicating for multiple address families, the method comprising: Receiving a packet from a common network apparatus by a specific network apparatus; wherein the packet is dispatched by the common network apparatus according to an instance identifier for multiple address families included in the packet;

5. The method as claimed in claim 4, wherein the instance identifier is used for IPv6 unicast address family, IPv6 multicast address family, IPv4 unicast address family, or IPv4 unicast address family; and

The specific network apparatus includes: a network apparatus for IPv6 unicast address family, a network apparatus for IPv6 multicast address family, a network apparatus for IPv4 unicast address family, or a network apparatus for IPv4 multicast address family.

6. The method as claimed in claim 4 or 5, wherein the method further comprising:

Creating a socket without protocol identifier by the specific network apparatus such that the specific network apparatus does not receive packet on the socket;

Creating a RAW IP packet; and sending the RAW IP packet by using the socket.

7. The method as claimed in claim 5, wherein the method further comprising:

Receiving a command for OSPFv3 by the specific network apparatus; wherein the command is from a SMP and dispatched by the common network apparatus;

Executing the command; and sending a response to the SMP directly.

8. A common network apparatus, the common network apparatus comprising:

A first dispatcher, configured to dispatch the packet to a specific network apparatus according to the instance identifier; wherein the specific network apparatus and the common network apparatus are distributed.

9. The common network apparatus as claimed in claim 8, wherein the instance identifier is used for IPv6 unicast address family, IPv6 multicast address family, IPv4 unicast address family, or IPv4 unicast address family; and

10. The common network apparatus as claimed in claim 9, wherein the common network apparatus further comprising:

A second receiver, configured to receive a command for OSPFv3 from a SMP;

A second dispatcher, configured to dispatch the command to one of the specific network apparatus according to an address family if the address family is mentioned in the command; and dispatch the command to the network apparatus for IPv6 unicast address family if any address family is not mentioned in the command.

11. A specific network apparatus, the specific network apparatus comprising:

A third receiver, configured to receive a packet from a common network apparatus; wherein the packet is dispatched by the common network apparatus according to an instance identifier for multiple address families included in the packet;

12. The specific network apparatus as claimed in claim 11, wherein the instance identifier is used for IPv6 unicast address family, IPv6 multicast address family, IPv4 unicast address family, or IPv4 unicast address family; and

13. The specific network apparatus as claimed in claim 11 or 12, wherein the specific network apparatus further comprising:

A first creator, configured to create a socket without protocol identifier such that the specific network apparatus does not receive packet on the socket;

A second creator, configured to create a RAW IP packet; and

A first sender, configured to send the RAW IP packet by using the socket.

14. The specific network apparatus as claimed in claim 12, wherein the specific network apparatus further comprising:

A fourth receiver, configured to receive a command for OSPFv3; wherein the command is from a SMP and dispatched by the common network apparatus;

An executor, configured to execute the command; and

A second sender, configured to send a response to the SMP directly.