Source: https://patents.google.com/patent/US7551634?oq=7%2C682%2C496
Timestamp: 2018-03-18 02:23:20
Document Index: 424040971

Matched Legal Cases: ['§111', 'ART12', 'ART12', 'ART11', 'ART12', 'ART11', 'ART12', 'ART12', 'ART11', 'ART10', 'ART11', 'ART10', 'ART10', 'ART10', 'ART10', 'ART10', 'ART11', 'ART12', 'ART12', 'ART12', 'ART12', 'ART12', 'ART12', 'ART12', 'ART11', 'ART12', 'ART11', 'ART 11', 'ART12', 'ART 11', 'ART21', 'ART20', 'ART21', 'ART20', 'ART20', 'ART20', 'ART21', 'ART20', 'ART12', 'ART12', 'ART12', 'ART12', 'ART12', 'ART12', 'ART12']

US7551634B2 - Communication network system - Google Patents
US7551634B2
US7551634B2 US11024418 US2441804A US7551634B2 US 7551634 B2 US7551634 B2 US 7551634B2 US 11024418 US11024418 US 11024418 US 2441804 A US2441804 A US 2441804A US 7551634 B2 US7551634 B2 US 7551634B2
US11024418
US20050122981A1 (en )
Takehiro Nabae
This application is a continuing application, filed under 35 U.S.C. §111(a), of International Application PCT/JP02/11779, filed Nov. 12, 2002.
plural lower hierarchy networks having plural first relay apparatuses that accommodate at least one terminal in a distributed arrangement, respectively, and that adjacent ones of which are connected by a line, respectively; and
an intermediate hierarchy network having plural second relay apparatuses, adjacent ones of which are connected by a line, and connecting the plural lower hierarchy networks via the second relay apparatuses in edge positions to be connected with the first relay apparatuses in respective edge positions in the plural lower hierarchy networks, in which:
each of the first relay apparatuses in the plural lower hierarchy networks has a first routing table that holds information limited to routing information corresponding to the first relay apparatus and routing information on at least one of the first relay apparatuses and the second relay apparatuses in the edge positions that come into an adjacent state through the line; and
each of the second relay apparatuses in the intermediate hierarchy network has a second routing table that holds information including routing information on at least one of the second relay apparatuses and the first relay apparatuses in the edge positions that come into an adjacent state through the line.
According to a second aspect of the present invention, there is provided a communication network system, further including an upper hierarchy network having, when a plurality of the intermediate hierarchy networks are present, plural third relay apparatuses, adjacent ones of which are connected by a line, and connecting the plural intermediate hierarchy networks via the third relay apparatuses in edge positions that are connected with the second relay apparatuses in the respective edge positions in the plural intermediate hierarchy networks by a line, in which:
the second routing table of each of the second relay apparatuses in the plural intermediate hierarchy networks further holds routing information for routing to the third relay apparatuses in the edge positions; and
each of the third relay apparatuses in the edge positions in the upper hierarchy networks makes it possible to perform routing processing based on parameters for specifying a priority of a line in each section of the third relay apparatuses in an adjacent state.
In the communication network system according to the present invention, the upper hierarchy network is a backbone network that connects the plural intermediate hierarchy networks through a high-speed line.
The first route creation unit 2171 of the header management unit 217 creates additional information by adding a route in the local network LNW to an additional information area in a header portion of outgoing call information. At this point, the route creation unit 2171 sets an additional information flag to OFF “0”.
In a route check unit 2173 of the header management unit 217 of the area router ART, it is judged whether it is necessary to make connection through the area router ART. As a result, when it is judged that it is necessary to make connection through the area router ART (when routes do not overlap), the route creation unit 2171 of the header management unit 217 adds route information used in the local network LNW on an exit side to a header portion. At this point, the route creation unit 2171 sets the additional information flag to OFF “0”.
In the route check unit 2173 of the header management unit 217 of the area router ART, it is judged whether it is necessary to make connection through the area router ART. As a result, when it is judged that it is unnecessary to make connection through the area router ART (when routes overlap), the second route creation unit 2172 of the header management unit 217 adds route information (routing information) from a calling terminal to a called terminal in one local network LNW to a header portion as replay information. At this point, the route creation unit 2172 sets the additional information flag to ON “1”.
(5) Depending upon contents of an additional information flag included in the received outgoing call information (“1”: ON at the time of communication in the local network LNW and “0”: OFF in the case of reception from the wide network WNW or the area network ANW), when “1”: ON at the time of communication in the local network LNW, the area router ART sets a route opposite to a route in the received additional information in an additional information area to make it possible to send a reply from the terminal TE.
(6) As a result of checking the additional information flag in the additional information read unit 410, when the additional information flag is “1”: ON, the calling terminal TE having received the outgoing call information sets the additional information in the additional information setting unit 411 and performs re-calling.
(9) As a result of the routing processing that refers to the area routing table 212, when the destination exists and there is no route information in the outgoing call information, the area router ART having received the outgoing call information confirms whether there is additional information in the routing information and, when there is additional information, adds the additional information (indicating a route of routing in the local network LNW) to the received outgoing call information and transfers the outgoing call information to the local network LNW side. Here, when the area router ART adds the additional information to the received outgoing call information, the area router ART sets “0”: OFF in the additional information flag and transfers the outgoing call information to the local network LNW side.
In the local router LRT15, the header analysis unit 117 confirms contents of the additional information flag (ON=“1” or OFF=“0”) included in the outgoing call information from the calling terminal TE15. When the contents of the additional information flag is “1” indicating that there is additional information, the control unit 113 transfers the outgoing call information to the next route indicated by the additional information.
In addition, when the contents of the additional information flag is “0” indicating that there is no additional information, the control unit 113 judges how the received outgoing call information should be processed with reference to the slim routing table 112 of the local router LRT15 shown in FIG. 13. The control unit 113 confirms a network (sub-network) indicated by a destination IP address of an IP header in the header portion of the outgoing call information and confirms whether the network belongs to (is set in) the slim routing table 112 as a destination.
In this example, since the calling terminal TE15 transmits the outgoing call information to the called terminal TE14 of the network N14, a destination of the outgoing call information indicates the “network N14”. In the local router LRT15, when the control unit 13 refers to the slim routing table 112, the control unit 113 recognizes that a routing destination of the destination “N14” is not present in the table 112.
Therefore, the outgoing call information received from the calling terminal TE15 is transmitted to the local router LRT14 as a routing destination corresponding to a destination “others” in the table 112. In that case, in the local router LRT15, route addition information “local router LRT15” is stored (set) as a route, through which the outgoing call information is transmitted, in the route addition information area in the outgoing call information according to the function of the route addition unit 1161 of the header management unit 116.
Note that, for any local router LRT in the respective local networks LNWs, a routing destination corresponding to the destination “others” in the slim routing table 112 is set in a route to the area router ART.
In this example, since there is no additional information, as a result of referring to the slim routing table 112 (FIG. 13), the destination “N14” is “others”, and the local router LRT15 transmits the data packet to the local router LRT14 corresponding to a route to the area router ART.
In this example, since there is no receiving additional information in the local router LRT14, the local router LRT14 performs routing processing with reference to the slim routing table 112 (FIG. 14). As a result, the destination “N14” is “own router”, and the control unit 113 performs data transfer to a destination port corresponding to the called terminal TE14 under the control of the local router LRT14.
In the local router LRT14, the header analysis unit 116 confirms contents of the additional information flag (ON=“1” or OFF=“0”) included in the outgoing call information from the calling terminal TE14. When the contents of the additional information flag is “1” indicating that there is additional information, the control unit 113 transfers the outgoing call information to the next route indicated by the additional information.
In addition, when the contents of the additional information flag is “0” indicating that there is no additional information, the control unit 113 judges how the received outgoing call information should be processed with reference to the slim routing table 112 of the local router LRT14 shown in FIG. 16. The control unit 113 confirms a network (sub-network) indicated by a destination IP address of an IP header in the header portion of the outgoing call information and confirms whether the network belongs to (is set in) the slim routing table 112 as a destination.
In this example, since the calling terminal TE14 transmits the outgoing call information to the called terminal TE12 of the network N12 in the local network LNW11, a destination of the outgoing call information indicates the “network N12”. In the local router LRT14, when the control unit 13 refers to the slim routing table 112, the control unit 113 recognizes that a routing destination of the destination “N12” is not present in the table 112.
Therefore, the outgoing call information received from the calling terminal TE14 is transmitted to the area router ART12 as a routing destination corresponding to a destination “others” in the table 112. In that case, in the local router LRT14, route addition information “local router LRT14” is stored as a route, through which the outgoing call information is transmitted, in the route addition information area in the outgoing call information according to the function of the route addition unit 1161 of the header management unit 116.
Note that, for any local router LRT in the respective local network LNW, a routing destination corresponding to the destination “others” in the slim routing table 112 is set in a route to the area router ART.
In the area router ART12, the control unit 213 judges how the outgoing call-information received from the local router LRT14 should be processed with reference to the area routing table 212 shown in FIG. 17. In cooperation with the header analysis unit 216, first, the control unit 213 confirms a network indicated by the destination IP address of the IP header in the header portion of the outgoing call information and confirms whether there is a corresponding routing destination in the area routing table 212. When there is no corresponding routing destination, the control unit 213 transfers the outgoing call information to the area router ART corresponding to a route to the wide router WRT indicated by the destination “others”.
In this example, since the destination IP address of the IP header is the network “N12” and the routing destination is the area router ART11, the area router ART12 transfers the outgoing call information to the area router ART11. At this point, the route information deletion unit 2176 of the header management unit 217 in the area router ART12 deletes the route information (route addition information) “local router LRT14” set in the route addition information area of the header portion of the outgoing call information received from the local router LRT14.
When overlap of routes is confirmed by the route check unit 2173, in other words, when it is judged that the local routers LRTs are capable of communicating with one another even without passing the area router ART12, the area router ART creates reply information, in which route addition information and the additional information flag “1” among the local routers LRTs are set, with the second route creation unit 2172 of the header management unit 217 and further adds the created reply information to the outgoing call information to the calling terminal TE14 and transmits the outgoing call information according to the function of the route transmission unit 2174 of the header management unit 217.
In the area router ART11, in cooperation with the header analysis unit 216, the control unit 213 confirms a network indicated by the destination IP address of the IP header in the header portion of the outgoing call information and confirms whether there is a corresponding routing destination in the area routing table 212 (FIG. 18). If there is no corresponding routing destination, the control unit 213 transfers the outgoing call information to a route to the wide router WRT corresponding to a routing destination indicated by the destination “others” in the area routing table 212.
In this example, since the destination IP address of the IP header in the outgoing call information is the network “N12” and the routing destination is the “area router ART10”, the area router ART11 transfers the outgoing call information to the area router ART10.
In the area router ART10, in cooperation with the header analysis unit 216, the control unit 213 confirms a network indicated by the destination IP address of the IP header in the header portion of the outgoing call information and confirms whether there is a corresponding routing destination in the area routing table 212. If there is no corresponding routing destination, the control unit 213 transfers the outgoing call information to a route to the wide router WRT corresponding to a routing destination indicated by the destination “others” in the area routing table 212.
In this example, since the destination IP address of the IP header in the outgoing call information is the network “N12” and the routing destination is the “local router LRT12”, the area router ART10 transfers the outgoing call information to the local router LRT12.
At this point, in the area router ART10, the control unit 213 creates additional information, which indicates a transfer route in the local network LNW11 on the called side and the additional information flag “0”, for the called terminal TE12 with the first route creation unit 2171 of the header management unit 217. Moreover, the route transmission unit 2174 of the header management unit 217 transmits the outgoing call information, in which the additional information is added to the additional information area in the header unit of the outgoing call information, to the next router.
In this example, since the called local router LRT12 is adjacent to the area router ART10, there are no additional information flag and additional information. Note that, for example, when a destination is the network “N10”, the additional information flag is “0” and the additional information is the “local router LRT10”.
In this example, since there is no additional information in the data packet transmitted from the calling terminal TE14, as a result of referring to the slim routing table 112, the destination “N2” is the destination of “others”. Thus, outgoing call information is transmitted to the area router ART corresponding to a route to area routers.
In the local router LRT12 having received the data packet, the control unit 113 confirms presence or absence of additional information in the data packet. When there is additional information, the control unit 113 performs routing processing in a route indicated by the additional information. When there is no additional information, the control unit 113 performs routing processing on the basis of the slim routing table 212 of the local router LRT12. In this example, since there is no additional information and, as a result of referring to the area routing table 212, the destination “N12” is a routing destination “own router”, the local router LRT12 performs data transfer to a destination port corresponding to the called terminal TE12 under its control.
In the local router LRT14, the header analysis unit 117 confirms contents of the additional information flag (ON=“1” or OFF=“0”) included in the outgoing call information from the calling terminal TE14. When the contents of the additional information flag is “1” indicating that there is additional information, the control unit 113 transfers the outgoing call information to the next route indicated by the additional information.
In addition, when the contents of the additional information flag is “0” indicating that there is no additional information, the control unit 113 judges how the received outgoing call information should be processed with reference to the slim routing table 112 of the local router LRT14 shown in FIG. 22. The control unit 113 confirms a network (sub-network) indicated by a destination IP address of an IP header in the header portion of the outgoing call information and confirms whether the network belongs to the slim routing table 112 as a destination.
In this example, since the calling terminal TE14 transmits the outgoing call information to the called terminal TE16 of the network N16 in the local network LNW12, a destination of the outgoing call information indicates the “network N16”. In the local router LRT14 when the control unit 113 refers to the slim routing table 112, the control unit 113 recognizes that a routing destination of the destination “N16” is not present in the table 112.
Consequently, the control unit 213 confirms whether a corresponding destination (network) is present in the area routing table 212. When there is no corresponding destination, the control unit 213 transfers the outgoing call information to a route to the wide router WRT corresponding to the routing destination “area router ART11” indicated by the destination “others”.
In this example, since the destination “N16” is present in the area routing table 212, there is a corresponding routing destination. In other words, the destination IP address is “NN16”, the routing destination is the “local router LRT14”, and the additional information is the “local router LRT15” and the “local router LRT16”.
At this point, in the area router ART12, the route read unit 2175 of the header management unit 217 reads route information. In this example, the route read unit 2175 reads out the route addition information “local router LRT14” of the route addition information area included in the header portion of the outgoing call information. Then, the route read unit 2175 compares the routing destination “local router LRT14” and the routing destination addition information “local router LRT15, local router LRT16” indicated by the destination “N16” in the area routing table 212 and the route addition information “local router LRT14” included in the outgoing call information and confirms presence or absence of an overlapped portion.
The comparison and confirmation of this overlapped portion is as described below. In this case, in the area router ART12, as a result of comparing the routing destinations “the local router LRT14, the local router LRT15, and the local router LRT16” and the route addition information “local router LRT14”, it is seen that the “local router LRT14” overlaps. In other words, it is seen that it is possible to make connection in the local network LNW12 even without passing the area router ART12.
In the area router ART12 that has judged that it is possible to make connection in the local network LNW12, for the calling terminal TE14, the second route creation unit 2172 of the header management unit 217 stores an additional information flag, which is required when the calling terminal TE14 re-calls, as “reply information 1” and stores additional information as “reply information 2” in a free-use area of a header portion of reply information shown in FIG. 24 or 25. FIG. 24 shows a format of reply information applicable to the protocol IPv4 and FIG. 25 shows a format of reply information applicable to the protocol IPv6.
In this example, since the additional information flag at the time when the calling terminal TE14 calls is “1” and the additional information is “the local router LRT14, the local router LRT15, and the local router LRT16”, “1” is stored in a reply information section 1 and “the local router LRT14, the local router LRT15, and the local router LRT16” is stored in a reply information section 2. Note that the additional information flag included in the reply information is “0”, the additional information is the “local router LRT14”, and the route addition information is “none”.
The route transmission unit 2174 of the header management unit 217 in the area router ART12 transmits the reply information to the calling terminal TE14. In this case, contents to be stored in the free-use area of the header portion as reply information are the additional information flag “0”, the additional information the “local router LRT14”, the route addition information “none”, the reply information 1 “1”, the reply information 2 “the local router LRT14, the local router LRT15,and the local router LRT16”.
The route transmission unit 2174 of the header management unit 217 confirms the additional information “local router LRT14” of the reply information and transmits the reply information to the local router LRT14.
In the local router LRT14 having received the reply information, the control unit 113 confirms the additional information of the reply information in cooperation with the header analysis unit 117. However, since the contents is the “local router LRT14”, the control unit.113 performs routing processing with reference to the slim routing table 112 (FIG. 22) held by the control unit 113 itself.
As a result of the reference to the slim routing table 112, since the destination “N14” is under the control of its own router, the control unit 13 transmits the reply information to a destination port (corresponding to the calling terminal TE14) indicated by the destination IP address.
In the calling terminal TE14 having received the reply information, the additional information read unit 410 reads the reply information 1 and the reply information 2 included in the header portion of the reply information. In the calling terminal TE14, the additional information setting unit 411 sets the contents of the reply information 1 and the reply information 2 read by the additional information read unit 410 in the outgoing call information as an additional information flag and additional information. In other words, in the calling terminal TE14, the additional information setting unit 411 sets the additional information flag “1” and the additional information “the local router LRT14, the local router LRT15, and the local router LRT16” in the outgoing call information and transmits the outgoing call information in the local router LRT14 again.
In this example, since the additional information exists in the outgoing call information, in the local router LRT14, the control unit 113 performs routing processing on the basis of the additional information. In this case, since the contents of the additional information is “the local router LRT14, the local router LRT15, and the local router LRT16”, in the local router LRT14, the control unit 113 performs transfer processing to the local router LRT15 as the next routing destination.
In the local router LRT15 having received the outgoing call information from the local router LRT14, as in the local router LRT14, the control unit 113 confirms whether there is additional information in the outgoing call information. In this case, since additional information is included in the outgoing call information, in the local router LRT15, the control unit 113 transfers the outgoing call information to the routing destination “local router LRT16” indicated in the additional information.
In the local router LRT16, as in the local routers LRT14 and LRT15, the control unit 113 confirms an additional information flag included in the outgoing call information. In this case, since additional information is included but additional information on or after the “local router LRT16” is not included, in the local router LRT16, the control unit 113 performs routing processing with reference to the slim routing table 112 held by the local router LRT16 itself shown in FIG. 26. In the local router LRT16, as a result of the reference to the slim routing table 112, since a routing destination indicated by the destination “N16” is “own router”, the control unit 113 transmits the outgoing call information to a destination port (corresponding to the calling terminal TE16) indicated by a destination IP address.
In the called terminal TE16 having received the outgoing call information from the local router LRT16, the additional information read unit 410 reads the additional information flag and the additional information. When the additional information flag of the outgoing call information, which is transmitted from the calling terminal TE14 and received through the local router LRT16, is “1”, the called terminal TE16 sets the additional information flag to “0” with the additional information setting unit 411 and sets additional information with an order of contents reversed from that at the time of reception.
For example, when the called terminal TE16 replies (transmits data) to the calling terminal TE14, the called terminal TE16 adds the contents set by the additional information setting unit 411, that is, the additional information flag “0” and additional information “the local router LRT16, the local router LRT15, and the local router LRT14” with an order of contents reversed from that at the time of reception to the data packet and performs data transmission. Note that, when the additional information flag transmitted from the outgoing terminal TE14 is “0”, the called terminal TE16 does not perform the setting by the additional information setting unit 411.
In this example, since there is additional information, routing processing is performed on the basis of an instruction of the additional information, and the data packet is transferred to the local router LRT15. In the local router LRT15, the control unit 113 confirms presence or absence of additional information and, since there is additional information, transfers the outgoing call information to the routing destination “local router LRT16”.
The local router LRT16 also confirms that there is additional information. However, since there is no additional information on or after the local router LRT16, the local router LRT16 performs routing processing with reference to the slim routing table 112 (FIG. 26) of the local router LRT16. In this case, since a routing destination indicated by the destination “N16” is “own router”, in the local router LRT16, the control unit 113 performs data transfer to a destination port corresponding to the called terminal TE6 under the control of its own router.
In addition, when the contents of the additional information flag is “0” indicating that there is no additional information, the control unit 113 judges how the received outgoing call information should be processed with reference to the slim routing table 112 of the local router LRT14 shown in FIG. 28. The control unit 113 confirms a network (sub-network) indicated by a destination IP address of an IP header in the header portion of the outgoing call information and confirms whether the network belongs to slim routing table 112 as a destination.
In this example, since there is no additional information in the outgoing call information, in the local router LRT14, the control unit 113 performs routing processing with reference to the slim routing table 112. In the local router LRT14, when the slim routing table 112 is referred to, the destination “N20” is not present in the table 112.
Therefore, the control unit 113 transmits the outgoing call information to the routing destination “area router ART12” indicated by the destination “others” in the slim routing table 112. At that point, in the local router LRT14, the control unit 13 stores the route “local router LRT14”, through which the outgoing call information is transmitted, in the route addition information area in the header portion of the outgoing call information as route addition information.
In the area router ART12, first, the control unit 113 confirms a network indicated by the destination IP address of the IP header in the header portion of the outgoing call information and confirms whether there is a corresponding routing destination in the area routing table 212. When there is no corresponding routing destination, the control unit 113 transfers the outgoing call information to a route to the wide router WRT corresponding to a routing destination indicated by the destination “others”.
In this example, since the destination is “N20”, there is no corresponding routing destination, and the control unit 113 transfers the outgoing call information to the area router ART11 corresponding to the route to the wide router WRT indicated by the destination “others”. In transferring the outgoing call information, the area router ART12 deletes route information included in the outgoing call information according to the function of the route information deletion unit 2176 of the header management unit 217 and transfers the outgoing call information to the area router ART11.
The area router ART 11 receives the outgoing call information from the area router ART12. In the area router ART 11, the control unit 213 confirms a network indicated by the destination IP address of the outgoing call information and confirms whether there is a corresponding routing destination in the area routing table 212 shown in FIG. 30. When there is no corresponding routing destination, the control unit 213 transfers the outgoing call information to the route to the wide router WRT corresponding to the routing destination indicated by the destination “others”. In this example, since there is no corresponding routing destination, the outgoing call information is transferred to the wide router WRT11.
In this example, since there is no wide information in the outgoing call information received by the wide router WRT11, in the wide router WRT11, the control unit 314 performs confirmation of the parameters of the outgoing call information. As a result, since there is no parameter either, in the wide router WRT11, the control unit 314 searches for a route leading to the destination “N20” with reference to the wide routing table 313 shown in FIG. 33. Here, the parameter of the wide network WNW is subjected to system setting (default setting) in advance as “1: line speed” among “1: line speed, 2: the number of hops, and 3: security level”.
Route R2: Wide router WRT11 Wide router WRT12 Wide router WRT13 Wide router WRT14
Route R3: Wide router WRT11 Wide router WRT15 Wide router WRT16 Wide router WRT14
=Total parameter value: 4+4=8
=Total parameter value: 2+2+2=6
=Total parameter value: 3+3+3=9
As a result, the route R2, in which the total parameter value (line speed) has a minimum value “6”, is adopted.
=Total parameter value: 1+1=2
=Total parameter value: 1+1+1=3
As a result, the route R1, in which the total parameter value (number of hops) has a minimum value “2”, is adopted.
In the wide router WRT11, as a result of searching the wide routing table 313 (FIG. 33) for a route for the destination “N20”, the control unit 314 confirms that the routing destination is the “wide router WRT12”, the wide information 1 is the “wide router WRT13”, and the wide information 2 is the “wide router WRT14”.
In this example, first, the wide router WRT11 stores the wide information 1 “wide router WRT13” and the wide information 2 “wide router WRT14” with respect to the outgoing call information of the protocol IPv4 (FIG. 31) or the protocol IPv6 (FIG. 32). Next, the wide router WRT11 transfers the outgoing call information to the wide router WRT12 that is a routing destination.
In the wide router WRT12 having received the outgoing call information from the wide router WRT11, the control unit 314 confirms whether wide information (wide information 1 and 2) is included in the outgoing call information. In this case, since the wide information 1 “wide router WRT13” is included in the outgoing call information, the wide router WRT12 transfers the outgoing call information to the wide router WRT13 in the next stage (next hop). At this point, the wide information deletion unit 321 of the wide router WRT12 deletes the wide information 1 “wide router WRT13” from the header portion of the outgoing call information.
In the wide router WRT13 having received the outgoing call information from the wide router WRT12, the control unit 314 confirms whether wide information is included in the outgoing call information. In this case, since the wide information 2 “wide router WRT14” is included in the outgoing call information, the wide router WRT13 transfers the outgoing call information to the wide router WRT14 in the next stage. At this point, the wide information deletion unit 321 of the wide router WRT13 deletes the wide information 2 “wide router WRT14” from the header portion of the outgoing call information.
In the wide router WRT14 having received the outgoing call information from the wide router WRT13, the control unit 314 also confirms whether wide information is included in the outgoing call information. In this case, since wide information is not included in the outgoing call information, in the wide router WRT14, the control unit 314 confirms a destination indicated by the destination IP address of the IP header with reference to the wide routing table 313 shown in FIG. 35. When the destination is the area router ART under the control of its own router, the wide router WRT14 transfers the outgoing call information to the area router ART. Here, since the destination of the outgoing call information is “N20”, the wide router WRT14 applies routing processing to the area router ART21.
In this example, the destination IP address of the IP header is the destination “N20” and the routing destination is the “area router ART20”. Therefore, the area router ART21 transfers the received outgoing call information to the area router ART20.
In this example, since the destination IP address of the IP header is the destination “N20” and the routing destination is the “local router LRT21”, the area router ART20 transfers the received outgoing call information to the local router LRT21.
At this point, for the called terminal TE20, the area router ART20 adds an additional information flag and additional information to the header portion of the outgoing call information with the first route creation unit 2171 of the header management unit 217. Here, the additional information flag is “0” and the additional information is the “local router LRT20”.
Note that, concerning the additional information flag, an additional information flag “1” is set in the case of the third operation example described-above (the communication form for routing in the local network LNW according to a reconnection request from the area network ANW to the local network LNW). In all other cases, an additional information flag “0” is set.
In addition, when the destination is not the local router LRT21 itself, the local router LRT21 confirms whether there is additional information in the header portion of the outgoing call information and, when there is additional information, transfers the outgoing call information to a destination indicated by the additional information. When there is no additional information, the local router LRT21 performs routing processing according to the slim routing table 213. In this example, since there is the “local router LRT20” as additional information, the local router LRT21 transfers the outgoing call information to the local router LRT20.
In the local router LRT20, the control unit 113 processes the outgoing call information received from the local router LRT21 with reference to the slim routing table 112 held by the local router LRT20 itself and shown in FIG. 39. First, the control unit 113 confirms the destination IP address of the IP header in the header portion of the outgoing call information according to the area routing table 112. Since the destination “N20” corresponds to the terminal TE20 included in the local router LRT20 itself, in the local router LRT20, the control unit 113 transmits the outgoing call information to a destination port corresponding to the destination IP address of the received outgoing call information.
In the local network LNW12, the calling terminal TE14 performs an outgoing call request by transmitting the outgoing call information to the local router LRT14. At this point, concerning routing processing in the wide network WNW, the calling terminal TE14 requests the system side to minimize the number of hops. Therefore, the calling terminal TE14 stores the parameter “the number of hops” in the free-use area in the header portion of the outgoing call information and, then, transmits the outgoing call information to the local router LRT14. The outgoing call information transmitted from the calling terminal TE14 has the contents shown in FIGS. 11 and 12 as in the first operation example described above.
In this example, since there is no wide information in the outgoing call information received by the wide router WRT11, in the wide router WRT11, the control unit 314 confirms presence or absence of parameters of the outgoing call information. As a result, since the parameter “the number of hops” is present in the outgoing call information, in the wide router WRT11, the control unit 314 finds whether “2: the number of hops” is set in a route leading to the destination “N20” as a parameter with reference to the wide routing table 313 shown in FIG. 33.
Here, since a parameter of the wide network WNW is subjected to system setting (default setting) uniformly as “1: line speed” among “1: line speed, 2: the number of hops, and 3: security level” in advance, “2: the number of hops” is not present in the wide routing table 313 as a parameter for the destination “N20”. Thus, in the wide router WRT11, the control unit 314 searches the parameter table 312 shown in FIG. 34 for the most effective route to the destination “N20” and adds the most effective route to the wide routing table 313 shown in FIG. 33.
Concerning these three routes, the control unit 314 adopts a route in which a total parameter value of the parameter “the number of pops” is minimized, that is, a route in which the number of wide routers on the route is the smallest and adds the route in the wide routing table 313 shown in FIG. 33. Note that, in adding the route, a transfer object wide router in the next stage (the wide router WRT10) writes (stores) a wide router on the route (the wide router WRT14) following the wide router WRT10 as wide information. FIG. 40 shows an example of the wide routing table 313 created after the addition processing.
In the wide router WRT11, as a result of searching the wide routing table 313 shown in FIG. 40 for a route corresponding to the parameter “2: the number of hops” for the destination “N20”, the control unit 314 confirms that the routing destination is the “wide router WRT10”, and the wide information 1 is the “wide router WRT14”.
In this example, first, the wide router WRT11 stores the wide information 1 “wide router WRT14” with respect to the outgoing call information of the protocol IPv4 (FIG. 31) or the protocol IPv6 (FIG. 32) with reference to the wild routing table 313. Next, the wide router WRT11 transfers the outgoing call information to the wide router WRT10 that is a routing destination.
In the wide router WRT10 having received the outgoing call information from the wide router WRT11, the control unit 314 confirms whether wide information (wide information 1 and 2) is included in the outgoing call information. In this case, since the wide information 1 “wide router WRT14” is included in the outgoing call information, the wide router WRT10 transfers the outgoing call information to the wide router WRT14 in the next stage. At this point, the wide information deletion unit 321 of the wide router WRT10 deletes the wide information 1 “wide router WRT14” from the header portion of the outgoing call information.
In the wide router WRT14 having received the outgoing call information from the wide router WRT10, the control unit 314 confirms whether wide information is included in the outgoing call information. In this case, since wide information is not included in the outgoing call information, in the wide router WRT14, the control unit 314 confirms a destination indicated by the destination IP address of the IP header with reference to the wide routing table 313 shown in FIG. 35. When the destination is the area router ART under the control of its own router, the wide router WRT14 transfers the outgoing call information to the area router ART. Here, since the destination of the outgoing call information is “N20”, the wide router WRT14 applies routing processing to the area router ART21.
At this point, for the called terminal TE20, the area router ART20 adds an additional information flag and additional information to the header portion of the outgoing call information with the first route creation unit 2171 of the header management unit 217. Here, the additional information flag is “0” and the additional information is the “local router LRT20”. The outgoing call information added with the additional information flag and the additional information is transmitted by the route transmission unit 2174 of the header management unit 217.
Note that, concerning the additional information flag, in the case of the third operation example described above (the communication form for performing routing in the local network LNW according to a reconnection request from the area network ANW to the local network LNW), an additional information flag “1” is set. In all other cases, an additional information flag “0” is set.
In the table 112 of the local router LRT16, destinations “N15” and a routing destination “local router LRT15” are set (FIG. 42).
In the table 112 of the local router LRT15, destinations “N16”, and “14”, and routing destinations “local router LRT16”, and “local router LRT14” are set (FIG. 43).
In the table 112 of the local router LRT14, destinations “N15” and “13”, and routing destination “local router LRT15”, and “local router LRT13” are set (FIG. 44).
In the table 112 of the local router LRT13, a destination “others”, and a routing destination “local router LRT14” are set (FIG. 45).
In the table 212 of the area router ART12, destinations “N13”, “N14”, “N15”, and “N16” and a routing destination “local router LRT14” are set (FIG. 46).
(2) The area router ART12 notifies the local router LRT14 to be directly connected to the local network LNW12 of area router information as routing information. The local router LRT14 having received the area router information adds the destination “others” and the routing destination “area router ART12” to the routing table 112 of the local router LRT14 itself and, at the same time, transmits the area router information to the local routers LRT13 and LRT15 corresponding to all exit routes (excluding entrance routes) connected to the local router LRT14.
In the table 112 of the local router LRT16, a routing destination “local router LRT15” is additionally set as a route to an area router (FIG. 42).
In the table 112 of the local router LRT15, a routing destination “local router LRT14” is additionally set as a route to an area router (FIG. 43).
In the table 112 of the local router LRT14, a routing destination “local router LRT12” is additionally set as a route to an area router (FIG. 44).
In the table 112 of the local router LRT13, a routing destination “local router LRT14” is additionally set as a route to an area router (FIG. 45).
Then, the local router information transmitted from the local router LRT13 reaches the area router ART12 as “the local router LRT13 and the local router LRT14”.
The local router information transmitted from the local router LRT14 reaches the area router ART12 as “the local router LRT14”.
The local router information transmitted from the local router LRT15 reaches the area router ART12 as “the local router LRT15 and the local router LRT14”.
The local router information transmitted from the local router LRT16 reaches the area router ART12 as “the local router LRT16, the local router LRT15, and the local router LRT14”.
US11024418 2002-11-12 2004-12-30 Communication network system Active 2024-09-27 US7551634B2 (en)
PCT/JP2002/011779 WO2004045163A1 (en) 2002-11-12 2002-11-12 Communication network system
US11024418 US7551634B2 (en) 2002-11-12 2004-12-30 Communication network system
US20050122981A1 true US20050122981A1 (en) 2005-06-09
US7551634B2 true US7551634B2 (en) 2009-06-23
ID=34632393
US11024418 Active 2024-09-27 US7551634B2 (en) 2002-11-12 2004-12-30 Communication network system
US (1) US7551634B2 (en)
WO2013001655A1 (en) * 2011-06-30 2013-01-03 富士通株式会社 Route search program and information processing device
JPH053492A (en) 1991-06-25 1993-01-08 Nissan Motor Co Ltd Communication processing unit for hierarchical network
JPH0766835A (en) 1993-07-30 1995-03-10 Internatl Business Mach Corp <Ibm> Communication network and path selection method for the same
JP2000031978A (en) 1998-07-10 2000-01-28 Mitsubishi Electric Corp Call control system and call control method
EP1104963A1 (en) 1999-12-01 2001-06-06 Lucent Technologies Inc. Method and apparatus for exchanging routing information in a packet-based data network
JP2002252635A (en) 2001-02-23 2002-09-06 Mitsubishi Electric Corp Data communication system, data relay device and data relay method
Norito Fujita et al., "Kaiso-ka o Mochiita Scalable na IP-Qos Seigyo System", The Institute of Electronics, Information and Communication Engineers Gijutsu Kenkyu Hokoku, SSE99-125, Dec. 17, 1999, Section 2, 1-2.2.
US20050122981A1 (en) 2005-06-09 application
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NABAE, TAKEHIRO;REEL/FRAME:016139/0986