System and methods for providing multi-hop access in a communications network

FIELD OF INVENTION

0001The present invention relates to a system and method of providing a client access to a communications network through an authenticator in the communications network.

BACKGROUND OF THE INVENTION

0002The use of wireless communication devices has increased over the years. In present day communication networks, mobile devices such as PDAs, cellular phones and laptops need authentication before getting access to private databases or access to the Internet. Devices are authenticated through an Infrastructure Access Point (IAP), typically a base station, which is connected to an authentication server. The authentication request is transmitted using the Extensible authentication protocol (EAP) comprising of EAP over LAN (EAPOL) packets. The entire authentication process involves several EAPOL packets being transmitted and received, starting with an EAP Start packet and being completed with either an EAP Success message packet or an EAP Failure message packet. The authentication server stores the authentication credentials of the device (typically called a supplicant) that is being authenticated using the authentication server. Authentication servers can also be connected to other authentication servers to obtain authentication credentials of supplicants that are not stored locally.

0003In prior systems, a centralized approach is followed wherein a single IAP handles the authentication process of all supplicants within the range of the IAP. Since every supplicant can only be authenticated via the IAP, this method has several shortcomings. Prior systems which adhere to American National Standards Institute/Institute of Electrical and Electronics Engineers ANSI/IEEE 802.1X or ANSI/IEEE 802.11i standards utilize such a method. In such standards, the process of authentication of mobile devices is defined and the standards discuss a supplicant, an authenticator and an authentication server, where the authentication server authenticates a supplicant using an authenticator. The authentication server trusts the authenticator to forward correct authentication information received from the supplicant to the authentication server. However the authentication process as defined in the standards requires that the supplicant have a direct communication channel with the authenticator, and as such the standards do not support wireless multi-hop communications.

0004Since prior systems rely on a centralized approach and require a direct communication channel, there is a need for an improved system and method for providing multi-hop access.

BRIEF DESCRIPTION OF THE DIAGRAMS

0005The accompanying figures together with the detailed description below are incorporated in and form part of the specification, serve to further illustrate various embodiments and to explain various principles and advantages all in accordance with the present invention.

0006<figref idref="DRAWINGS">FIG. 1</figref> is a first embodiment showing a distributed approach in a wireless communications network.

0007<figref idref="DRAWINGS">FIG. 2</figref> is a second embodiment showing a flow chart of a method of providing access in a wireless communications network.

0008<figref idref="DRAWINGS">FIG. 3</figref> illustrates a process of creating a state at each authentication node in a relay chain pursuant to an embodiment of the invention.

0009<figref idref="DRAWINGS">FIG. 4</figref> shows a third embodiment for a method of providing mobility to a trusted supplicant, authenticated via an authenticator, in a wireless communications network

0010<figref idref="DRAWINGS">FIG. 5</figref> shows the third embodiment wherein the trusted supplicant seeks authentication after connecting to a second authenticator.

0011<figref idref="DRAWINGS">FIG. 6</figref> shows the embodiment of <figref idref="DRAWINGS">FIG. 4</figref> wherein the trusted supplicant becomes authenticated through the second authenticator.

0012<figref idref="DRAWINGS">FIG. 7</figref> shows an embodiment of <figref idref="DRAWINGS">FIG. 4</figref> wherein a pairwise master key is stored at selected nodes.

0013<figref idref="DRAWINGS">FIG. 8</figref> shows another method pursuant to an embodiment of the present invention.

0014<figref idref="DRAWINGS">FIG. 9</figref> is a flow chart of a method for providing mobility to a trusted supplicant described in the third embodiment.

DETAILED DESCRIPTION

0015The present invention may be embodied in several forms and manners. The description provided below and the drawings show exemplary embodiments of the invention. Those of skill in the art will appreciate that the invention may be embodied in other forms and manners not shown below. The invention shall have the full scope of the claims and shall not be limited by the embodiments shown below. It is further understood that the use of relational term, if any, such as first, second, top and bottom, front and rear and the like are used solely for distinguishing one entity or action from another, without necessarily requiring or implying any such actual relationship or order between such entities or actions.

