through standard Iu-CS and Iu-PS interfaces on the core network side. allow for full-service transparency as well as a low initial cost of deployment and low overall disruption to the operations of an operator's existing network. of a standard RNC are moved to the femtocell itself, the scaling issues associated with the Iu-b over IP approach are avoided. on the RAN Gateway approach for device-to-core network connectivity. "iU over ip" inTerFACe device-to-core network connectivity, the key remaining challenge is to fully define and standardize the "Iu over IP" interface between the femtocells and a RAN Gateway. dardize an entirely new interface; or (ii) to extend the existing 3GPP UMA standard, which is, for all intents and purposes, a successful 3GPP RAN Gateway interface already used to ser- vice dual-mode Wi-Fi handsets over the internet. comparing alternative proposals, which include: `locked in' to a vendor-specific interface between femtocells and the RAN gateway. Traditional RAN vendors have effectively created a closed market in the macro RAN access network with vendor specific flavors of the `Iu-b' protocol. But for the femtocell market to flourish, an open, standardized interface would enable operators to select from multiple femtocell access point manufacturers, driving up overall volumes and driving down overall costs. dual-mode Wi-Fi handsets, femtocells present a number of unique demands as they involve the delivery of mobile services over the inherently unreliable and unsecured public internet. As a result, defining the "Iu over IP" interface is significantly more complex than solely defining a method to transport Iu traffic out from the core over an IP network. For example, key areas that need to be defined and standardized include IP security, discovery and registration, authentication, authorization, roaming and handover, link reliability, regulatory compliance, |