JP3488114B2 - Closed user group network management system - Google Patents

Description

Description: BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a virtual private network (VPN) that communicates only within a specific group of members while using the Internet as a backbone.
The present invention relates to a management system for a closed user group (CUG: Closed User Group) network, such as a V. network. [0002] A CUG network management system has a C
In the management of the UG network, it is necessary to make settings such as addition and deletion of CUG members. In such a case, it is desirable that the member settings can be made efficiently. In the CUG, a node that transfers a packet has a member table and a routing table for each CUG. The member table has information on which member belongs to each CUG, and the routing table has information on each CU.
G has an entry in which a destination member and a transfer destination node are paired. [0004] When each node receives a packet addressed to a member of a certain CUG from a member connected to itself,
After confirming that the transmission source member is registered in the CUG member table, the packet is transferred in accordance with the CUG routing table, and if not registered, the packet is discarded. FIG. 1 shows an example of a CUG network. In the figure, CUG (1) and CUG (n) denote closed user groups (note that the numbers in parentheses represent group numbers), M1, and M1. M2,... Mx and My are members, N
1, N2 and N3 are nodes. FIG. 2B shows the details of the node N1, particularly the member table and the routing table owned by the node N1. Hereinafter, the mechanism of the CUG will be described by taking the node N1 of the CUG (1) as an example. First, consider a case where a member M1 of CUG (1) attempts to communicate with M2. Upon receiving the packet, the node N1 confirms that the transmission source member M1 is registered in the CUG (1) member table, and
Entry E in the routing table R11 for UG (1)
In accordance with 111, the packet is transferred to the node N2 which is the transfer destination of the member M2. Node N2 transfers the packet to member M
Hand over to 2. Next, consider the case where M5, which is not a member of CUG (1), attempts to communicate with M2. When the node N1 receives the packet, the member M5 of the transmission source
(1) Confirm that the packet is not registered in the member table, and discard the packet. Therefore, communication from outside the CUG is not possible. Next, the member M1 of CUG (1)
Consider a case where communication with M6 that is not a member of (1) is attempted. Upon receiving the packet, the node N1 confirms that the transmission source member M1 is registered in the CUG (1) member table, and tries to transfer the packet according to the CUG (1) routing table R11.
However, the entry for transferring the member M6 is
Since it is not in the routing table R11 for UG (1),
The packet is discarded. Therefore, communication outside the CUG cannot be performed. Here, consider adding a member M4 connected to the node N3 as a new member to CUG (1). At that time, (a) M4 is registered in N3 as a member of CUG (1), (b) M4 can communicate with M1, M2, and M3, and (c) M4 can communicate with M1, M2, and M3. It is necessary. Regarding (a), the CUG of the node N3
It is necessary to set the member M4 in the (1) member table. As for (b), members M1, M2, M
It is necessary to add an entry “the packet destined for M4 is transferred to N3” to the routing tables R11 and R21 (however, R21 is not shown) for the CUG (1) of the nodes N1 and N2 to which 3 is connected. . Further, regarding (c), the C of the node N3 to which the member M4 is connected
UG (1) routing table R31 (however, R3
1 is not shown in the figure) "The packet addressed to M1 is transferred to N1,
It is necessary to add an entry that "packets addressed to M2 and M3 are forwarded to N2." Conventionally, there is no mechanism for automatically setting the data required for adding a CUG member, and the operator has manually set the above-mentioned settings for all the related nodes. When a member of a CUG is added, an operator not only updates a member table of a node to which the member is connected but also updates all nodes to which each member of the CUG is connected. Must set an entry in the routing table owned by that node. Therefore, manually adding a CUG member by an operator is a very time-consuming operation. [0014] An object of the present invention is to solve the above-mentioned problem by efficiently setting a member table and a routing table of a node for adding a CUG member.
It is to provide a G network management system. According to the present invention, in order to achieve the above object, a network management system is enlarged to include a user interface unit, a node information database, a member information adding unit, a node information adding unit, and a node information collecting unit. , A routing information collecting unit and a routing table adding unit. The user interface receives an operation input from an operator. The node information database holds information on connection nodes of all members belonging to the CUG, using the CUG number as a key. The member information adding unit additionally sets a member in the CUG member table of the node based on the information of the CUG number, the member and the node from the user interface unit. The node information adding unit additionally sets a node in the node for the CUG in the node information database based on the CUG number and the node information from the user interface unit. The node information collecting unit searches the node information database from the CUG number from the user interface unit, and collects information on all nodes belonging to the CUG. The routing information collecting unit collects entries of the routing table for the CUG from each node from the CUG number and the node information from the node information collecting unit. The routing table addition unit is connected to additional members based on the CUG number, node and routing table entries from the routing information collection unit, and CUG number, member and node information from the user interface unit. The entry of the routing table of the node and all the nodes belonging to the CUG is set. In the above configuration, first, the user interface unit inputs information of the CUG number (n) to which a member is to be added, the member (Mj) to be added, and the node (Ni) to which the member is to be connected. The received information is passed to the member information adding unit, the node information adding unit, the node information collecting unit, and the routing table adding unit. The member information adding section includes a CUG number (n),
The member (Mj) is added to the member table for the CUG (n) of the node (Ni) based on the information of the member (Mj) and the node (Ni). The node information adding unit checks whether or not the node (Ni) is already included in the item for the CUG (n) in the node information database from the information of the CUG number (n) and the node (Ni). If it is not included, add it. The node information collection unit searches the node information database from the CUG number (n) and finds the CUG (n)
, And collects the information of all the nodes (Nx, Ny, Ni,...) And passes the collected information to the routing information collection unit. The routing information collecting unit includes a node (N
x, Ny, Ni,...)
G (n) routing tables (Rxn, Ryn,...)
..), ((Exn1, Exn2,...)),
(Eyn1, Eyn2, ...), ...
Pass it to the routing table addition unit (however, if the contents of the entries overlap, pass only one). The routing table adding unit stores the routing table (Rxn, Rx) collected by the routing information collecting unit in the routing table (Rin) for CUG (n) of the node (Ni) to which the member (Mj) is connected.
yn,...) entry (Einα, Einβ,...)
Add. The entry (Exn) is stored in the routing table (Rxn, Ryn,...) For CUG (n) of the node (Nx, Ny,...) To which the member is already connected.
a, Eynb, ...). FIG. 2 shows an embodiment of a closed user group network management system according to the present invention. In the figure, reference numeral 10 denotes a network management system, which includes a user interface unit 11, a node information database 12, a member information adding unit 13, a node information adding unit 14, a node information collecting unit 15, a routing information collecting unit 16, and a routing table adding unit 17. It consists of. The user interface unit 11 receives an operation input from an operator, and transfers the contents to a member information adding unit 13, a node information adding unit 14, a node information collecting unit 15, and a routing table adding unit 17. The node information database 12 holds information on connection nodes of all members belonging to the CUG, using the CUG number as a key. The member information adding unit 13 includes a CUG number to which a member from the user interface unit 11 is to be added,
Based on the information of the member to be added and its connection node, the member is additionally set in the CUG member table of the node. The node information adding unit 14 additionally sets a node in the node for the CUG in the node information database 12 based on the CUG number and the node information from the user interface unit 11. The node information collecting unit 15 searches the node information database 12 based on the CUG number from the user interface unit 11, collects information on all nodes belonging to the CUG, and sends the information together with the CUG number to the routing information collecting unit 16. hand over. The routing information collecting unit 16 calculates the CUG number and the node information from the node information collecting unit 15
An entry of the routing table of the CUG is collected from each node, and the collected entry is transferred to the routing table adding unit 17 together with the CUG number and the node information (however, if the contents of the entry are duplicated, only one is passed). The routing table adding unit 17 adds a CUG number, a node, and information of a routing table entry from the routing information collecting unit 16 and a CUG number, a member, and a node information from the user interface unit 11. The node to which the member is connected and the entries of the routing tables of all the nodes belonging to the CUG are set. FIG. 3 shows an example of an operation sequence of the CUG network management system according to the present invention, in which a member M4 is added to the CUG (1) described with reference to FIG. Here, the member M4 is connected to the node N3, and the CUG of the node information database 12 is stored.
It is assumed that nodes N1 and N2 are registered in the item for (1). (Step 1) User interface unit 1
1 receives information of a CUG number (1) to which a member is to be added, a member (M4) to be added, and a node (N3) to which the member is connected, input from the operator. (Step 2) The member information adding unit 13
CUG number (1) from the user interface unit 11,
The information of the member (M4) and the node (N3) is received, and the member (M4) is added to the CUG (1) member table of the node (N3). (Step 3) The node information adding unit 14
The information of the CUG number (1) and the node (N3) is received from the user interface unit 11, and the node (N) is added to the item for the CUG (1) in the node information database 12.
Add 3). (Step 4) The node information collecting unit 15
CUG number from user interface unit 11 (1)
The node information database 12 is searched from the
The information of all the connection nodes (N1, N2) belonging to (1) is collected and passed to the routing information collecting unit 16 together with the CUG number (1). (Step 5) Routing information collecting unit 1
6 is the information of the entry (E111, E112) in the routing table for the CUG (1) from the node (N1) based on the information of the CUG number (1) and the node (N1, N2) from the node information collecting unit 15. Is collected from the node (N2), and information of an entry (E211) in the routing table for the CUG (1) is collected.
The UG number (1) and the information of the nodes (N1, N2) are passed to the routing table adding unit 17 together with the information. In this example, there is no duplicate entry. (Step 6) The routing table adding unit 17 sets the node (N3) to which the member (M4) is connected.
In the routing table for CUG (1), each entry (E
311, E312 and E313) are added. Also, for the nodes (N1, N2) to which the members are already connected, an entry (E113) is entered in the routing table for the CUG (1) of the node N1, and the CUG (1) of the node N2.
(E212) is added to the routing table for the server. The above embodiment has three nodes,
Although the case where the members are four CUGs has been described, the present invention is not limited to this. As described above, according to the present invention,
The following effects can be obtained. 1. The operator has the information of the member added to CUG, C
Since only the UG number and the node to be connected need to be input to the user interface unit, there is no need to search for nodes that need to be added or changed by themselves and collect routing information. 2. The method of collecting routing table information and setting routing information differs for each target network and CUG realization method. However, in the present invention, since the routing information collecting unit and the routing table adding unit are independent, It can be easily applied to various networks and CUG realization methods.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram showing an example of a CUG network. FIG. 2 is a configuration diagram showing an example of an embodiment of a CUG network management system of the present invention. FIG. 3 is a CUG network management system of the present invention. [Description of References] 10: Network management system, 11: User interface unit, 12: Node information database, 13:
Member information adding unit, 14: Node information adding unit, 15: Node information collecting unit, 16: Routing information collecting unit, 1
7: Routing table adding unit.