0016<figref idref="DRAWINGS">FIG. 1</figref> illustrates a communications network comprising a supplicant <b>105</b>, an authenticator <b>110</b>, a prime authenticator <b>115</b>, node <b>130</b> and an authentication server <b>125</b>. The supplicant <b>105</b> sends an authentication request to the authenticator <b>110</b> where the authenticator forwards the authentication request towards a prime authenticator <b>115</b> by way of a relay. As used herein, the prime authenticator <b>115</b> is a fixed node that has a permanent security association with the authentication server <b>125</b>. As used herein, the authenticator <b>110</b> is a supplicant that has already been authenticated indirectly by the prime authenticator <b>115</b> and thus is now termed an authenticator. Node <b>130</b> is authenticator <b>110</b>'s authenticator. As shown in <figref idref="DRAWINGS">FIG. 1</figref>, the supplicant <b>105</b> has an indirect security association with the authentication server <b>125</b> where indirect means that the supplicant <b>105</b>'s security association is via at least one other node. In this case, the supplicant <b>105</b> has an indirect security association via node <b>130</b> and the prime authenticator <b>115</b>.

0017According to one embodiment, the supplicant <b>105</b> is authenticated via the authenticator <b>110</b> and once authenticated, is able to serve as an authenticator for other supplicants in the wireless communication network. As used herein, the authentication request is an authentication message transmitted from the supplicant <b>105</b> to the authenticator <b>110</b>. As used herein, the direction of sending a message from the supplicant to the authenticator towards the prime authenticator is inbound; whereas, the direction of sending a message from the prime authenticator towards the authenticator and supplicant is outbound. As is known to one of ordinary skill in the art, the authentication request can be sent as a Remote Authentication Dial In User Service (RADIUS) message, as an extensible authentication packet over LAN (EAPOL) Start message, or as another similar authentication protocol. Those skilled in the art shall appreciate that there are several protocols and messaging technologies that can be used to send and receive authentication requests and such protocols and messaging technologies are within the scope of the present invention.

0018In any case, the authentication request contains information that indicates that the supplicant is attempting to authenticate with the authentication server. In the EAPOL embodiment, the authentication process occurs over several EAPOL messages, starting with an EAPOL Start or an EAP Request/Identity message and completing with an EAPOL Success message (in the event of a success in authenticating the supplicant) or an EAPOL Failure message (in the event of a failure in authenticating the supplicant). Further, every authenticator can be configured to create such authentication requests and forward the authentication requests to the prime authenticator <b>115</b>. In any case, the authentication server stores the authentication credentials of the supplicant and uses the authentication credentials to validate the authentication request.

0019In one embodiment, the supplicant and the authenticators in the communication network are laptop computers. In such an embodiment, an Infrastructure Access Point (“IAP”) serves as a prime authenticator for authenticating the laptop computers in conjunction with an alternate authentication server (“AAA server”). For example, a police network may provide access to police infrastructure to several laptops owned by the police department in a wireless communication network. In conventional systems, each laptop owned by the police department would be authenticated via the IAP that may also be owned by the police department. However the present invention provides a method whereby each laptop that has already been authenticated by the communication network can also serve as an authenticator. In one embodiment, an authenticator, e.g. a supplicant that has an indirect security relationship with the authentication server via the prime authenticator, sends out an advertisement where any new laptop wanting to get access to the police infrastructure services can be authenticated via the authenticator instead of being authenticated directly through the IAP. The method of authenticating the supplicant via another authenticator is done by means of a relay where the authentication request is relayed towards the prime authenticator via the authenticator. As used herein, the prime authenticator is a fixed node that has a permanent security relationship with the authentication server and all authentication requests are routed through the prime authenticator to reach the authentication server.

