Patent Grant
9065883
The present invention relates generally to an apparatus and a method for performing communication without stoppage using a different Internet Protocol version 6 (IPv6) address when connection using an IPv6 address fails in a communication apparatus which may use IPv6.
Unlike IPv4, in IPv6, one interface or each of a plurality of interfaces may have multiple IPv6 addresses. Also, a plurality of destination IPv6 addresses included in a Domain Name System (DNS) name query response message may be provided.
Unlike an IPv4 address system, since there exist a plurality of transmission IPv6 addresses at one node, and a plurality of destination IPv6 addresses at one node, there exist a problem of having to select a suitable transmission IPv6 address and a suitable destination IPv6 address for communication between a transmission node and a destination node.
To address this problem, Internet Engineering Task Force (IETF) suggests a transmission and destination address selection algorithm through a document Request For Comments (RFC) 3484.
The transmission and destination address selection algorithm of RFC 3484 uses following information in order to determine a couple of a transmission address and a destination address when there exit a plurality of transmission addresses and destination addresses.
First, an address range is classified into link-local, site-local, and global. An address state is classified into deprecated or not, and reachable or not. An address use purpose is classified into temporary or not. As an address prefix, a longest matching prefix is preferentially selected.
A high address precedence is preferentially selected. Regarding a label value, an address having the same label value is preferentially selected.
Referring to
In this case, for communication with a destination host 130, the transmission host 110 transmits a “DNS name query request” message to a DNS server 120 in order to determine the address of the destination host 130. The DNS server 120 responds following destination addresses using a “DNS name query response” message.
The transmission and destination address selection algorithm determines a following transmission-destination address couple with respect to the above transmission addresses and destination addresses.
After that, the transmission host 110 and the destination host 130 communicate with each other using the above-determined address couple.
In
However, generally, during an Internet access, when an access fails by a maximum frequency of retransmission, an Internet access failure occurs and an Internet access using the next address couple is not tried.
Also, even though the next address couple may be used when an Internet access using the first address pair fails in
Therefore, even when there exist useful addresses among transmission addresses not selected by the transmission and destination address selection algorithm, they are not used.
Referring to
A router 230 which connects the host A (210) with the host B (260) has two Network Interface Cards (NICs). An NIC1 supports ISATAP and IPv6, and an NIC2 supports IPv6.
Therefore, an IPv6/IPv4 network 200 may be used as a network between the host A (210) and the NIC1. That is, the host A (210) may transfer a packet to the host B (260) via the IPv6/IPv4 network 200 using an IPv6 address.
Also, the host A (210) may transfer an IPv6 packet encapsulated using IPv4 to the host B (260) by transmitting the IPv6 packet encapsulated using IPv4 through the IPv4 network 200 using the ISATAP interface of the router 230 which uses an IPv6 address.
An exemplary embodiment of the present invention assumes that the host A (210) and the host B (260) have the following address information.
Also, an exemplary embodiment of the present invention assumes that the host B (260) is operated as an Internet Information Service (IIS) server, and the host A (210) is connected to the host B (260) via an Internet web browser. Also, an exemplary embodiment of the present invention assumes that it has been confirmed that all addresses of the host A (210) and the host B (260) are valid addresses as a result of a ping test.
At this point, the address of the host A (210) is determined as “2001:1:2:0:200:f0ff:fe7a:5214” by the transmission and destination address selection algorithm. After that, communication using a transmission address (2001:1:2:0:200:f0ff:fe7a:5214) and a destination address (2001:3:4:5:1966:b2f1:475c:940c) is performed. A communication process is described below.
First, the host A (210) performs a connection to the host B (260). Also, during connection, the router 230 removes an IPv6 function at the NIC1 and leaves only the ISATAP router function. This is for realizing a failure of an IPv6 network.
After that, the host A (210) experiences a connection failure to the host B (260) (connection failure after connection is tried by a frequency of retransmission designated by TCP/UDP/IP).
After that, the host A (210) tries a connection to the host B (260) using the transmission and destination address selection algorithm, but the connection fails because the host A (210) tries a connection by selecting “2001:1:2:0:200:f0ff:fe7a:5214” as a transmission address.
As described in the above example, since “2001:1:2:0:200:f0ff:fe7a:5214” is non-deprecated, “2001:1:2:0:200:f0ff:fe7a:5214” is selected continuously by the transmission and destination address selection algorithm even though a connection fails.
In this case, if an ISATAP address (2001:DB8:0:7:0:5efe:192.168.1.10) were selected during a connection failure, connection would be performed successfully.
Consequently, when the transmission and destination address selection algorithm defined by the document RFC 3484 is used, a long transmission delay time due to a connection failure, and an inefficient address access may be generated.
An aspect of the present invention is to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below.
Accordingly an aspect of the present invention is to provide an apparatus and a method for setting a network address in a packet communication system.
Another aspect of the present invention is to provide an apparatus and a method for a support sub-layer, which may support TCP/UDP/IP and select a valid address from addresses not selected by a basic address selection algorithm.
Still another aspect of the present invention is to provide an apparatus and a method for addressing long delay time generated by retransmission when a connection fails, and maintaining an existing session.
According to an aspect of exemplary embodiments of the present invention, a connection method of a support sub-layer in a packet communication system is provided. The method includes: trying a first connection to a destination node using a first address set having a highest priority in an address management table; when the first connection fails, trying a second connection to the destination node in a pipeline manner on the basis of address sets inside the address management table; and generating valid address sets via the second connection.
According to another aspect of exemplary embodiments of the present invention, a connection method of a support sub-layer in a packet communication system is provided. The method includes: determining whether a timeout occurs while performing communication with a destination node; when the timeout occurs, trying a first connection to the destination node using a first address set having a highest priority in an address management table; when the first connection fails, trying a second connection to the destination node in a pipeline manner on the basis of address sets inside the address management table; and generating valid address sets via the second connection.
According to still another aspect of exemplary embodiments of the present invention, an apparatus of a support sub-layer in a packet communication system is provided. The apparatus includes: a communication module for communicating with a destination node; a controller for trying a first connection to the destination node using a first address set having a highest priority in an address management table through the communication module, when the first connection fails, trying a second connection to the destination node in a pipeline manner using address sets inside the address management table, and generating valid address sets via the second connection; and a storing unit for storing the address management table.
According to yet another aspect of exemplary embodiments of the present invention, an apparatus of a support sub-layer in a packet communication system is provided. The apparatus includes: a communication module for communicating with a destination node; a controller for determining whether a timeout occurs while performing communication with the destination node through the communication module, when the timeout occurs, trying a first connection to the destination node using a first address set having a highest priority in an address management table, when the first connection fails, trying a second connection to the destination node in a pipeline manner using address sets inside the address management table, and generating valid address sets via the second connection; and a storing unit for storing the address management table.
Other aspects, advantages and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention.
The above and other objects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings in which:
Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures.
The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein may be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness.
The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention are provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents.
It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.
By the term “substantially” it is meant that the recited characteristic, parameter, or value need not be achieved exactly, but that deviations or variations, including for example, tolerances, measurement error, measurement accuracy limitations and other factors known to skill in the art, may occur in amounts that do not preclude the effect the characteristic was intended to provide.
Exemplary embodiments of the present invention provide an apparatus and a method for setting a network address in a packet communication system.
The structure of a TCP/UDP/IP support sub-layer (310/320) is located between a transport layer and a network layer of an Open System Interface (OSI) 7 layer.
The TCP/UDP/IP support sub-layers 310 and 320 perform the following function.
First, the TCP/UDP/IP support sub-layers 310 and 320 manage and maintain addresses. The TCP/UDP/IP support sub-layers 310 and 320 manage and maintain addresses selected by an address selection algorithm defined in RFC 3484, and addresses not selected by the address selection algorithm. Also, the TCP/UDP/IP support sub-layers 310 and 320 use address management tables. To allow a valid address registered in the address management table to be selected when the address selection algorithm defined in RFC 3484 is executed, the TCP/UDP/IP support sub-layers 310 and 320 may change values such as precedence and an address state (for example, reachable-or-not) referred by the address selection algorithm when the address selection algorithm is executed. When data transmission using an address selected by the address selection algorithm of RFC 3484 fails, the precedence value of the relevant address is lowered. When the data transmission is successful, the precedence value of the relevant address is increased.
Also, when data transmission fails during a maximum frequency of retransmission defined by a TCP, an address state is changed (for example, unreachable, deprecated, etc.). When the address selection algorithm is executed again afterward, the address selection algorithm refers to the changed precedence value, address, and state information. Also, the address selection algorithm performs a pipeline-based efficient data transmission and valid address search function.
Referring to
First, a packet is transmitted using a first address set (S1, D1) determined by an upper layer. However, when there is no response during a timeout duration (step a), a packet is simultaneously transmitted using a second valid address set (S2, D2) in a pipeline manner during the next transmission (step b). In this case, the packet transmission using the first address set (S1, D1) is performed together.
Since there will exist a valid address set (Si, Di) within the maximum frequency of retransmission, when a previous address set (Si−1, Di−1) results in a transmission failure, simultaneous packet transmission is continuously performed in a pipeline manner. After that, a packet of transmitted packets which responds first is transferred to the upper layer. This is for fast transmission response.
Of address sets which have provided responses among all address sets transmitted during the same timeout duration, an address set having a highest priority is registered as a valid address set in an address management table. At this point, for a priority, an order determined by the address selection algorithm defined in RFC 3484 may be used.
For a valid address set (Si, Di) transmitted in a pipeline manner, an address set registered in the address management table may be used. Also, a determined valid address may be reflected to the address management table and an address swapping function which will be described later.
Referring to
When a packet is input from the upper layer, the support sub-layer 510 swaps an existing address set with a valid address set (Si, Di) and transfers the packet to the network layer until the upper layer terminates the opened session.
Also, when a response packet having a valid address set (Si, Di) is input from the network layer, the support sub-layer 510 swaps the address with the existing address set again, and transfers the packet to the upper layer.
By doing so, a session may be maintained. That is, generally, when a connection fails, a session is disconnected, but according to an exemplary embodiment of the present invention, a session may be maintained using an address swapping function.
Therefore, the support sub-layer 510 may provide a transparent packet transmission function between the transport layer and the network layer. Also, this function cooperates with a pipeline function to support an efficient packet transfer using session maintenance, packet delay time reduction, and packet transmission rate improvement.
Referring to
After that, when the connection tried using the address (S2, D2) is successful, the address set (S2, D2) becomes a valid address set.
When there exists a session connected using an existing address set (S1, D1), the address set (S1, D1) is swapped into the address set (S2, D2) by the TCP/UDP/IP support sub-layer. Also, an address management table is changed as in Table 1.
After that, a session to be newly connected may succeed by trying a connection using the address set (S1, D1) of Table 1 changed according to priority of an address management table.
Referring to
In step 720, the transmission node generates address sets using the transmission and destination address selection algorithm defined in RFC 3484 with respect to a plurality of transmission addresses and destination addresses. Also, the transmission node registers the addresses in an address management table.
In step 730, the transmission node tries a connection to the destination node using an address set (S1, D1) having a highest priority of the address sets generated by the transmission and destination address selection algorithm.
When a TCP/UDP/IP support sub-layer fails in connection at a first connection try in step 740, the TCP/UDP/IP support sub-layer tries a second connection. During the second connection try, the TCP/UDP/IP support sub-layer tries a connection using an address set (S2, D2) having the next priority in a pipeline manner (step 750). When the TCP/UDP/IP support sub-layer fails in connection at the second connection try and there exists a valid address set, the TCP/UDP/IP support sub-layer retries a connection in a pipeline manner within a maximum frequency of TCP retransmission.
In step 760, during the retry process, the TCP/UDP/IP support sub-layer determines address sets having high priorities as valid address sets (Svalid, Dvalid) with respect to address sets which have provided successful responses among tried address sets. The TCP/UDP/IP support sub-layer provides a packet received via the valid address set (Svalid, Dvalid) to an upper layer.
At this point, when the valid address set (Svalid, Dvalid) is different from an address set (S1, D1) which has been used by the upper layer (step 770), the TCP/UDP/IP support sub-layer communicates using the above-described swapping function (step 780). After that, the TCP/UDP/IP support sub-layer updates reference variables (precedence value, label value, and address state) for the valid address set (Svalid, Dvalid), and registers the same in an address management table.
The swapping function denotes that in the case where the TCP/UDP/IP support sub-layer performs packet transmission/reception via a connected session, the TCP/UDP/IP support sub-layer swaps the address set (S1, D1) tried by the upper layer into the address set (Svalid, Dvalid), and transfers a packet to a network layer, and swaps an address set (Svalid, Dvalid) from the network layer into the address set (S1, D1) to perform packet transmission/reception. By doing so, transparent packet transmission/reception and session maintenance may be accomplished.
After a session terminates, when performing a new session connection during a normal operation, the TCP/UDP/IP support sub-layer may newly generate address sets by executing the transmission and destination address selection algorithm defined in RFC 3484 on the basis of changed address information.
When the TCP/UDP/IP support sub-layer succeeds in connection at a first connection try in step 740, or when the valid address set (Svalid, Dvalid) is the same as the address set (S1, D1) which has been used for a connection try by the upper layer in step 770, the TCP/UDP/IP support sub-layer performs general communication (step 790).
After that, the algorithm according to an exemplary embodiment of the present invention is ended.
Referring to
When timeout occurs during communication in step 820, a TCP/UDP/IP support sub-layer of the transmission node tries a connection using an address set (S2, D2) having the next priority in a pipeline manner (step 830). When timeout occurs and there exists a valid address set, the TCP/UDP/IP support sub-layer retries a connection in a pipeline manner within a maximum frequency of TCP retransmission.
In step 840, with respect to address sets which have provided successful responses among connection-tried address sets, the TCP/UDP/IP support sub-layer determines address sets having high priorities as valid address sets (Svalid, Dvalid).
At this point, when the valid address set (Svalid, Dvalid) is different from an address set (S1, D1) which has been used for a connection try by an upper layer in step 850, the TCP/UDP/IP support sub-layer communicates using a swapping function defined by the TCP/UDP/IP support sub-layer (step 860).
After that, the TCP/UDP/IP support sub-layer updates reference variables (precedence value, label value, and address state) for the valid address set (Svalid, Dvalid), and registers the same in an address management table.
The swapping function denotes that in the case where the TCP/UDP/IP support sub-layer performs packet transmission/reception via a connected session, the TCP/UDP/IP support sub-layer swaps the address set (S1, D1) tried by the upper layer into the address set (Svalid, Dvalid), and transfers a packet to a network layer, and swaps an address set (Svalid, Dvalid) from the network layer into the address set (S1, D1) to perform packet transmission/reception. By doing so, transparent packet transmission/reception and session maintenance may be accomplished.
After a session terminates, when performing a new session connection during a normal operation, the TCP/UDP/IP support sub-layer may newly generate address sets by executing the transmission and destination address selection algorithm defined in RFC 3484 on the basis of changed address information.
When the timeout does not occur in step 820, or when the valid address set (Svalid, Dvalid) is the same as the address set (S1, D1) which has been used for a connection try by the upper layer in step 850, the TCP/UDP/IP support sub-layer of the transmission node performs general communication (step 870).
After that, the algorithm according to an exemplary embodiment of the present invention is ended.
Of address sets generated in the address management table, only basically valid addresses become objects of the address management table, and address sets generated by the transmission and destination address selection algorithm defined in RFC 3484 may be preferentially registered in the address management table. Also, valid addresses having matching ranges (link-local or site-local or global) though they are not selected by the transmission and destination address selection algorithm defined in RFC 3484 are registered in the address management table. A related example is provided below.
In the case where transmission address={Sa, Sb, Sc, Sd}, destination address={Da, Db}, global address={Sa, Sb, Da} (priority: Sa>Sb), and site-local address={Sc, Sd, Db} (priority: Sc>Sd), address sets selected by the transmission and destination address selection algorithm become (Sc, Db) and (Sa, Da).
Here, a generated address management table is given as in Table 2.
Assuming that (Si, Di) is an address set of Table 2, i is a priority number. That is, address sets become (S1, D1), (S2, D2), (S3, D3), and (S4, D4).
A case where the function of the TCP/UDP/IP support sub-layer according to an exemplary embodiment of the present invention is applied to the case of
When the TCP/UDP/IP support sub-layer is applied to
When the TCP/UDP/IP support sub-layer is applied to the same test scenario applied to
Referring to
The communication module 910 serves as a module for communicating with a different node, particularly, a destination node. In the case where the apparatus uses wireless communication, the communication module 910 includes a Radio Frequency (RF) processor and an RF baseband processor. The RF processor converts a signal received via an antenna to a baseband signal and provides the baseband signal to the RF baseband processor. Also, the RF processor converts a baseband signal from the baseband processor to an RF signal so that the RF signal may be transmitted on an actual RF path, and transmits the RF signal via the antenna.
In the case where the apparatus uses wired communication, the communication module 910 includes a wired processor and a wired baseband processor. The wired processor converts a signal received via a wired path to a baseband signal and provides the baseband signal to the wired baseband processor. Also, the wired processor converts a signal from the wired baseband processor to a wired signal so that the wired signal may be transmitted on an actual wired path, and transmits the wired signal via the wired path.
The controller 920 controls an overall operation of the apparatus. Particularly, the controller 920 controls the address manager 940 according to an exemplary embodiment of the present invention.
The storing unit 930 stores a program for controlling an overall operation of the apparatus, and temporary data generated while a program is executed. Particularly, the storing unit 930 stores an address management table according to an exemplary embodiment of the present invention.
The address manager 940 performs the above-described function of the TCP/UDP/IP support sub-layer. Though not shown, the rest of layers may exist separately, or the controller 920 may perform all or some of functions of the rest of the layers.
The address manager 940 performs the following function during connection.
The address manager 940 performs a DNS query process in order to perform an initial connection. Also, the transmission node generates address sets using the transmission and destination address selection algorithm defined in RFC 3484 with respect to a plurality of transmission addresses and destination addresses, and registers the addresses in an address management table.
The address manager 940 tries a connection using an address set (S1, D1) having a highest priority among address sets generated by the transmission and destination address selection algorithm. When a first connection try fails, the address manager 940 tries a second connection. During the second connection try, the address manager 940 tries a connection using an address set (S2, D2) having the next priority in a pipeline manner. When the second connection try fails and there exists a valid address set, the address manager 940 retries a connection in a pipeline manner within a maximum frequency of TCP retransmission.
During the retry process, the address manager 940 determines address sets having high priorities as valid address sets (Svalid, Dvalid) with respect to address sets which have provided successful responses among tried address sets. Also, the address manager 940 provides a packet received via the valid address set (Svalid, Dvalid) to an upper layer.
At this point, when the valid address set (Svalid, Dvalid) is different from the address set (S1, D1) which has been used for a connection try by the upper layer, the address manager 940 communicates using the above-described swapping function, updates reference variables (precedence value, label value, and address state) for the valid address set (Svalid, Dvalid), and registers the same in the address management table.
After a session terminates, when opening a new session and trying a connection during a normal operation, the address manager 940 may newly generate address sets by executing the transmission and destination address selection algorithm defined in RFC 3484 on the basis of changed address information.
When the address manager 940 succeeds in connection at a first connection try, or when the valid address set (Svalid, Dvalid) is the same as the address set (S1, D1) which has been used for a connection try by the upper layer, the address manager 940 performs general communication.
The address manager 940 performs the following function during communication.
When timeout occurs during communication, the address manager 940 tries a connection using an address set (S2, D2) having the next priority in a pipeline manner. When the timeout occurs and there exists a valid address, the address manager 940 retries a connection in a pipeline manner within a maximum frequency of TCP retransmission.
The address manager 940 determines address sets having high priorities as valid address sets (Svalid, Dvalid) with respect to address sets which have provided successful responses among connection-tried address sets. At this point, when the valid address set (Svalid, Dvalid) is different from the address set (S1, D1) which has been used for a connection try by the upper layer, the address manager 940 communicates using the defined swapping function.
The address manager 940 updates reference variables (precedence value, label value, and address state) for the valid address set (Svalid, Dvalid), and registers the same in the address management table.
After a session terminates, when opening a new session and trying a connection during a normal operation, the address manager 940 may newly generate address sets by executing the transmission and destination address selection algorithm defined in RFC 3484 on the basis of changed address information.
When the timeout does not occur, or when the valid address set (Svalid, Dvalid) is the same as the address set (S1, D1) which has been used for a connection try by the upper layer, the address manger 940 performs general communication.
In the above-described block diagram, the controller 920 may perform the function of the address manager 940. Separate configuration and illustration of the address manager 940 in an exemplary embodiment of the present invention is for separately describing each function.
Therefore, in actual realization of a product, all or some of the functions of the address manager 940 may be processed by the controller 920.
An exemplary embodiment of the present invention may a long transmission delay time generated due to retransmission when connection fails, increase a packet transmission rate by improving connection ability through valid address management and efficient address access, and maintain a session.
Although the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents. Therefore, the scope of the present invention should not be limited to the above-described embodiments but should be determined by not only the appended claims but also the equivalents thereof.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2008-0052394 | Jun 2008 | KR | national |
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/KR2009/002983 | 6/4/2009 | WO | 00 | 11/26/2010 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2009/148274 | 12/10/2009 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 4680753 | Fulton et al. | Jul 1987 | A |
| 5903559 | Acharya et al. | May 1999 | A |
| 5933490 | White et al. | Aug 1999 | A |
| 6118784 | Tsuchiya et al. | Sep 2000 | A |
| 6813243 | Epps et al. | Nov 2004 | B1 |
| 6968553 | Theeten | Nov 2005 | B1 |
| 7333510 | Hies et al. | Feb 2008 | B1 |
| 7716370 | Devarapalli | May 2010 | B1 |
| 7746858 | Boers et al. | Jun 2010 | B2 |
| 7769017 | Sylvain | Aug 2010 | B2 |
| 8166126 | Bristow et al. | Apr 2012 | B2 |
| 20030005100 | Barnard et al. | Jan 2003 | A1 |
| 20030061376 | Li et al. | Mar 2003 | A1 |
| 20030088701 | Mross | May 2003 | A1 |
| 20040015728 | Cole et al. | Jan 2004 | A1 |
| 20040037297 | Ishida et al. | Feb 2004 | A1 |
| 20040059822 | Jiang et al. | Mar 2004 | A1 |
| 20040143579 | Nakazawa | Jul 2004 | A1 |
| 20040221207 | Yokota et al. | Nov 2004 | A1 |
| 20050002339 | Patil et al. | Jan 2005 | A1 |
| 20050050148 | Mohammadioun et al. | Mar 2005 | A1 |
| 20050220094 | Parker et al. | Oct 2005 | A1 |
| 20060018301 | Schrufer | Jan 2006 | A1 |
| 20060056386 | Stogel | Mar 2006 | A1 |
| 20070011326 | Ohara | Jan 2007 | A1 |
| 20070025270 | Sylvain | Feb 2007 | A1 |
| 20070154005 | Daigle | Jul 2007 | A1 |
| 20080069137 | Jimmei | Mar 2008 | A1 |
| 20090006648 | Gopalakrishnan et al. | Jan 2009 | A1 |
| 20090080335 | Siminoff | Mar 2009 | A1 |
| 20090216497 | Schwiers et al. | Aug 2009 | A1 |
| 20100115106 | Moriwaki et al. | May 2010 | A1 |
| 20130016628 | Bertani et al. | Jan 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 10-0776817 | Aug 2007 | KR |
| Entry |
|---|
| RD 466,106 “Automated re-connection for a network device which has no console device, during network configuration”, disclosed by IBM Corp., published in the Feb. 2003. |
| Number | Date | Country | |
|---|---|---|---|
| 20110075551 A1 | Mar 2011 | US |
