1. Technical Field
Embodiments of the present disclosure relate to security authentication technology, and particularly to a Femto access point (AP) and method for reducing authentication time of a user equipment (UE) in an Internet Protocol multimedia subsystem (IMS) network using the Femto-AP.
2. Description of Related Art
Currently, there is no standard user equipment (UE) authentication process in the Internet Protocol multimedia subsystem network (IMS network) using Femto-AP (i.e., Femtocell-AP). Authentication between the UE and an authentication, authorization, and accounting (AAA) server is performed using an extensible authentication protocol-authentication and key agreement (EAP-AKA) mechanism. However, under the EAP-AKA authentication mechanism, a secure channel between the UE and the AAA server must be established before the authentication starts every time. Therefore, an improved method for performing the UE authentication with the AAA server in the IMS network is desired.
All of the processes described below may be embodied in, and fully automated via, functional code modules executed by one or more general purpose computers or processors. The code modules may be stored in any type of non-transitory readable medium or other storage device. Some or all of the methods may alternatively be embodied in specialized hardware. Depending on the embodiment, the non-transitory readable medium may be a hard disk drive, a compact disc, a digital video disc, or a tape drive.
In some embodiments, the UE authentication system 212 may include one or more modules. The one or more modules are stored in the storage device 21 and configured for execution by the one or more processors (only one processor 23 is shown in
In block S1, the Femto-AP 2 establishes a secure channel between the Femto-AP 2 and the gateway 3 using a private key of the Femto-AP 2. In some embodiments, the private key is stored in the USIM 22 of the Femto-AP 2, and the secure channel is the security architecture for IP network (IPsec) channel.
In block S2, the Femto-AP 2 performs a Femto-AP authentication with the AAA server 4 through the secure channel, and obtains a plurality of virtual Internet Protocol (IP) addresses from the AAA server 4. In some embodiments, the virtual IP addresses may be 10.0.0.1/30.
In block S3, the Femto-AP 2 receives an authentication request from the UE 1. As shown in
In block S4, the Femto-AP 2 determines if the UE 1 is a designated equipment in the whitelist 210. If the UE 1 is the designated equipment in the whitelist 210, the procedure goes to block S5. If the UE 1 is not the designated equipment in the whitelist 210, the procedure ends. In some embodiments, the designated equipment is a qualified equipment which is provided a particular service by the Femto-AP 2
In block S5, the Femto-AP 2 controls the UE 1 to perform an UE authentication with the AAA server 4 through the secure channel. In some embodiments, the UE authentication with the AAA server 4 is performed using an extensible authentication protocol-authentication and key agreement (EAP-AKA) mechanism. A detailed description of block S5 refers to
In block S6, the Femto-AP 2 assigns one of the plurality of virtual IP addresses to the UE 1 to register the UE 1 in the IMS server 5 upon the condition that the UE authentication is completed and the UE 1 needs virtual IP address for data access. In some embodiments, the register operation between the UE 1 and the IMS server 5 is performed using an session initiation protocol (SIP) mechanism. In other embodiments, the block S6 may be deleted upon the condition that the UE does not need virtual IP address for data access.
Because the UE 1 uses a pr-established secure channel to perform the authentication with the AAA server 4, it is no need to establish the secure channel between the UE 1 and the AAA server 4 before the authentication starts every time. Thus, much authentication time may be saved. In other embodiments, the aforementioned method may be performed by other suitable electronic devices, such as a Set-top box, a gateway, and a router.
It should be emphasized that the above-described embodiments of the present disclosure, particularly, any embodiments, are merely possible examples of implementations, merely set forth for a clear understanding of the principles of the disclosure. Many variations and modifications may be made to the above-described embodiment(s) of the disclosure without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and the present disclosure and protected by the following claims.
Number | Date | Country | Kind |
---|---|---|---|
201010236645.7 | Jul 2010 | CN | national |