0020In one embodiment, the system further comprises at least one other node, e.g. node <b>130</b>, between the authenticator <b>110</b> and the prime authenticator <b>115</b> where the node <b>130</b> functions to relay the authentication request to the prime authenticator <b>115</b>. In such an embodiment, node <b>130</b> is an intermediate device known as an authentication relay. As an authentication relay, the node can also serve as an authenticator. That is, a node that has been authenticated can behave as both an authenticator and a relay based on the configuration. In essence, the node that has been authenticated can exhibit two behaviors through the node's relationship with another node. Those two behaviors are as an authenticator and as a relay. For example, the prime authenticator <b>115</b> is an authenticated node which has been authenticated to the authentication server <b>125</b>. The relationship between the nodes is established through the inbound packets received from another node. First, an authenticated node knows that it is behaving as an authenticator to a supplicant node if the inbound packet is an EAPOL Start message where the EAPOL Start message has a transmitter address and a source address that are the same and/or the source address of the EAPOL Start message is in the authenticator's association table. In one embodiment, the authenticator's association table is updated when the authenticator receives an inbound or an outbound packet. In one embodiment, if a node behaves as an authenticator, it behaves according to ANSI/IEEE 802.11i's rules relating to authentication. Second, if the authenticated node receives an inbound EAPOL Start message from a node where the transmitter address is not equal to the source address and/or the source address of the EAPOL Start message is not in the authenticator's association table, the authenticated node knows that it needs to behave as a relay for that packet. Where the node behaves as a relay node, it updates the association table with the destination address, source address, transmitter address and receiver address for inbound and outbound EAPOL packets.

0021Once the authentication request reaches the prime authenticator <b>115</b>, the prime authenticator <b>115</b> forwards the authentication request to the authentication server <b>125</b>. In the EAPOL embodiment, the authentication process occurs over several EAPOL messages, starting with an EAPOL Start message or an EAP Request/Identity message and being completed with an EAPOL Success message (in the event of a success in authenticating the supplicant) or an EAPOL Failure message (in the event of a failure in authenticating the supplicant). Several packets comprising authentication information is relayed between the supplicant and the authentication server before the supplicant has been authenticated by the network. These packets comprise at least one of the packets described by the authentication processes defined authorized by ANSI/IEEE 802.1X.

0022The authentication information received from the authentication server <b>125</b> is sent to the prime authenticator <b>115</b>. The prime authenticator <b>115</b> then uses the same relay process used while sending the authentication request to the authentication server <b>125</b> in reverse. The prime authenticator <b>115</b> relays the authentication information to node <b>130</b> which in turn relays the authentication information back to the authenticator <b>110</b>. In the EAPOL embodiment, the authentication process is accomplished using several EAPOL messages that are relayed between the authentication server and the authenticator. The authenticator <b>110</b> then fulfills the authentication request using the authentication information.

0023As per one embodiment, the authentication information comprises a pairwise master key that is relayed from authentication server <b>125</b> back to the authenticator <b>110</b> by way of a relay. The pairwise master key is a unique key generated at the authentication server <b>125</b> corresponding to the supplicant <b>105</b>, for each authentication. Each supplicant has a unique pairwise master key generated at the authentication server <b>125</b> corresponding to each supplicant, during each authentication. The unique key is relayed back to the authenticator <b>110</b> corresponding to the supplicant <b>105</b> and used to fulfill the authentication request of the supplicant <b>105</b>.

0024According to an embodiment disclosed in <figref idref="DRAWINGS">FIG. 2</figref>, a method for providing a supplicant access to a communications network comprises an authenticator first receiving an authentication request from a supplicant, step <b>205</b>. Upon identifying the authenticator, the supplicant sends the authentication request to the authenticator. The authenticator creates a state on receiving the authentication request, step <b>210</b>. The state comprises information including the source address, transmitting address, destination address, receiver address and other details pertaining to the supplicant and the authentication request, step <b>220</b>, <b>225</b>. The state is used to identify nodes in the relay chain to send the authentication information during the outbound relay process e.g. when the authentication information is relayed from the prime authenticator towards the authenticator. As per another embodiment, the authenticator can be connected to the prime authenticator via at an authentication relay and hence the authentication request would need to be relayed via an authentication relay to reach the prime authenticator, step <b>230</b>. In this case, each authentication relay would create a state based on the authentication request. The prime authenticator relays authentication information to the authenticator, where the authenticator is an immediate node that sent the authentication request to the prime authenticator, step <b>232</b>. The authentication information is generated at the authentication server based on the authentication request received from the supplicant. The prime authenticator receives the authentication request and forwards the authentication request to the authentication server.

