Access relay method and access gateway device

• US 9,537,755 B2
• Filed: 01/20/2015
• Issued: 01/03/2017
• Est. Priority Date: 10/17/2011
• Status: Active Grant

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Nemoto, Naokazu, Toumura, Kunihiko, Haraguchi, Naoki
• Primary Examiner(s): Smithers, Matthew
• Application Number:
  US14/600,545
• Publication Number:
  US 20150134849A1
• Time in Patent Office: 714 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/14 Routing performance; Theoretical aspects
• CPC Class Codes: H04L 63/02 for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 67/01 Protocols

Abstract

A gateway device disposed at front stage before a server has a dispersion rule of data dispersed on server side and analyzes communication data to specify a server to be accessed finally, so that identification information of the specified server is added to packet option of IP layer to thereby omit higher-rank routing processing than IP layer of gateway devices on the way. Consequently, transfer processing of a gateway device at back stage can be performed at high speed and access passing through a network route intended by manager is possible.

Claims

1. A node in a network system, the node being coupled with other nodes, each node being one of a gateway device or a switch disposed between clients and servers of the network system,

the node being configured to send, according to a protocol processing, to another one of the nodes a message prepared;

the node being configured to;

process a first datagram including the message and one or more destination identification identifiers, to generate a second datagram including the message and being addressed to a second node by referring to one of the one or more destination identification identifiers;

send out the datagram generated,

wherein the one or more destination identification identifiers are configured to be set in accordance with a predetermined rule; and

record in the second datagram an identifier of the node as a track record.

2. The node according to claim 1, wherein the one or more identification identifiers are set in an order of the one or more of the nodes through which the message travels.

3. The node according to claim 2, further configured to refer, in generating the second datagram, the identifier first positioned in the one or more destination identification identifiers.

4. The node according to claim 1, wherein each of the identification identifiers is set with information used for judging whether or not the one or more destination identification identifiers are referred to.

5. The node according to claim 1, further configured to set in the second datagram the one or more destination identification identifiers in the first datagram without the identifier having been referred to in the node.

6. The node according to claim 1, further configured to delete, in generating the second datagram, the identifier referred to in the node from the one or more destination identification identifiers of the first datagram.

7. The node according to claim 1, further configured to obtain the identifier to be referred to stored in a header option of the first datagram.

8. The node according to claim 1, further configured to record in the second datagram an identifier of the node as a track record even when the one or more destination identification identifiers are not referred to.

9. The node according to claim 1, further configured to record the identifier of the node as the track record in the header option of the datagram.

10. The node according to claim 1, further configured to add the identifier thereof to the one or more identifiers recorded in an order of one or more of the nodes through which the message has passed.

11. The node according to claim 1, further configured to refer to, in case of processing the first datagram to generate the second datagram, the one or more destination identification identifiers, in case of being designated to refer to the one or more destination identification identifiers in the node.

12. The node according to claim 1,

wherein in case that a number of the destination identification identifiers to be generated is plural, each of the destination identification identifiers is generated in accordance with respective rules different from each other.

13. The node according to claim 1, wherein the destination identification identifiers are generated during the protocol processing.

14. The node according to claim 1, wherein the node is configured to define another node by the protocol processing in case that the destination identification identifier has not been included in a header of the datagram.

15. A node in a network system, the node being coupled with other nodes, each node being one of a gateway device or a switch disposed between clients and servers of the network system,

the node being configured to send, according to a protocol processing, to another one of the nodes a message prepared;

the node being configured to;

process a first datagram including the message and one or more destination identification identifiers, to generate a second datagram including the message and being addressed to a second node by referring to one of the one or more destination identification identifiers;

send out the datagram generated,

wherein the one or more destination identification identifiers are configured to be set in accordance with predetermined rule,

wherein the predetermined rule comprises a dispersion rule.