Certificate based authentication authorization accounting scheme for loose coupling interworking

[0001] 1. Field of the Invention

[0002] The present invention generally relates to networking and, more particularly, to a certificate based Authentication Authorization and Accounting (AAA) scheme for loose coupling interworking between two different access networks.

[0003] 2. Related Art

[0004] Typically, Authentication, Authorization and Accounting (AAA) are required to access and utilize networks such as cellular networks and Wireless Local Area Networks (WLANs). However, the implementing of AAA can be difficult as well as requiring additional software and/or hardware in the case of interworking between two different radio access networks that do not belong to the same administrative domain and do not share the same AAA schemes.

[0005] There are two main types of interworking between cellular networks and WLANs: tight coupling and loose coupling. In a loose coupling scenario, the WLAN and the cellular network have independent data paths but the AAA for WLAN users relies on cellular network AAA functions. However, the cellular network AAA protocols (MAP/SS7) are incompatible with Internet Protocol (IP) based protocols used by WLAN users. Two approaches have been proposed. In the first approach, an AAA interface is provided in the cellular network Home Location Register (HLR). This requires either duplicating HLR data or providing a protocol converter between Radius/Diameter and MAP. In the second approach, if the Mobile Terminal (MT) uses a Subscriber Identity Module (SIM) card based authentication mechanism (e.g., NOKIA's wireless operator LAN), then the AAA will follow the cellular procedure. An AAA InterWorking Function (IWF) is necessary to interface with the HLR and an MT. Functionality wise, it is similar to a Serving GPRS (General Packet Radio Service) Support Node (SGSN) or Mobile Switching Center (MSC) from the AAA perspective except AAA traffic is carried through IP.

[0006] With both approaches, special interworking functions or gateways need to be deployed by the cellular operators. With the second approach, users are required to have a SIM card for WLAN access, but most WLAN users do not have SIM cards available on their laptops or Personal Digital Assistants (PDAs).

[0007] Accordingly, it would be desirable and highly advantageous to have an Authentication Authorization and Accounting (AAA) scheme for the case of interworking between two different networks that do not belong to the same administrative domain and do not share the same AAA schemes, where the AAA scheme does not require the deployment of a special interworking function to bridge between the two different types of networks.

[0008] The problems stated above, as well as other related problems of the prior art, are solved by the present invention, a certificate based Authentication, Authorization and Accounting (AAA) scheme for an interworking between different access networks.

[0009] Advantageously, the present invention can operate without interaction with the cellular core network during authentication. Compared with existing schemes, the proposed scheme does not require the cellular operators to adapt their Home Location Register (HLR) interfaces to provide authentication for WLAN users through Internet protocols.

[0010] According to an aspect of the present invention, there is provided a method for Authentication Authorization and Accounting (AAA) in an interworking between at least two networks. The at least two networks include a first network and a second network. A user of the first network is verified based on a certificate, by the second network. A session key is sent from the second network to a mobile device of the user when the user is verified. The session key is used for encrypting communication between the mobile device and the second network.

[0011] These and other aspects, features and advantages of the present invention will become apparent from the following detailed description of preferred embodiments, which is to be read in connection with the accompanying drawings.

[0012] FIG. 1 is a block diagram illustrating a computer system 100 to which the present invention may be applied, according to an illustrative embodiment of the present invention;

[0013] FIG. 2 is a block diagram illustrating a combination of access networks to which the present invention may be applied, according to an illustrative embodiment of the present invention;

[0014] FIG. 3 is a flow chart illustrating a certificate based method for Authentication Authorization and Accounting (AAA) of a mobile user in a loose coupling interworking between access networks, according to an illustrative embodiment of the present invention; and

[0015] FIG. 4 is a flow chart illustrating a certificate based method for Authentication Authorization and Accounting (AAA) of a mobile user in a loose coupling interworking between access networks, according to another illustrative embodiment of the present invention.

[0016] The present invention is directed to a certificate based Authentication Authorization and Accounting (AAA) scheme for loose coupling interworking. It is to be appreciated that the present invention is applicable to any combination of access networks (such as, e.g., an interworking between a Community Access Television (CATV) network and a Wireless Local Area Network (WLAN)). However, the present invention is particularly applicable to a cellular network and WLAN in a loose interworking arrangement.

[0017] It is to be understood that the present invention may be implemented in various forms of hardware, software, firmware, special purpose processors, or a combination thereof, for example, within a mobile terminal, access point, or a cellular network. Preferably, the present invention is implemented as a combination of hardware and software. Moreover, the software is preferably implemented as an application program tangibly embodied on a program storage device. The application program may be uploaded to, and executed by, a machine comprising any suitable architecture. Preferably, the machine is implemented on a computer platform having hardware such as one or more central processing units (CPU), a random access memory (RAM), and input/output (I/O) interface(s). The computer platform also includes an operating system and microinstruction code. The various processes and functions described herein may either be part of the microinstruction code or part of the application program (or a combination thereof), which is executed via the operating system. In addition, various other peripheral devices may be connected to the computer platform such as an additional data storage device and a printing device.

[0018] It is to be further understood that, because some of the constituent system components and method steps depicted in the accompanying Figures are preferably implemented in software, the actual connections between the system components (or the process steps) may differ depending upon the manner in which the present invention is programmed. Given the teachings herein, one of ordinary skill in the related art will be able to contemplate these and similar implementations or configurations of the present invention.

[0019] FIG. 1 is a block diagram illustrating a computer system 100 to which the present invention may be applied, according to an illustrative embodiment of the present invention. The computer processing system 100 may be embodied in a mobile device used to access a cellular network or a WLAN. The computer processing system 100 includes at least one processor (CPU) 102 operatively coupled to other components via a system bus 104. A read only memory (ROM) 106, a random access memory (RAM) 108, a display adapter 110, an I/O adapter 112, a user interface adapter 114, a sound adapter 199, and a network adapter 198, are operatively coupled to the system bus 104.

[0020] A display device 116 is operatively coupled to system bus 104 by display adapter 110. A disk storage device (e.g., a magnetic or optical disk storage device) 118 is operatively coupled to system bus 104 by I/O adapter 112. A mouse 120 and keyboard 122 are operatively coupled to system bus 104 by user interface adapter 114. The mouse 120 and keyboard 122 are used to input and output information to and from system 100.

[0021] At least one speaker (herein after “speaker”) 197 is operatively coupled to system bus 104 by sound adapter 199.

[0022] A (digital and/or analog) modem 196 is operatively coupled to system bus 104 by network adapter 198.

[0023] FIG. 2 is a block diagram illustrating a combination of access networks to which the present invention may be applied, according to an illustrative embodiment of the present invention. In the illustrative embodiment of FIG. 2, the combination of access networks includes a cellular network 210 and three Wireless Local Area Network (WLAN) 220a, 220b, and 220c. Mobile terminal 200, cellular network 210 and WLANs 220 may communicate with each other as indicated. The present invention provides a certificate based scheme to provide MA services to WLAN users. As noted above, the present invention may be applied to any combination of networks, including different numbers and different types of networks.

[0024] FIG. 3 is a flow diagram illustrating a certificate based method for Authentication Authorization and Accounting (MA) of a mobile user in a loose coupling interworking between access networks, according to an illustrative embodiment of the present invention. The access networks include a cellular network and a Wireless Local Area Network (WLAN), such as those shown in FIG. 2. The cellular network is associated with at least a mobile user. It is to be appreciated that while the illustrative embodiment of FIG. 3 (as well as the illustrative embodiment of FIG. 4 below) is described with respect to a cellular network and a WLAN, any combination of networks, including the preceding and other types of networks as well as different numbers of networks, may be readily employed in accordance with the present invention while maintaining the spirit and scope of the present invention.

[0025] Initially, a public key K_pub—cn associated with the cellular network is sent from the cellular network to the WLAN, which has an interworking contract with the cellular network (step 310). In the event that the cellular network has an interworking contract with more than one WLAN, then the cellular network could send the cellular network public key K_pub—cn to all of the WLANs with which it has a contract. It is preferable, but not mandatory, that the cellular network public key K_pub—cn is distributed through a secure channel so that the recipient WLAN can be sure that K_pub—cn is indeed a valid public key associated with the cellular network.

[0026] A certificate is then sent from the cellular network to the mobile user (step 315). The certificate includes, but is not limited to, the following: public key K_pub—u associated with the mobile user; ID of cellular network; subscription level of the mobile user, for example, whether the mobile user has subscribed for WLAN service, for authorization/verification purposes; expiration time of the certificate; and ID of the mobile user. The certificate is signed with a private key K_pri—cn of the cellular network. It is preferable, but not mandatory, that the certificate is sent to the mobile user when the mobile user signs up with the cellular network for WLAN interworking service.

[0027] The various keys and the certificate are used as follows. When the mobiel user moves into an area under WLAN coverage, the certificate is sent from the mobile user to the WLAN (step 320). The WLAN then: checks the ID of the cellular network included in the certificate (step 325); checks the ID of the mobile user included in the certificate (e.g., for an authorization/verification purpose(s)) (step 327); verifies the authenticity of the certificate using the public key K_pub—cn of the cellular network (step 330); upon verification, computes a session key for the mobile user that is encrypted with a public key K_pub—u of the mobile user that was included in the certificate (step 335); and sends the session key to the mobile user (step 340). The session key may be, but is not limited to, a per user Wired Equivalent Privacy (WEP) key.

[0028] Upon receiving the session key, the mobile user decrypts the session key using his/her private key K_pri—u (step 345) and communicates with the WLAN using the session key (i.e., all subsequent communication between the mobile device and the WLAN is encrypted with the session key) (step 350). Thus, the mobile user is authenticated by the WLAN since only that specific mobile user has the necessary private key K_pri—u to decrypt the session key.

[0029] FIG. 4 is a flow diagram illustrating a certificate based method for Authentication Authorization and Accounting (AAA) of a mobile user in a loose coupling interworking between access networks, according to another illustrative embodiment of the present invention. The access networks include a cellular network and a Wireless Local Area Network (WLAN). The cellular network is associated with at least a mobile user. The method of FIG. 4 allows for mutual authentication between the mobile user and the WLAN, so that the mobile user can also verify that he/she is indeed communicating with a legitimate WLAN (to prevent, e.g., messages from being snooped).

[0030] A public key K_pub—on of the cellular network is sent from the cellular network to the WLAN, which has an interworking contract with the cellular network (step 310). In the event that the cellular network has an interworking contract with more than one WLAN, then the cellular network could send the public key K_pub—cn of the cellular network to all of these WLANs. It is preferable, but not mandatory, that the public key K_pub—cn is distributed through a secure channel so that the WLAN can be sure that K_pub—cn is indeed the public key of the cellular network.

[0031] The public key K_pub—cn of the cellular network is also sent from the cellular network to the mobile user (step 412).

[0032] A first certificate is sent from the cellular network to the mobile user (step 315). The first certificate includes, but is not limited to, the following: public key K_pub—u of the mobile user; ID of cellular network; subscription level of the mobile user (whether the mobile user has subscribed for WLAN service); expiration time of the first certificate; and ID of mobile user. The first certificate is signed with a private key K_pri—cn of the cellular network. It is preferable, but not mandatory, that the first certificate is sent to the mobile user when the mobile user signs up with the cellular network for WLAN interworking service.

[0033] A second certificate is also sent from the cellular network to each WLAN (that has a contract agreement with the cellular network) (step 417). The second certificate includes, but is not limited to, a public key K_pub—w of the WLAN. The second certificate is signed with the private key K_pri—cn of the cellular network.

[0034] The first certificate is sent from the mobile user to the WLAN (e.g., an Access Point (AP) or other entity), e.g., when the mobile user moves into an area under WLAN coverage (step 320). In response, the WLAN checks the ID of the cellular network included in the first certificate (step 325), checks the ID of the mobile user included in the first certificate (e.g., for an authorization/verification purpose(s)) (step 327), and verifies the authenticity of the first certificate using the public key K_pub—cn of the cellular network (step 330). Upon verification, the WLAN computes a session key for the mobile user that is encrypted with the public key K_pub—u of the mobile user (that was included in the first certificate) and that is signed with the private key K_pri—w of the WLAN (step 435), and sends the session key and the second certificate to the mobile user (step 440). The session key may be, but is not limited to, a per user Wired Equivalent Privacy (WEP) key.

[0035] Upon receiving the session key and the second certificate, the mobile user verifies that the second certificate is valid using the public key K_pub—cn of the cellular network (step 441). If it is valid, then the public key K_pub—w of the WLAN is extracted from the second certificate (step 442). The mobile user then verifies that the session key actually comes from the WLAN by using the public key K_pub—w of the WLAN to verify the signature on the session key (step 443). If the encrypted session key is verified to come from the WLAN, the mobile user then decrypts the session key using his/her private key K_pri—u (step 345) and communicates with the WLAN using the session key. All subsequent communication between the mobile device and the WLAN is encrypted with the session key starts using the session key for communicating with the WLAN (step 350).

[0036] Thus, a primary advantage of the present invention as compared with the prior art is that the present invention does not require any physical interworking functions in order for the WLAN to interact with the cellular network for the purpose of user authentication. In fact, by using certificates, the WLANs do not need any interaction with the cellular network at the time the mobile terminal requests access to the network in order to grant user access. Since the certificate includes the identity of the mobile user, accounting functions can be easily performed using this information, including the user identity.

[0037] Although the illustrative embodiments have been described herein with reference to the accompanying drawings, it is to be understood that the present invention is not limited to those precise embodiments, and that various other changes and modifications may be affected therein by one skilled in the art without departing from the scope or spirit of the invention. All such changes and modifications are intended to be included within the scope of the invention as defined by the appended claims.