0025The authentication server generates authentication information corresponding to the supplicant and sends the authentication information to the prime authenticator. The authentication information comprises a pairwise master key unique to the supplicant that is generated by the authentication server corresponding to the supplicant. The prime authenticator relays the authentication information back to the authenticator, step <b>235</b>. The outbound relay process i.e. the relay from the prime authenticator towards the supplicant uses the state generated during the inbound relay process to identify the lower node to which the authentication information is to be sent. In one embodiment, where the authenticator is connected to the prime authenticator via at least one other authentication relay, the authentication information is relayed to the authenticator. The authenticator fulfills the authentication request using the pairwise master key received from the authentication server via the prime authenticator and authentication relay. In one embodiment, the authentication request is fulfilled using a four-way handshake process as specified in the ANSI/IEEE 802.1X standard. The result of a successful four-way handshake produces keys, at least one of which is used to encrypt/decrypt communications sent between the authenticator and supplicant. The system is capable of extending the function of the prime authenticator to other authenticated nodes in the wireless communications network by creating the state at each relay. The creation of the state at each authentication relay is further explained in with reference to <figref idref="DRAWINGS">FIG. 3</figref>.

0026<figref idref="DRAWINGS">FIG. 3</figref> shows a method by which authentication using a relay process is provided. As per one embodiment, a downstream relay is an inbound relay where nodes lower in the relay forward the authentication messages received from the supplicant <b>315</b> towards the prime authenticator <b>300</b>. The supplicant, which is an ordinary client, sends the authentication messages to the first authenticator <b>310</b>. An authenticator is a supplicant that has an indirect security relationship with the authentication server via the prime authenticator <b>300</b>. As shown in <figref idref="DRAWINGS">FIG. 3</figref>, the first authenticator <b>310</b> has been authenticated via a second authenticator <b>305</b> and hence has a secure relationship to the authentication server via the second authenticator <b>305</b> and prime authenticator <b>300</b>. The supplicant <b>315</b> first sends an authentication request to the first authenticator <b>310</b>. The authentication request being relayed between the first authenticator <b>310</b> and the prime authenticator <b>300</b> can be done using various methods. As mentioned above, the authentication request can be sent as a Remote Authentication Dial In User Service (RADIUS) message, as an extensible authentication packet over LAN (EAPOL) Start message, or as another similar authentication protocol. As per the EAPOL embodiment, the authentication request involves the use of WDS frame formats incorporated within an EAPOL message. The WDS frames append the source address, the destination address, the transmitting address and the receiver address to the packet. The first authenticator <b>310</b> receives the authentication request such as an EAPOL Start message and creates a state. The state comprises information including the source address, the destination address, the transmitting address and the receiver address. In the embodiment shown in <figref idref="DRAWINGS">FIG. 3</figref>, the state generated by the first authenticator <b>310</b> includes the source address and the transmitting address as that of the supplicant. The EAPOL packet is then relayed to the next hop in the downstream relay chain. The second authenticator <b>305</b> receives the authentication request from the first authenticator <b>310</b>. The second authenticator <b>305</b> also creates a state where the source address is that of the supplicant; however, the transmitting address is that of the first authenticator <b>310</b>. As used herein, the state comprises one element of a state address pairing table, where the element pairs each source address with a transmitter address. The state establishes a relation where the second authenticator knows the node that sent the second authenticator <b>305</b> the authentication request of the supplicant. It can use this relation to relay the authentication information received from the authentication server via the prime authenticator to the supplicant. The authentication request reaches the prime authenticator <b>300</b> where the prime authenticator creates a state. The source address is the address of the supplicant and the transmitting address is that of the second authenticator <b>305</b>. The authentication request is then forwarded to the authentication server for validation. As mentioned above, the prime authenticator <b>300</b> has a permanent security relationship with the authentication server using a virtual private network or similar such secure connection.