────────────────────────────────────────────────── ─── Continuation of the front page (56) References JP-A-10-145364 (JP, A) JP-A-11-234283 (JP, A) JP-A-9-130421 (JP, A) JP-A-3- 141754 (JP, A) JP-A-1-166643 (JP, A) JP-A-2000-216780 (JP, A) (58) Fields investigated (Int. Cl. ⁷ , DB name) H04L 12/28 H04L 12 / 56

Claims (1)

(57) [Claims] [Claim 1] For each closed user group (CUG), which is a specific group of members, which members belong to each CUG
Member table having information on whether or not
The destination member and the destination node are paired.
Routing tables with entries
And using a plurality of nodes for transferring packets,
In a CUG network that communicates only within the CUG
And the member table of each node accompanying the addition of CUG members
Closed user group for setting the router and routing table
A loop network management system , comprising: a user interface unit, a node information database,
A member information adding unit, a node information adding unit, a node information collecting unit, a routing information collecting unit, and a routing table adding unit ;
CUG number to add member, member to add
The information of the node to which the member is connected is passed to the member information adding unit, the node information adding unit, the node information collecting unit, and the routing table adding unit, and the node information database uses the CUG number as a key for all the members belonging to the CUG. The member information adding unit holds the information of the connection node, and additionally sets a member in the CUG member table of the node from the information of the CUG number, the member and the node from the user interface unit. Based on the CUG number and the node information from the interface unit, a node is additionally set in the item for the CUG in the node information database. The node information collection unit searches the node information database from the CUG number from the user interface unit, and Collects information on all nodes belonging to CUG, CUG
The number is passed to the routing information collection unit along with the number.
From the UG number and the node information, each node
G entries of the routing table for G are collected and passed to the routing table adding unit together with the information of the CUG number and the node. The routing table adding unit receives the information of the CUG number, the node and the entry of the routing table from the routing information collecting unit. And a CUG number, a member and a node from the user interface unit, and set a node to which the additional member is connected and an entry in a routing table of all nodes belonging to the CUG. Network management system.