0027As used herein, an upstream relay is an outbound relay where the authentication information received from the authentication server is relayed back to the authenticator. As shown in <figref idref="DRAWINGS">FIG. 3</figref>, the prime authenticator <b>300</b> relays the authentication information received from the authentication server to the next hop, the second authenticator <b>305</b>, using the state created in the inbound relay. As per the example described above, the second authenticator <b>305</b> receives the EAPOL packet from the prime authenticator <b>300</b> and creates additional state where the authentication information is stored. The authentication information comprises a unique pairwise master key corresponding to the supplicant, timers and other such information. The second authenticator <b>305</b> identifies the first authenticator as the node that relayed the authentication request in the inbound relay and therefore, relays the authentication information to the first authenticator <b>310</b>. The second authenticator identifies which authenticator to send the authentication information to by first determining the destination address in the authentication information. Subsequently the second authenticator searches a state address pairing table. In one embodiment, the state address pairing table is created by inbound authentication requests. The second authenticator searches the state address pairing table for an element with a matching source address. Once this source address is found, the second authenticator finds the paired transmitter address which was initially extracted from the same inbound authentication request information. Having identified the source address and the transmitter address of the inbound authentication request in its state address pairing table, the second authenticator uses the source address as the destination address and the transmitter address as the receiver address for the outbound authentication information packet. Similarly, the first authenticator <b>310</b> receives the EAPOL packet from the second authenticator <b>305</b>, creates additional state and identifies the supplicant as the next node in the relay. At this point, the authentication information comprising the pairwise master is not sent to the supplicant. The first authenticator <b>310</b> uses this pairwise master key to authenticate the supplicant by way of a four-way handshake. The four-way handshake process uses a key generated by the supplicant <b>315</b> and the unique key received by the first authenticator <b>310</b> from the authentication server to authenticate the supplicant. However, those skilled in the art shall appreciate that other ways of creating such states to enable the relay process and identifying intermediate nodes through which the supplicant can establish a secure connection to the authentication server can also be used and these methods are within the scope of the present invention.

0028<figref idref="DRAWINGS">FIGS. 4, 5</figref>, <b>6</b>, <b>7</b> and <b>9</b>, depict a method of providing mobility to a trusted supplicant <b>405</b> authenticated via a first authenticator in a wireless communications network pursuant to an embodiment of the present invention. In one embodiment, as shown in <figref idref="DRAWINGS">FIG. 4</figref>, a trusted supplicant <b>405</b> is a node that has an established secure association with the authentication server <b>425</b>. The supplicant <b>405</b> is able to access the infrastructure or the database via the first authenticator <b>410</b>. The authentication process disclosed above in previous embodiments is used to establish this secure connection. However, in the case where the first authenticator <b>410</b> disconnects from the communication network or the trusted supplicant <b>405</b> travels outside the range of the first authenticator <b>410</b>, the trusted supplicant <b>405</b> needs to be re-authenticated via another trusted node in the communications network. As shown in <figref idref="DRAWINGS">FIGS. 4 and 9</figref>, the method includes first identifying a second authenticator <b>430</b> as per step <b>905</b>, wherein the second authenticator <b>430</b> and the first authenticator <b>410</b> have a security association with the authentication server via a third authenticator <b>420</b> where the third authenticator has a secure relationship with the authentication server <b>425</b> via a prime authenticator <b>415</b>. In one embodiment (not shown), there can be several other authenticators between the first authenticator <b>410</b> and the third authenticator <b>420</b>, or the second authenticator <b>430</b> and the third authenticator <b>420</b> or the third authenticator <b>420</b> and the prime authenticator <b>415</b>. An authenticator that is the first common node between the first authenticator <b>410</b> and second authenticator <b>430</b> serves as a node to provide authentication credentials to the second authenticator <b>430</b> to re-authenticate the supplicant <b>405</b>. When the trusted supplicant <b>405</b> reattaches to the second authenticator <b>430</b>, the trusted supplicant <b>405</b> still has its unique authentication key, but the second authenticator <b>430</b> does not, as shown in <figref idref="DRAWINGS">FIG. 5</figref>. As shown in <figref idref="DRAWINGS">FIG. 6</figref>, the trusted supplicant <b>405</b> initiates a full authentication process by transmitting an extensible application packet over LAN (EAPOL) start. The supplicant identifies the second authenticator <b>430</b> and sends an authentication request to the second authenticator <b>430</b>. The second authenticator <b>430</b> relays this authentication request towards the prime authenticator. However, the third authenticator <b>420</b> receives the authentication request in the relay and identifies the supplicant. The third authenticator <b>420</b> relays the unique key corresponding to the trusted supplicant <b>405</b>, as per step <b>910</b> back to the second authenticator. The third authenticator <b>420</b> identifies the supplicant based on the address of the supplicant <b>405</b> that had been previously stored by the third authenticator <b>420</b> during the authentication of the supplicant <b>405</b> by the first authenticator <b>410</b>. When the trusted supplicant <b>405</b> is being re-authenticated via the second authenticator <b>430</b>, the authentication request does not travel to the prime authenticator <b>415</b>. The third authenticator <b>420</b> is able to forward the authentication information corresponding to the trusted supplicant <b>405</b> directly to the second authenticator <b>430</b>. The second authenticator <b>430</b> obtains the unique key from the third authenticator <b>420</b> and authenticates the trusted supplicant <b>405</b> using the unique key as per step <b>915</b>. The re-authentication process is completed by way of the four-way handshake between the second trusted node and the trusted supplicant. This process provides increased mobility to a supplicant in the wireless communications network.

0029According to another embodiment, as shown in <figref idref="DRAWINGS">FIG. 7</figref>, the nodes can be configured such that the pair wise master key relayed during the authentication is stored only at select authenticators to authenticate the supplicant. For example, the pairwise master key can be stored only at the prime authenticator <b>415</b> and the first authenticator <b>410</b> when the supplicant is being authenticated via the first authenticator <b>410</b>. The pairwise master key is not stored at any of the intermediate authenticators such as <b>420</b>. Not storing the pairwise master key at intermediate authenticators increases the security within the system. However, the supplicant is not provided with the increased mobility provided in a previous embodiment. In the case where the authentication credentials are stored only at the first authenticator <b>410</b> and the prime authenticator <b>415</b>, the authentication request would need to be relayed to the prime authenticator <b>415</b> to obtain the authentication credentials i.e. the unique pairwise master key instead of the previous embodiment where the third authenticator <b>420</b> is able to relay the authentication information to the second authenticator <b>430</b>. The unique key is relayed to the second authenticator <b>430</b> and then used to complete the authentication process using a four-way handshake. However, this embodiment still prevents the need to contact the authentication server <b>425</b> again to obtain the authentication information pertaining to the trusted supplicant <b>405</b>. The delay caused due to the process of contacting the authentication server <b>425</b> is avoided and the prime authenticator <b>415</b> can relay the authentication credentials created at the time of authenticating the supplicant via the first authenticator <b>410</b>, directly to the second authenticator <b>430</b> for re-authentication.

0030Pursuant to one embodiment shown in <figref idref="DRAWINGS">FIG. 8</figref>, the pair wise master key is stored at selected authenticators. An authenticator node <b>935</b> can work in one of two modes, depending on the configuration. The authenticator <b>935</b> can allow traffic that authenticator <b>830</b> allows or force all authenticators below authenticators <b>830</b> to re-authenticate or all authenticators below and including <b>830</b> to reauthenticate.

0031This disclosure is intended to explain how to fashion and use various embodiments in accordance with the invention rather than to limit the true, intended and fair scope and spirit thereof. The foregoing discussion is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Modifications or variations are possible in the light of the above teachings. The embodiment(s) was chosen and described to provide the best illustration of the principles of the invention and practical application, and to enable one of ordinary skill in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. All such modifications and variations are within the scope of the invention as determined by the appended claims, as may be amended during the pendency of this application for patent, and all equivalents thereof, when interpreted in accordance with the breadth to which they are fairly, legally and equitably entitled.