Method and apparatus for resource management

CLAIM OF BENEFIT TO RELATED APPLICATIONS

0001This application claims the benefit of U.S. Provisional Application 60/826,700, entitled “Radio Access Network—Generic Access to the Iu Interface for Femtocells”, filed Sep. 22, 2006; U.S. Provisional Application 60/869,900, entitled “Generic Access to the Iu Interface for Femtocells”, filed Dec. 13, 2006; U.S. Provisional Application 60/911,862, entitled “Generic Access to the Iu Interface for Femtocells”, filed Apr. 13, 2007; U.S. Provisional Application 60/949,826, entitled “Generic Access to the Iu Interface”, filed Jul. 13, 2007; U.S. Provisional Application 60/884,889, entitled “Methods to Provide Protection against service Theft for Femtocells”, filed Jan. 14, 2007; U.S. Provisional Application 60/893,361, entitled “Methods to Prevent Theft of Service for Femtocells Operating in Open Access Mode”, filed Mar. 6, 2007; U.S. Provisional Application 60/884,017, entitled “Generic Access to the Iu Interface for Femtocell—Stage 3”, filed Jan. 8, 2007; U.S. Provisional Application 60/911,864, entitled “Generic Access to the Iu Interface for Femtocell—Stage 3”, filed Apr. 13, 2007; U.S. Provisional Application 60/862,564, entitled “E-UMA—Generic Access to the Iu Interface”, filed Oct. 23, 2006; U.S. Provisional Application 60/949,853, entitled “Generic Access to the Iu Interface”, filed Jul. 14, 2007; and U.S. Provisional Application 60/954,549, entitled “Generic Access to the Iu Interfaces—Stage 2 Specification”, filed Aug. 7, 2007. The contents of each of the above mentioned provisional applications are hereby incorporated by reference.

FIELD OF THE INVENTION

0002The invention relates to telecommunication. More particularly, this invention relates to a technique for seamlessly integrating voice and data telecommunication services across a licensed wireless system and a short-ranged licensed wireless system.

BACKGROUND OF THE INVENTION

0003Licensed wireless systems provide mobile wireless communications to individuals using wireless transceivers. Licensed wireless systems refer to public cellular telephone systems and/or Personal Communication Services (PCS) telephone systems. Wireless transceivers include cellular telephones, PCS telephones, wireless-enabled personal digital assistants, wireless modems, and the like.

0004Licensed wireless systems utilize wireless signal frequencies that are licensed from governments. Large fees are paid for access to these frequencies. Expensive base station (BS) equipment is used to support communications on licensed frequencies. Base stations are typically installed approximately a mile apart from one another (e.g., cellular towers in a cellular network). The wireless transport mechanisms and frequencies employed by typical licensed wireless systems limit both data transfer rates and range. As a result, the quality of service (voice quality and speed of data transfer) in licensed wireless systems is considerably inferior to the quality of service afforded by landline (wired) connections. Thus, the user of a licensed wireless system pays relatively high fees for relatively low quality service.

0005Landline (wired) connections are extensively deployed and generally perform at a lower cost with higher quality voice and higher speed data services. The problem with landline connections is that they constrain the mobility of a user. Traditionally, a physical connection to the landline was required.

0006In the past few years, the use of unlicensed wireless communication systems to facilitate mobile access to landline-based networks has seen rapid growth. For example, such unlicensed wireless systems may support wireless communication based on the IEEE 802.11a, b or g standards (WiFi), or the Bluetooth® standard. The mobility range associated with such systems is typically on the order of 100 meters or less. A typical unlicensed wireless communication system includes a base station comprising a wireless access point (AP) with a physical connection (e.g., coaxial, twisted pair, or optical cable) to a landline-based network. The AP has a RF transceiver to facilitate communication with a wireless handset that is operative within a modest distance of the AP, wherein the data transport rates supported by the WiFi and Bluetooth® standards are much higher than those supported by the aforementioned licensed wireless systems. Thus, this option provides higher quality services at a lower cost, but the services only extend a modest distance from the base station.

0007Currently, technology is being developed to integrate the use of licensed and unlicensed wireless systems in a seamless fashion, thus enabling a user to access, via a single handset, an unlicensed wireless system when within the range of such a system, while accessing a licensed wireless system when out of range of the unlicensed wireless system. The unlicensed wireless communication systems, however, require the use of dual-mode wireless transceivers to communicate with the licensed system over the licensed wireless frequencies and with the unlicensed system over the unlicensed wireless frequencies. The use of such dual-mode transceivers requires the service providers to upgrade the existing subscribers' transceivers which operate only on licensed wireless frequencies to dual-mode transceivers. Therefore, there is a need in the art to develop a system that provides the benefits of the systems described above, without the need for dual-mode transceivers.

SUMMARY OF THE INVENTION

0008Some embodiments are implemented in a communication system that includes a first wireless communication system and a second wireless communication system that includes a Femtocell access point (FAP) and a network controller that can communicatively couple the FAP to the first wireless communication system.

0009In some embodiments, the network controller can communicatively couple to the first wireless communication system through a UTRAN Iu interface. In some embodiments, the FAP can communicatively couple to a user equipment using a short-range licensed wireless frequency.

0010Some embodiments provide a resource management method that determines that a user equipment (UE) has roved in a region serviced by the FAP. The FAP includes a generic access resource control (GA-RC) protocol sub-layer. The method creates a separate GA-RC state dedicated to the UE in the GA-RC protocol sub-layer. The method also sets the GA-RC state dedicated to the UE to a deregistered state to indicate that the UE is not registered to use the services of the second wireless communication system.

0011Some embodiments provide method that determines whether a UE has roved-out of the second communication system. The method receives a periodic message at the FAP from the UE. When the FAP fails to receive a pre-determined number of the periodic messages, the method sends a deregister message to the network controller over a unique connection between the FAP and the network controller which is dedicated to the UE and also releases the dedicated connection.

0012Some embodiments provide a method of that releases resources after the loss of connectivity. The method sends a periodic message from the FAP to the network controller over a connection between the FAP and the network controller to determine whether the connection is lost. When the FAP determines that the connection is lost, the FAP deregisters a user equipment (UE) that is communicatively coupled with the FAP and forces the UE to perform a cell reselection.

0013Some embodiments provide a method that registers a Femtocell access point (FAP). The method sends a register request message that includes a registration type from the FAP to the network controller. The registration type identifies the FAP as a device to be registered with the network controller. When the register request message is acceptable by the network controller, the FAP receives a register accept message.

0014Some embodiments provide a method for performing discovery. The method sends a discovery request message that includes a licensed wireless cell information to a provisioning network controller. The method receives a discovery accept message at the FAP. The discovery accept message includes identification of a default network controller determined based on the cell information. The discovery accept message is sent by the provisioning network controller when the provisioning network controller determines that the provisioning network controller can accept the discovery request message.

0015Some embodiments provide a method of performing a user equipment (UE) registration. The method establishes a unique connection dedicated to the UE between the FAP and the network controller. The method receives a register request message at the network controller from the FAP through the dedicated connection.

0016Some embodiments provide a security control method. The method receives a security mode command that includes a set of security keys and a set of security algorithms at the FAP from the network controller, the set of security keys and the set of security algorithms are received at the network controller from the first wireless communication system. The method determines the integrity of a set of messages that are exchanged between the FAP and a user equipment (UE) that is communicatively coupled to the FAP through an air interface by using the set of security keys and the set of security algorithms.

0017Some embodiments provide method of providing security. The method establishes a secure tunnel between the FAP and the network controller. The method communicatively couples the FAP and several user equipments (UEs) to the network controller by using the secure tunnel. The UEs are communicatively coupled to the FAP through an air interface.

0018Some embodiments provide a method of preventing theft of service. The method creates an authorized session that includes a session identity for a first user equipment (UE). The session is for communicatively coupling the first UE with the first wireless communication system through the FAP. The first UE is recognized by the first wireless communication system as an authorized UE to use the FAP. The method rejects a request by the FAP to register a second UE when the identity of the second does not match any identity in the set of first UE identities. The rejected request includes the session identity of the authorized session and the identity of the second UE. The second UE is not recognized by the first wireless communication system as an authorized UE to use the FAP.

BRIEF DESCRIPTION OF THE DRAWINGS

0019The novel features of the invention are set forth in the appended claims. However, for purpose of explanation, several embodiments of the invention are set forth in the following figures.

0020<figref idref="DRAWINGS">FIG. 1</figref> illustrates an integrated communication system (ICS) of some embodiments.

0021<figref idref="DRAWINGS">FIG. 2</figref> illustrates several applications of an ICS in some embodiments.

0022<figref idref="DRAWINGS">FIG. 3</figref> illustrates the overall A/Gb-mode GAN functional architecture of some embodiments.

0023<figref idref="DRAWINGS">FIG. 4</figref> illustrates the overall Iu-mode GAN functional architecture of some embodiments.

0024<figref idref="DRAWINGS">FIG. 5</figref> illustrates the Femtocell functional architecture of some embodiments.

0025<figref idref="DRAWINGS">FIG. 6</figref> illustrates Femtocell network architecture of some embodiments with an asynchronous transfer mode (ATM) interface towards the core network.

0026<figref idref="DRAWINGS">FIG. 7</figref> illustrates Femtocell network architecture of some embodiments with IP interface towards the core network.

0027<figref idref="DRAWINGS">FIG. 8</figref> illustrates CS Domain Control Plane Architecture of some embodiments.

0028<figref idref="DRAWINGS">FIG. 9</figref> illustrates CS Domain User Plane Protocol Architecture of some embodiments.

0029<figref idref="DRAWINGS">FIG. 10</figref> illustrates PS Domain Control Plane Architecture of some embodiments.

0030<figref idref="DRAWINGS">FIG. 11</figref> illustrates PS Domain User Plane Protocol Architecture of some embodiments.

0031<figref idref="DRAWINGS">FIG. 12</figref> illustrates the state diagram for Generic Access in the FAP of some embodiments.

0032<figref idref="DRAWINGS">FIG. 13</figref> illustrates the state diagram in some embodiments for GA-CSR in the FAP for each UE.

0033<figref idref="DRAWINGS">FIG. 14</figref> illustrates the state diagram in some embodiments for GA-PSR in the FAP for each UE.

0034<figref idref="DRAWINGS">FIG. 15</figref> illustrates FAP initiated GA-CSR connection establishment in some embodiments.

0035<figref idref="DRAWINGS">FIG. 16</figref> illustrates GA-CSR connection release of some embodiments.

0036<figref idref="DRAWINGS">FIG. 17</figref> illustrates FAP initiated GA-PSR connection establishment of some embodiments.

0037<figref idref="DRAWINGS">FIG. 18</figref> illustrates GA-PSR connection release in some embodiments.

0038<figref idref="DRAWINGS">FIG. 19</figref> illustrates FAP power on discovery procedure of some embodiments.

0039<figref idref="DRAWINGS">FIG. 20</figref> illustrates FAP power on registration procedure in some embodiments.

0040<figref idref="DRAWINGS">FIG. 21</figref> illustrates the messages associated with the FAP initiated synchronization procedure in some embodiments.

0041<figref idref="DRAWINGS">FIG. 22</figref> illustrates UE registration in some embodiments.

0042<figref idref="DRAWINGS">FIG. 23</figref> illustrates UE Rove out in some embodiments.

0043<figref idref="DRAWINGS">FIG. 24</figref> illustrates a scenario where the UE powers down and performs an IMSI detach in some embodiments.

0044<figref idref="DRAWINGS">FIG. 25</figref> illustrates a scenario for loss of Up interface connectivity in some embodiments.

0045<figref idref="DRAWINGS">FIG. 26</figref> illustrates FAP-initiated register update scenario of some embodiments.

0046<figref idref="DRAWINGS">FIG. 27</figref> illustrates INC-initiated register update scenario in some embodiments.

0047<figref idref="DRAWINGS">FIG. 28</figref> illustrates the FAP initiated synchronization procedure in some embodiments.

0048<figref idref="DRAWINGS">FIG. 29</figref> illustrates voice bearer establishment procedures (for MO/MT calls, using Iu-UP over AAL2) in some embodiments.

0049<figref idref="DRAWINGS">FIG. 30</figref> illustrates the mobile originated mobile-to-PSTN call in some embodiments.

0050<figref idref="DRAWINGS">FIG. 31</figref> illustrates a mobile terminated PSTN-to-mobile call in some embodiments.

0051<figref idref="DRAWINGS">FIG. 32</figref> illustrates call release by Femtocell subscriber in some embodiments.

0052<figref idref="DRAWINGS">FIG. 33</figref> illustrates an example of relay of DTAP supplementary service messages in some embodiments.

0053<figref idref="DRAWINGS">FIG. 34</figref> illustrates FAP initiated GA-PSR Transport Channel activation in some embodiments.

0054<figref idref="DRAWINGS">FIG. 35</figref> illustrates FAP initiated Transport Channel deactivation in some embodiments.

0055<figref idref="DRAWINGS">FIG. 36</figref> illustrates network initiated Transport Channel Activation for user data service in some embodiments.

0056<figref idref="DRAWINGS">FIG. 37</figref> illustrates network initiated Transport Channel deactivation in some embodiments.

0057<figref idref="DRAWINGS">FIG. 38</figref> illustrates Femtocell User Plane Data Transport procedures in some embodiments.

0058<figref idref="DRAWINGS">FIG. 39</figref> illustrates Uplink Control Plane Data Transport of some embodiments.

0059<figref idref="DRAWINGS">FIG. 40</figref> illustrates Downlink Control Plane Data Transport of some embodiments.

0060<figref idref="DRAWINGS">FIG. 41</figref> illustrates the protocol architecture for CS mode SMS in some embodiments.

0061<figref idref="DRAWINGS">FIG. 42</figref> illustrates the GAN protocol architecture for packet mode SMS in some embodiments.

0062<figref idref="DRAWINGS">FIG. 43</figref> illustrates a mobile originated SMS transfer via GAN circuit mode in some embodiments.

0063<figref idref="DRAWINGS">FIG. 44</figref> illustrates a CS mode mobile terminated SMS transfer via Femtocell in some embodiments.

0064<figref idref="DRAWINGS">FIG. 45</figref> illustrates a service area based routing scenario of some embodiments.

0065<figref idref="DRAWINGS">FIG. 46</figref> illustrates GAN Femtocell security mechanisms in some embodiments.

0066<figref idref="DRAWINGS">FIG. 47</figref> illustrates EAP-SIM authentication procedure in some embodiments.

0067<figref idref="DRAWINGS">FIG. 48</figref> illustrates EAP-AKA authentication procedure of some embodiments.

0068<figref idref="DRAWINGS">FIG. 49</figref> illustrates the message flow for security mode control in some embodiments.

0069<figref idref="DRAWINGS">FIG. 50</figref> illustrates the AKA procedure used for mutual authentication in some embodiments.

0070<figref idref="DRAWINGS">FIG. 51</figref> illustrates the high level procedure which can result in theft of service by a rogue FAP.

0071<figref idref="DRAWINGS">FIG. 52</figref> illustrates the Femtocell service theft prevention approach of some embodiments.

0072<figref idref="DRAWINGS">FIG. 53</figref> illustrates the Femtocell service theft prevention in some embodiments.

0073<figref idref="DRAWINGS">FIG. 54</figref> illustrates the Service Access Control for new FAP connecting to Femtocell network in some embodiments.

0074<figref idref="DRAWINGS">FIG. 55</figref> illustrates the Service Access Control for the FAP getting redirected in Femtocell network in some embodiments.

0075<figref idref="DRAWINGS">FIG. 56</figref> illustrates the Service Access Control for FAP registering in restricted UMTS coverage area in some embodiments.

0076<figref idref="DRAWINGS">FIG. 57</figref> illustrates the Service Access Control for Unauthorized UE accessing authorized FAP in some embodiments.

0077<figref idref="DRAWINGS">FIG. 58</figref> conceptually illustrates a computer system with which some embodiments are implemented.

DETAILED DESCRIPTION OF THE INVENTION

0078In the following detailed description of the invention, numerous details, examples, and embodiments of the invention are set forth and described. However, it will be clear and apparent to one skilled in the art that the invention is not limited to the embodiments set forth and that the invention may be practiced without some of the specific details and examples discussed.

0079Throughout the following description, acronyms commonly used in the telecommunications industry for wireless services are utilized along with acronyms specific to the present invention. A table of acronyms used in this application is included in Section XV.

0080Some embodiments are implemented in a communication system that includes a first wireless communication system and a second wireless communication system that includes a Femtocell access point (FAP) and a network controller that can communicatively couple the FAP to the first wireless communication system.

0081In some embodiments, the network controller can communicatively couple to the first wireless communication system through a UTRAN Iu interface. In some embodiments, the FAP can communicatively couple to a user equipment using a short-range licensed wireless frequency.

0082Some embodiments provide a resource management method that determines that a user equipment (UE) has roved in a region serviced by the FAP. The FAP includes a generic access resource control (GA-RC) protocol sub-layer. The method creates a separate GA-RC state dedicated to the UE in the GA-RC protocol sub-layer. The method also sets the GA-RC state dedicated to the UE to a deregistered state to indicate that the UE is not registered to use the services of the second wireless communication system.

0083Some embodiments provide method that determines whether a UE has roved-out of the second communication system. The method receives a periodic message at the FAP from the UE. When the FAP fails to receive a pre-determined number of the periodic messages, the method sends a deregister message to the network controller over a unique connection between the FAP and the network controller which is dedicated to the UE and also releases the dedicated connection.

0084Some embodiments provide a method of that releases resources after the loss of connectivity. The method sends a periodic message from the FAP to the network controller over a connection between the FAP and the network controller to determine whether the connection is lost. When the FAP determines that the connection is lost, the FAP deregisters a user equipment (UE) that is communicatively coupled with the FAP and forces the UE to perform a cell reselection.

0085Some embodiments provide a method that registers a Femtocell access point (FAP). The method sends a register request message that includes a registration type from the FAP to the network controller. The registration type identifies the FAP as a device to be registered with the network controller. When the register request message is acceptable by the network controller, the FAP receives a register accept message.

0086Some embodiments provide a method for performing discovery. The method sends a discovery request message that includes a licensed wireless cell information to a provisioning network controller. The method receives a discovery accept message at the FAP. The discovery accept message includes identification of a default network controller determined based on the cell information. The discovery accept message is sent by the provisioning network controller when the provisioning network controller determines that the provisioning network controller can accept the discovery request message.

0087Some embodiments provide a method of performing a user equipment (UE) registration. The method establishes a unique connection dedicated to the UE between the FAP and the network controller. The method receives a register request message at the network controller from the FAP through the dedicated connection.

0088Some embodiments provide a security control method. The method receives a security mode command that includes a set of security keys and a set of security algorithms at the FAP from the network controller, the set of security keys and the set of security algorithms are received at the network controller from the first wireless communication system. The method determines the integrity of a set of messages that are exchanged between the FAP and a user equipment (UE) that is communicatively coupled to the FAP through an air interface by using the set of security keys and the set of security algorithms.

0089Some embodiments provide method of providing security. The method establishes a secure tunnel between the FAP and the network controller. The method communicatively couples the FAP and several user equipments (UEs) to the network controller by using the secure tunnel. The UEs are communicatively coupled to the FAP through an air interface.

0090Some embodiments provide a method of preventing theft of service. The method creates an authorized session that includes a session identity for a first user equipment (UE). The session is for communicatively coupling the first UE with the first wireless communication system through the FAP. The first UE is recognized by the first wireless communication system as an authorized UE to use the FAP. The method rejects a request by the FAP to register a second UE when the identity of the second UE does not match any identity in the set of first UE identities. The rejected request includes the session identity of the authorized session and the identity of the second UE. The second UE is not recognized by the first wireless communication system as an authorized UE to use the FAP.

0091Several more detailed embodiments of the invention are described in sections below. Specifically, Section I describes the overall integrated communication system in which some embodiments are incorporated. The discussion in Section I is followed by a discussion of the system architecture of a Femtocell system in Section II. Next, Section III describes the protocol architecture of the Femtocell system. Section IV then describes the resource management procedures of the Femtocell system in some embodiments. Next, Section V presents the mobility management functions of the Femtocell system in some embodiments.

0092Next, Section VI describes the call management procedures of the Femtocell system. This section is followed by Section VII which describes the packet services of the Femtocell system in some embodiments. Error handling procedures are described in Section VIII. Lists of messages and information elements used in different embodiments are provided in Section IX. Short Message Services support of the Femtocell system is described in Section X followed by the description of the emergency services in Section XI.

0093The Femtocell system security functions are described in Section XII. This description is followed by Femtocell system service access control discussed in Section XIII. Next, Section XIV description of a computer system with which some embodiments of the invention are implemented. Finally, Section XV lists the abbreviations used.

I. OVERALL SYSTEM

0094A. Integrated Communication Systems (ICS)

0095<figref idref="DRAWINGS">FIG. 1</figref> illustrates an integrated communication system (ICS) architecture <b>100</b> in accordance with some embodiments of the present invention. ICS architecture <b>100</b> enables user equipment (UE) <b>102</b> to access a voice and data network <b>165</b> via either a licensed air interface <b>106</b> or an ICS access interface <b>110</b> through which components of the licensed wireless core network <b>165</b> are alternatively accessed. In some embodiments, a communication session through either interface includes voice services, data services, or both.

0096The mobile core network <b>165</b> includes one or more Home Location Registers (HLRs) <b>150</b> and databases <b>145</b> for subscriber authentication and authorization. Once authorized, the UE <b>102</b> may access the voice and data services of the mobile core network <b>165</b>. In order to provide such services, the mobile core network <b>165</b> includes a mobile switching center (MSC) <b>160</b> for providing access to the circuit switched services (e.g., voice and data). Packet switched services are provided for through a Serving GPRS (General Packet Radio Service) Support Node (SGSN) <b>155</b> in conjunction with a gateway such as the Gateway GPRS Support Node (GGSN) <b>157</b>.

0097The SGSN <b>155</b> is typically responsible for delivering data packets from and to the GGSN <b>157</b> and the user equipment within the geographical service area of the SGSN <b>155</b>. Additionally, the SGSN <b>155</b> may perform functionality such as mobility management, storing user profiles, and storing location information. However, the actual interface from the mobile core network <b>165</b> to various external data packet services networks (e.g., public Internet) is facilitated by the GGSN <b>157</b>. As the data packets originating from the user equipment typically are not structured in the format with which to access the external data networks, it is the role of the GGSN <b>157</b> to act as the gateway into such packet services networks. In this manner, the GGSN <b>157</b> provides addressing for data packets passing to and from the UE <b>102</b> and the external packet services networks (not shown). Moreover, as the user equipment of a licensed wireless network traverses multiple service regions and thus multiple SGSNs, it is the role of the GGSN <b>157</b> to provide a static gateway into the external data networks.

0098In the illustrated embodiment, components common to a UMTS Terrestrial Radio Access Network (UTRAN), based cellular network that includes multiple base stations referred to as Node Bs <b>180</b> (of which only one is shown for simplicity) that facilitate wireless communication services for various user equipment <b>102</b> via respective licensed radio links <b>106</b> (e.g., radio links employing radio frequencies within a licensed bandwidth). However, one of ordinary skill in the art will recognize that in some embodiments, the licensed wireless network may include other components such the GSM/EDGE Radio Access Network (GERAN). An example of a system using A and Gb interfaces to access GERAN is shown in <figref idref="DRAWINGS">FIG. 3</figref> described further below.

0099The licensed wireless channel <b>106</b> may comprise any licensed wireless service having a defined UTRAN or GERAN interface protocol (e.g., Iu-cs and Iu-ps interfaces for UTRAN or A and Gb interfaces for GERAN) for a voice/data network. The UTRAN <b>185</b> typically includes at least one Node B <b>180</b> and a Radio Network Controller (RNC) <b>175</b> for managing the set of Node Bs <b>180</b>. Typically, the multiple Node Bs <b>180</b> are configured in a cellular configuration (one per each cell) that covers a wide service area. A licensed wireless cell is sometimes referred to as a macro cell which is a logical term used to reference, e.g., the UMTS radio cell (i.e., 3G cell) under Node-B/RNC which is used to provide coverage typically in the range of tens of kilometers. Also, the UTRAN or GERAN is sometimes referred to as a macro network.

0100Each RNC <b>175</b> communicates with components of the core network <b>165</b> through a standard radio network controller interface such as the Iu-cs and Iu-ps interfaces depicted in <figref idref="DRAWINGS">FIG. 1</figref>. For example, a RNC <b>175</b> communicates with MSC <b>160</b> via the UTRAN Iu-cs interface for circuit switched services. Additionally, the RNC <b>175</b> communicates with SGSN <b>155</b> via the UTRAN Iu-ps interface for packet switched services through GGSN <b>157</b>. Moreover, one of ordinary skill in the art will recognize that in some embodiments, other networks with other standard interfaces may apply. For example, the RNC <b>175</b> in a GERAN network is replaced with a Base Station Controller (BSC) that communicates with the MSC <b>160</b> via an A interface for the circuit switched services and the BSC communicates with the SGSN via a Gb interface of the GERAN network for packet switched services.

0101In some embodiments of the ICS architecture, the user equipment <b>102</b> use the services of the mobile core network (CN) <b>165</b> via a second communication network facilitated by the ICS access interface <b>110</b> and a Generic Access Network Controller (GANC) <b>120</b> (also referred to as a Universal Network Controller or UNC).

0102In some embodiments, the voice and data services over the ICS access interface <b>110</b> are facilitated via an access point <b>114</b> communicatively coupled to a broadband IP network <b>116</b>. In some embodiments, the access point <b>114</b> is a generic wireless access point that connects the user equipment <b>102</b> to the ICS network through an unlicensed wireless network <b>118</b> created by the access point <b>114</b>. In some other embodiments, the access point <b>114</b> is a Femtocell access point (FAP) <b>114</b> communicatively coupled to a broadband IP network <b>116</b>. The FAP facilitates short-range licensed wireless communication sessions <b>118</b> that operate independent of the licensed communication session <b>106</b>. In some embodiments, the GANC, FAP, UE, and the area covered by the FAP are collectively referred to as a Femtocell System. A Femtocell spans a smaller area (typically few tens of meters) than a macro cell. In other words, the Femtocell is a micro cell that has a range that is 100, 1000, or more times less than a macro cell. In case of the Femtocell system, the user equipment <b>102</b> connects to the ICS network through a short-range licensed wireless network created by the FAP <b>114</b>. Signals from the FAP are then transmitted over the broadband IP network <b>116</b>.

0103The signaling from the UE <b>102</b> is passed over the ICS access interface <b>110</b> to the GANC <b>120</b>. After the GANC <b>120</b> performs authentication and authorization of the subscriber, the GANC <b>120</b> communicates with components of the mobile core network <b>165</b> using a radio network controller interface that is the same or similar to the radio network controller interface of the UTRAN described above, and includes a UTRAN Iu-cs interface for circuit switched services and a UTRAN Iu-ps interface for packet switched services (e.g., GPRS). In this manner, the GANC <b>120</b> uses the same or similar interfaces to the mobile core network as a UTRAN Radio Access Network Subsystem (e.g., the Node B <b>180</b> and RNC <b>175</b>).

0104In some embodiments, the GANC <b>120</b> communicates with other system components of the ICS system through one or more of several other interfaces, which are (1) “Up”, (2) “Wm”, (3) “D′/Gr′”, (4) “Gn′”, and (5) “S1”. The “Up” interface is the standard interface for session management between the UE <b>102</b> and the GANC <b>120</b>. The “Wm” interface is a standardized interface between the GANC <b>120</b> and an Authorization, Authentication, and Accounting (AAA) Server <b>170</b> for authentication and authorization of the UE <b>102</b> into the ICS. The “D′/Gr′” interface is the standard interface between the AAA server <b>170</b> and the HLR <b>160</b>. Optionally, some embodiments use the “Gn′” interface which is a modified interface for direct communications with the data services gateway (e.g., GGSN) of the mobile core network. Some embodiments optionally include the “S1” interface. In these embodiments, the “S1” interface provides an authorization and authentication interface from the GANC <b>120</b> to an AAA sever <b>140</b>. In some embodiments, the AAA server <b>140</b> that supports the S1 interface and the AAA server <b>170</b> that supports Wm interface may be the same. More details of the S1 interface are described in U.S. application Ser. No. 11/349,025, entitled “Service Access Control Interface for an Unlicensed Wireless Communication System”, filed Feb. 6, 2006.

0105In some embodiments, the UE <b>102</b> must register with the GANC <b>120</b> prior to accessing ICS services. Registration information of some embodiments includes a subscriber's International Mobile Subscriber Identity (IMSI), a Media Access Control (MAC) address, and a Service Set Identifier (SSID) of the serving access point as well as the cell identity from the GSM or UTRAN cell upon which the UE <b>102</b> is already camped (a UE is camped on a cell when the UE has completed the cell selection/reselection process and has chosen a cell; the UE monitors system information and, in most cases, paging information). In some embodiments, the GANC <b>120</b> may pass this information to the AAA server <b>140</b> to authenticate the subscriber and determine the services (e.g., voice and data) available to the subscriber. If approved by the AAA server <b>140</b> for access, the GANC <b>120</b> will permit the UE <b>102</b> to access voice and data services of the ICS system.

0106These circuit switched and packet switched services are seamlessly provided by the ICS to the UE <b>102</b> through the various interfaces described above. In some embodiments, when data services are requested by the UE <b>102</b>, the ICS uses the optional Gn′ interface for directly communicating with a GGSN <b>157</b>. The Gn′ interface allows the GANC <b>120</b> to avoid the overhead and latency associated with communicating with the SGSN <b>155</b> over the Iu-ps interface of the UTRAN or the Gb interface of the GSM core networks prior to reaching the GGSN <b>157</b>.

0107B. Applications of ICS

0108An ICS provides scalable and secure interfaces into the core service network of mobile communication systems. <figref idref="DRAWINGS">FIG. 2</figref> illustrates several applications of an ICS in some embodiments. As shown, homes, offices, hot spots, hotels, and other public and private places <b>205</b> are connected to one or more network controllers <b>210</b> (such as the GANC <b>120</b> shown in <figref idref="DRAWINGS">FIG. 1</figref>) through the Internet <b>215</b>. The network controllers in turn connect to the mobile core network <b>220</b> (such as the core network <b>165</b> shown in <figref idref="DRAWINGS">FIG. 1</figref>).

0109<figref idref="DRAWINGS">FIG. 2</figref> also shows several user equipments. These user equipments are just examples of user equipments that can be used for each application. Although in most examples only one of each type of user equipments is shown, one of ordinary skill in the art would realize that other type of user equipments can be used in these examples without deviating from the teachings of the invention. Also, although only one of each type of access points, user equipment, or network controllers are shown, many such access points, user equipments, or network controllers may be employed in <figref idref="DRAWINGS">FIG. 2</figref>. For instance, an access point may be connected to several user equipment, a network controller may be connected to several access points, and several network controllers may be connected to the core network. The following sub-sections provide several examples of services that can be provided by an ICS.

01101. Wi-Fi

0111A Wi-Fi access point <b>230</b> enables a dual-mode cellular/Wi-Fi UEs <b>260</b>-<b>265</b> to receive high-performance, low-cost mobile services when in range of a home, office, or public Wi-Fi network. With dual-mode UEs, subscribers can roam and handover between licensed wireless communication system and Wi-Fi access and receive a consistent set of services as they transition between networks.

01122. Femtocells

0113A Femtocell enables user equipments, such as standard mobile stations <b>270</b> and wireless enabled computers <b>275</b> shown, to receive low cost services using a short-range licensed wireless communication sessions through a FAP <b>235</b>.

01143. Terminal Adaptors

0115Terminal adaptors <b>240</b> allow incorporating fixed-terminal devices such as telephones <b>245</b>, Faxes <b>250</b>, and other equipments that are not wireless enabled within the ICS. As far as the subscriber is concerned, the service behaves as a standard analog fixed telephone line. The service is delivered in a manner similar to other fixed line VoIP services, where a UE is connected to the subscriber's existing broadband (e.g., Internet) service.

01164. WiMAX

0117Some licensed wireless communication system operators are investigating deployment of WiMAX networks in parallel with their existing cellular networks. A dual mode cellular/WiMAX UE <b>255</b> enables a subscriber to seamlessly transition between a cellular network and such a WiMAX network through a WiMax access point <b>290</b>.

01185. SoftMobiles

0119Connecting laptops <b>280</b> to broadband access at hotels and Wi-Fi hot spots has become popular, particularly for international business travelers. In addition, many travelers are beginning to utilize their laptops and broadband connections for the purpose of voice communications. Rather than using mobile phones to make calls and pay significant roaming fees, they utilize SoftMobiles (or SoftPhones) and VoIP services when making long distance calls.

0120To use a SoftMobile service, a subscriber would place a USB memory stick <b>285</b> with an embedded SIM into a USB port of their laptop <b>280</b>. A SoftMobile client would automatically launch and connect over IP to the mobile service provider. From that point on, the subscriber would be able to make and receive mobile calls as if she was in her home calling area.

0121Several examples of Integrated Communication Systems (ICS) are given in the following sub-sections. A person of ordinary skill in the art would realize that the teachings in these examples can be readily combined. For instance, an ICS can be an IP based system and have an A/Gb interface towards the core network while another ICS can have a similar IP based system with an Iu interface towards the core network.

0122C. Integrated Systems with A/Gb and/or Iu Interfaces towards the Core Network

0123<figref idref="DRAWINGS">FIG. 3</figref> illustrates the A/Gb-mode Generic Access Network (GAN) functional architecture of some embodiments. The GAN includes one or more Generic Access Network Controllers (GANC) <b>310</b> and one or more generic IP access networks <b>315</b>. One or more UEs <b>305</b> (one is shown for simplicity) can connect to a GANC <b>310</b> through a generic IP access network <b>315</b>. The GANC <b>310</b> has the capability to appear to the core network <b>325</b> as a GSM/EDGE Radio Access Network (GERAN) Base Station Controller (BSC). The GANC <b>310</b> includes a Security Gateway (SeGW) <b>320</b> that terminates secure remote access tunnels from the UE <b>305</b>, providing mutual authentication, encryption and data integrity for signaling, voice and data traffic.

0124The generic IP access network <b>315</b> provides connectivity between the UE <b>305</b> and the GANC <b>310</b>. The IP transport connection extends from the GANC <b>310</b> to the UE <b>305</b>. A single interface, the Up interface, is defined between the GANC <b>310</b> and the UE <b>305</b>.

0125The GAN co-exists with the GERAN and maintains the interconnections with the Core Network (CN) <b>325</b> via the standardized interfaces defined for GERAN. These standardized interfaces include the A interface to Mobile Switching Center (MSC) <b>330</b> for circuit switched services, Gb interface to Serving GPRS Support Node (SGSN) <b>335</b> for packet switched services, Lb interface to Serving Mobile Location Center (SMLC) <b>350</b> for supporting location services, and an interface to Cell Broadcast Center (CBC) <b>355</b> for supporting cell broadcast services. The transaction control (e.g. Connection Management, CC, and Session Management, SM) and user services are provided by the core network (e.g. MSC/VLR and the SGSN/GGSN).

0126As shown, the SeGW <b>320</b> is connected to a AAA server <b>340</b> over the Wm interface. The AAA server <b>340</b> is used to authenticate the UE <b>305</b> when it sets up a secure tunnel. Some embodiments require only a subset of the Wm functionalities for the GAN application. In these embodiments, as a minimum the GANC-SeGW shall support the Wm authentication procedures.

0127<figref idref="DRAWINGS">FIG. 4</figref> illustrates the Iu-mode Generic Access Network (GAN) functional architecture of some embodiments. The GAN includes one or more Generic Access Network Controllers (GANC) <b>410</b> and one or more generic IP access networks <b>415</b>. One or more UEs <b>405</b> (one is shown for simplicity) can be connected to a GANC <b>410</b> through a generic IP access network <b>415</b>. In comparison with the GANC <b>310</b>, the GANC <b>410</b> has the capability to appear to the core network <b>425</b> as a UMTS Terrestrial Radio Access Network (UTRAN) Radio Network Controller (RNC). In some embodiments, the GANC has the expanded capability of supporting both the Iu and A/Gb interfaces to concurrently support both Iu-mode and A/Gb-mode UEs. Similar to the GANC <b>310</b>, the GANC <b>410</b> includes a Security Gateway (SeGW) <b>420</b> that terminates secure remote access tunnels from the UE <b>405</b>, providing mutual authentication, encryption and data integrity for signaling, voice and data traffic.

0128The generic IP access network <b>415</b> provides connectivity between the UE <b>405</b> and the GANC <b>410</b>. The IP transport connection extends from the GANC <b>410</b> to the UE <b>405</b>. A single interface, the Up interface, is defined between the GANC <b>410</b> and the UE <b>405</b>. Functionality is added to this interface, over the UP interface shown in <figref idref="DRAWINGS">FIG. 3</figref>, to support the Iu-mode GAN service.

0129The GAN co-exists with the UTRAN and maintains the interconnections with the Core Network (CN) <b>425</b> via the standardized interfaces defined for UTRAN. These standardized interfaces include the Iu-cs interface to Mobile Switching Center (MSC) <b>430</b> for circuit switched services, Iu-ps interface to Serving GPRS Support Node (SGSN) <b>435</b> for packet switched services, Iu-pc interface to Serving Mobile Location Center (SMLC) <b>450</b> for supporting location services, and Iu-bc interface to Cell Broadcast Center (CBC) <b>455</b> for supporting cell broadcast services. The transaction control (e.g. Connection Management, CC, and Session Management, SM) and user services are provided by the core network (e.g. MSC/VLR and the SGSN/GGSN).

0130As shown, the SeGW <b>420</b> is connected to a AAA server <b>440</b> over the Wm interface. The AAA server <b>440</b> is used to authenticate the UE <b>405</b> when it sets up a secure tunnel. Some embodiments require only a subset of the Wm functionalities for the Iu mode GAN application. In these embodiments, as a minimum the GANC-SeGW shall support the Wm authentication procedures.

II. FEMTOCELL SYSTEM ARCHITECTURE

0131<figref idref="DRAWINGS">FIG. 5</figref> illustrates the Femtocell system functional architecture of some embodiments. As shown, many components of the system shown in <figref idref="DRAWINGS">FIG. 5</figref> are similar to components of <figref idref="DRAWINGS">FIG. 4</figref>. In addition, the Femtocell system includes a Femtocell Access Point (FAP) <b>560</b> which communicatively couples the UE <b>505</b> to the GANC <b>510</b> through the Generic IP Access Network <b>515</b>. The interface between the UE <b>505</b> and the FAP <b>560</b> is referred to as the Uu interface in this disclosure. The UE <b>505</b> and the FAP <b>560</b> communicate through a short-range wireless air interface using licensed wireless frequencies. The GANC <b>510</b> is an enhanced version of the GANC <b>410</b> shown in <figref idref="DRAWINGS">FIG. 4</figref>. The Security Gateway (SeGW) <b>520</b> component of the GANC <b>510</b> terminates secure remote access tunnels from the FAP <b>560</b>, providing mutual authentication, encryption and data integrity for signaling, voice and data traffic.

0132The Femtocell Access Point (AP) Management System (AMS) <b>570</b> is used to manage a large number of FAPs. The AMS <b>570</b> functions include configuration, failure management, diagnostics, monitoring and software upgrades. The interface between the AMS <b>570</b> and the FAP <b>560</b> is referred to as the S3 interface. The S3 interface enables secure access to Femtocell access point management services for FAPs. All communication between the FAPs and AMS is exchanged via the Femtocell secure tunnel that is established between the FAP and SeGW <b>520</b>. As shown, the AMS <b>570</b> accesses to the AP/subscriber databases (Femtocell DB) <b>575</b> which provides centralized data storage facility for Femtocell AP (i.e., the FAP) and subscriber information. Multiple Femtocell system elements may access Femtocell DB via AAA server.

0133The IP Network Controller (INC) <b>565</b> component of the GANC <b>510</b> interfaces with the AAA/proxy server <b>540</b> through the S1 interface for provisioning of the FAP related information and service access control. As shown in <figref idref="DRAWINGS">FIG. 5</figref>, the AAA/proxy server <b>540</b> also interfaces with the AP/subscriber databases <b>575</b>.

0134A. ATM and IP Based Architectures

0135In some embodiments, the Femtocell system uses Asynchronous Transfer Mode (ATM) based Iu (Iu-cs and Iu-ps) interfaces towards the CN. In some embodiments, the Femtocell system architecture can also support an IP based Iu (Iu-cs and Iu-ps) interface towards the CN.

0136A person of ordinary skill in the art would realize that the same examples can be readily applied to other types of ICS. For instance, these examples can be used when the ICS access interface <b>110</b> (shown in <figref idref="DRAWINGS">FIG. 1</figref>) uses unlicensed frequencies (instead of Femtocell's licensed frequencies), the access point <b>114</b> is a generic WiFi access point (instead of a FAP), etc. Also, a person of ordinary skill in the art would realize that the same examples can be readily implemented using A/Gb interfaces (described above) instead of Iu interfaces.

0137<figref idref="DRAWINGS">FIG. 6</figref> illustrates the basic elements of the Femtocell system architecture with Asynchronous Transfer Mode (ATM) based Iu (Iu-cs and Iu-ps) interfaces towards the CN in some embodiments. These elements include the user equipment (UE) <b>605</b>, the FAP <b>610</b>, and the Generic Access Network Controller (GANC) <b>615</b>, and the AMS <b>670</b>.

0138For simplicity, only one UE and one FAP are shown. However, each GANC can support multiple FAPs and each FAP in turn can support multiple UEs. As shown, the GANC <b>615</b> includes an IP Network Controller (INC) <b>625</b>, a GANC Security Gateway (SeGW) <b>630</b>, a GANC Signaling Gateway <b>635</b>, a GANC Media Gateway (MGW) <b>640</b>, an ATM Gateway (<b>645</b>). Elements of the Femtocell are described further below.

0139<figref idref="DRAWINGS">FIG. 7</figref> illustrates the basic elements of the Femtocell system architecture with an IP based Iu (Iu-cs and Iu-ps) interface towards the CN in some embodiments. For simplicity, only one UE and one FAP are shown. However, each GANC can support multiple FAPs and each FAP in turn can support multiple UEs. This option eliminates the need for the GANC Signaling gateway <b>635</b> and also the ATM gateway <b>645</b>. Optionally for IP based Iu interface, the GANC Media Gateway <b>640</b> can also be eliminated if the R4 MGW <b>705</b> in the CN can support termination of voice data i.e. RTP frames as defined in “Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs”, IETF RFC <b>3267</b>, hereinafter “RFC <b>3267</b>”.

0140Also shown in <figref idref="DRAWINGS">FIGS. 6 and 7</figref> are components of the licensed wireless communication systems. These components are 3G MSC <b>650</b>, 3G SGSN <b>655</b>, and other Core Network System (shown together) <b>665</b>. The 3G MSC <b>650</b> provides a standard Iu-cs interface towards the GANC. Another alternative for the MSC is shown in <figref idref="DRAWINGS">FIG. 7</figref>. As shown, the MSC <b>750</b> is split up into a MSS (MSC Server) <b>775</b> for Iu-cs based signaling and MGW <b>780</b> for the bearer path. R4 MSC <b>750</b> is a release 4 version of a 3G MSC with a different architecture i.e. R4 MSC is split into MSS for control traffic and a MGW for handling the bearer. A similar MSC can be used for the ATM architecture of <figref idref="DRAWINGS">FIG. 6</figref>. Both architectures shown in <figref idref="DRAWINGS">FIGS. 6 and 7</figref> are also adaptable to use any future versions of the MSC.

0141The 3G SGSN <b>655</b> provides packet services (PS) via the standard Iu-ps interface. The SGSN connects to the INC <b>625</b> for signaling and to the SeGW <b>630</b> for PS data. The AAA server <b>660</b> communicates with the SeGW <b>630</b> and supports the EAP-AKA and EAP-SIM procedures used in IKEv2 over the Wm interface and includes a MAP interface to the HLR/AuC. This system also supports the enhanced service access control functions over the S1 interface.

0142For simplicity, in several diagrams throughout the present application, only the INC component of the GANC is shown. Also, whenever the INC is the relevant component of the GANC, references to the INC and GANC are used interchangeably.

0143B. Functional Entities

01441. User Equipment (UE)

0145The UE includes the functions that are required to access the Iu-mode GAN. In some embodiments, the UE additionally includes the functions that are required to access the A/Gb-mode GAN. In some embodiments, the User Equipment (UE) is a dual mode (e.g., GSM and unlicensed radios) handset device with capability to switch between the two modes. The user equipment can support either Bluetooth® or IEEE 802.11 protocols. In some embodiments, the UE supports an IP interface to the access point. In these embodiments, the IP connection from the GANC extends all the way to the UE. In some other embodiments, the User Equipment (UE) is a standard 3G handset device operating over licensed spectrum of the provider.

0146In some embodiments, the user equipment includes a cellular telephone, smart phone, personal digital assistant, or computer equipped with a subscriber identity mobile (SIM) card for communicating over the licensed or unlicensed wireless networks. Moreover, in some embodiments the computer equipped with the SIM card communicates through a wired communication network.

0147Alternatively, in some embodiments the user equipment includes a fixed wireless device providing a set of terminal adapter functions for connecting Integrated Services Digital Network (ISDN), Session Initiation Protocol (SIP), or Plain Old Telephone Service (POTS) terminals to the ICS. Application of the present invention to this type of device enables the wireless service provider to offer the so-called landline replacement service to users, even for user locations not sufficiently covered by the licensed wireless network. Moreover, some embodiments of the terminal adapters are fixed wired devices for connecting ISDN, SIP, or POTS terminals to a different communication network (e.g., IP network) though alternate embodiments of the terminal adapters provide wireless equivalent functionality for connecting through unlicensed or licensed wireless networks.

01482. Femtocell Access Point (FAP)

0149The FAP is a licensed access point which offers a standard radio interface (Uu) for UE connectivity. The FAP provides radio access network connectivity for the UE using a modified version of the standard GAN interface (Up). In some embodiments, the FAP is equipped with either a standard 3G USIM or a 2G SIM.

0150In accordance with some embodiments, the FAP <b>610</b> will be located in a fixed structure, such as a home or an office building. In some embodiments, the service area of the FAP includes an indoor portion of a building, although it will be understood that the service area may include an outdoor portion of a building or campus.

01513. Generic Access Network Controller (GANC)

0152The GANC <b>510</b> is an enhanced version of the GANC defined in “Generic access to the A/Gb interface; Stage 2”, 3GPP TS 43.318 standard, hereinafter “TS 43.318 standard”. The GANC appears to the core network as a UTRAN Radio Network Controller (RNC). The GANC includes a Security Gateway (SeGW) <b>520</b> and IP Network Controller (INC) <b>565</b>. In some embodiments (not shown in <figref idref="DRAWINGS">FIG. 5</figref>), the GANC also includes GANC Signaling Gateway <b>635</b>, a GANC Media Gateway (MGW) <b>640</b>, and/or an ATM Gateway (<b>645</b>).

0153The SeGW <b>520</b> provides functions that are defined in TS 43.318 standard and “Generic access to the A/Gb interface; Stage 3”, 3GPP TS 44.318 standard. The SeGW terminates secure access tunnels from the FAP, providing mutual authentication, encryption and data integrity for signaling, voice and data traffic. The SeGW <b>520</b> is required to support EAP-SIM and EAP-AKA authentication for the FAP <b>560</b>.

0154The INC <b>565</b> is the kay GANC element. In some embodiments, the INC is front-ended with a load balancing router/switch subsystem which connects the INC to the other GAN systems; e.g., GANC security gateways, local or remote management systems, etc.

0155The GANC MGW <b>640</b> provides the inter-working function between the Up interface and the Iu-cs user plane. The GANC MGW would provide inter-working between RFC <b>3267</b> based frames received over the Up interface and Iu-UP frames towards the CN. The GANC Signaling GW <b>635</b> provides protocol conversion between SIGTRAN interface towards the INC and the ATM based Iu-cs interface towards the CN. The ATM GW <b>645</b> provides ATM/IP gateway functionality, primarily routing Iu-ps user plane packets between the SeGW (IP interface) and CN (AAL5 based ATM interface).

01564. Broadband IP Network

0157The Broadband IP Network <b>515</b> represents all the elements that collectively, support IP connectivity between the GANC SeGW <b>520</b> function and the FAP <b>560</b>. This includes: (1) Other Customer premise equipment (e.g., DSL/cable modem, WLAN switch, residential gateways/routers, switches, hubs, WLAN access points), (2) Network systems specific to the broadband access technology (e.g., DSLAM or CMTS), (3) ISP IP network systems (edge routers, core routers, firewalls), (4) Wireless service provider (WSP) IP network systems (edge routers, core routers, firewalls), and (5) Network address translation (NAT) functions, either standalone or integrated into one or more of the above systems.

01585. AP Management System (AMS)

0159The AMS <b>570</b> is used to manage a large number of FAPs <b>560</b> including configuration, failure management, diagnostics, monitoring and software upgrades. The access to AMS functionality is provided over secure interface via the GANC SeGW <b>520</b>.

0160Some embodiments of the above mentioned devices, such as the user equipment, FAP, or GANC, include electronic components, such as microprocessors and memory (not shown), that store computer program instructions (such as instructions for executing wireless protocols for managing voice and data services) in a machine-readable or computer-readable medium as further described below in the section labeled “Computer System”. Examples of machine-readable media or computer-readable media include, but are not limited to magnetic media such as hard disks, memory modules, magnetic tape, optical media such as CD-ROMS and holographic devices, magneto-optical media such as optical disks, and hardware devices that are specially configured to store and execute program code, such as application specific integrated circuits (ASICs), programmable logic devices (PLDs), ROM, and RAM devices. Examples of computer programs or computer code include machine code, such as produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.

III. FEMTOCELL PROTOCOL ARCHITECTURE

A. CS Domain

Control Plane Architecture

0161The GAN Femtocell architecture of some embodiments in support of the CS Domain control plane is illustrated in <figref idref="DRAWINGS">FIG. 8</figref>. The figure shows different protocol layers for the UE <b>805</b>, FAP <b>810</b>, Generic IP Network <b>815</b>, SeGW <b>820</b>, INC <b>825</b>, and MSC <b>830</b>. <figref idref="DRAWINGS">FIG. 8</figref> also shows the three interfaces Uu <b>840</b>, Up <b>845</b> and Iu-cs <b>850</b>.

01621. Up Interface for the CS Domain Control Plane

0163The main features of the Up interface <b>845</b> for the CS domain control plane are as follows. The underlying Access Layers <b>846</b> and Transport IP layer <b>848</b> provide the generic connectivity between the FAP <b>810</b> and the GANC (which includes SeGW <b>820</b> and INC <b>825</b>). The IPSec encapsulation security payload (ESP) layer <b>850</b> provides encryption and data integrity.

0164The TCP <b>852</b> provides reliable transport for the GA-RC <b>854</b> between FAP <b>810</b> and GANC and is transported using the Remote IP layer <b>856</b>. The GA-RC <b>854</b> manages the IP connection, including the Femtocell registration procedures.

0165The GA-CSR <b>858</b> protocol performs functionality equivalent to the UTRAN RRC protocol, using the underlying connection managed by the GA-RC <b>854</b>. Protocols, such as MM <b>860</b> and above, are carried transparently between the UE <b>805</b> and MSC <b>830</b>. The GANC terminates the GA-CSR <b>858</b> protocol and inter-works it to the Iu-cs <b>850</b> interface using Radio Access Network Application Part (RANAP) <b>862</b> messaging.

0166The Remote IP layer <b>856</b> is the ‘inner’ IP layer for IPSec tunnel mode and is used by the FAP <b>810</b> to be addressed by the INC <b>825</b>. Remote IP layer <b>856</b> is configured during the IPSec connection establishment. In some embodiments, the Iu-cs signaling transport layers <b>870</b> are per “UTRAN Iu interface signalling transport”, 3GPP TS 25.412 standard, hereinafter “TS 25.412”.

B. CS Domain

User Plane Architecture

0167The GAN Femtocell protocol architecture of some embodiments in support of the CS domain user plane is illustrated in <figref idref="DRAWINGS">FIG. 9</figref>. The figure shows different protocol layers for the UE <b>905</b>, FAP <b>910</b>, Generic IP Network <b>915</b>, SeGW <b>920</b>, Media GW <b>925</b>, and MSC <b>930</b>. <figref idref="DRAWINGS">FIG. 9</figref> also shows the three interfaces Uu <b>935</b>, Up <b>940</b>, and Iu-cs <b>945</b>.

0168The main features of the CS domain user plane are as follows. The underlying Access Layers <b>950</b> and Transport IP layer <b>952</b> provide the generic connectivity between the FAP <b>910</b> and the GANC. The IPSec layer <b>954</b> provides encryption and data integrity.

0169The FAP <b>910</b> frames the CS user data <b>956</b> (received over the air interface) into RFC <b>3267</b> defined frames. RFC <b>3267</b> user data <b>958</b> is transported over the Up interface to the GANC Media GW <b>925</b>. The GANC Media GW <b>925</b> will provide inter-working function <b>960</b> with Iu-UP (e.g., Support Mode) towards the CN. In some embodiments, Iu-UP uses ATM as a transport mechanism between the CN and the GANC Media GW <b>925</b>. In some embodiments, Iu-Up uses IP as a transport mechanism between the CN and the GANC Media GW <b>925</b>. In some embodiments, the CS domain user plane architecture supports AMR codec, as specified in “AMR speech codec; General description”, 3GPP TS 26.071 standard with support for other codec being optional. In some embodiments, the Iu-cs Data transport layers <b>970</b> are per TS 25.414.

C. PS Domain

Control Plane Architecture

0170The GAN Femtocell architecture of some embodiments in support of the PS Domain Control Plane is illustrated in <figref idref="DRAWINGS">FIG. 10</figref>. The figure shows different protocol layers for the UE <b>1005</b>, FAP <b>1010</b>, Generic IP Network <b>1015</b>, SeGW <b>1020</b>, INC <b>1025</b>, and SGSN <b>1030</b>. <figref idref="DRAWINGS">FIG. 10</figref> also shows the three interfaces Uu <b>1040</b>, Up <b>1045</b>, and Iu-ps <b>1050</b>.

0171The main features of the Up interface <b>1045</b> for the PS domain control plane are as follows. The underlying Access Layers <b>1052</b> and Transport IP layer <b>1054</b> provide the generic connectivity between the FAP <b>1010</b> and the GANC. The IPSec layer <b>1056</b> provides encryption and data integrity.

0172TCP <b>1058</b> provides reliable transport for the GA-PSR <b>1060</b> signaling messages between FAP <b>1010</b> and GANC. The GA-RC <b>1062</b> manages the IP connection, including the Femtocell registration procedures. The GA-PSR <b>1060</b> protocol performs functionality equivalent to the UTRAN RRC protocol.

0173Upper layer protocols <b>1064</b>, such as for GMM, SM and SMS, are carried transparently between the UE <b>1005</b> and CN. The GANC terminates the GA-PSR <b>1060</b> protocol and inter-works it to the Iu-ps interface <b>1050</b> using RANAP <b>1070</b>. In some embodiments, the Iu-ps signaling transport layers <b>1080</b> are per TS 25.412.

D. PS Domain

User Plane Architecture

0174<figref idref="DRAWINGS">FIG. 11</figref> illustrates the GAN Femtocell architecture for the PS Domain User Plane of some embodiments. The figure shows different protocol layers for the UE <b>1105</b>, FAP <b>1110</b>, Generic IP Network <b>1115</b>, SeGW <b>1120</b>, Packet Gateway (Packet GW) <b>1125</b>, and SGSN <b>1130</b>. <figref idref="DRAWINGS">FIG. 11</figref> also shows the three interfaces Uu <b>1135</b>, Up <b>1140</b>, and Iu-ps <b>1145</b>.

0175The main features of the Up interface <b>1140</b> for PS domain user plane are as follows. The underlying Access Layers <b>1150</b> and Transport IP layer <b>1155</b> provides the generic connectivity between the FAP <b>1110</b> and the GANC. The IPSec layer <b>1160</b> provides encryption and data integrity. The GTP-U <b>1170</b> protocol operates between the FAP <b>1110</b> and the SGSN <b>1130</b> transporting the upper layer payload (i.e. user plane data) across the Up <b>1140</b> and Iu-ps interfaces <b>1145</b>.

0176The packet GW <b>1125</b> provides either ATM GW functionality for ATM transport or IP GW functionality for IP transport. In some embodiment, the Packet GW <b>1125</b> functionality is combined in the SeGW <b>1120</b>. Additionally, in some embodiments, the Packet GW provides a GTP-U proxy functionality as well, where the GTP-U is optionally terminated in the Packet GW <b>1125</b> on either side. In the embodiments that the Packet GW <b>1125</b> provides ATM GW functionality, the packet GW <b>1125</b> provides transport layer conversion between IP (towards the FAP <b>1110</b>) and ATM (towards the CN). User data <b>1180</b> is carried transparently between the UE <b>1105</b> and CN. In some embodiments, the Iu-ps Data transport layers <b>1180</b> are per TS 25.414.

E. Alternative Embodiments

0177In some embodiments, instead of using separate CSR and PSR protocols for communication between the FAP and the GANC, as described in this Specification, a single protocol, Generic Access Radio Resource Control (GA-RRC) is used. In these embodiments, the GA-CSR <b>858</b> (shown in <figref idref="DRAWINGS">FIG. 8</figref>) and GA-PSR <b>1060</b> (shown in <figref idref="DRAWINGS">FIG. 10</figref>) protocol layers are replaced with one protocol layer GA-RRC. Details of the GA-RRC protocol architecture and messaging are further described in the U.S. patent application Ser. No. 11/778,040, entitled “Generic Access to the Iu Interface”, filed on Jul. 14, 2007. This application is incorporated herein by reference. One of ordinary skill in the art would be able to apply the disclosure of the present application regarding the GA-CSR and GA-PSR protocols to the GA-RRC protocol.

IV. RESOURCE MANAGEMENT

0178A. GA-RC (Generic Access Resource Control)

0179The GA-RC protocol provides a resource management layer, with the following functions. (1) Discovery and registration with GANC, (2) Registration update with GANC, (3) Application level keep-alive with GANC, and (4) Support for identification of the FAP being used for Femtocell access.

01801. States of the GA-RC Sub-Layer

0181<figref idref="DRAWINGS">FIG. 12</figref> illustrates different states of the GA-RC sub-layer in the FAP in some embodiments. As shown, the GA-RC sub-layer in the FAP can be in one of two states: GA-RC-DEREGISTERED <b>1205</b> or GA-RC-REGISTERED <b>1210</b>.

0182The FAP creates and maintains a separate state for the GA-RC sub-layer for each device it registers. For instance, if the FAP registers three UEs, the FAP creates and maintains three separate GA-RC sub-layers for these three UEs. Also, the FAP supports registration for two types of devices i.e. the FAP and the UE. Based on the type of device, the functionality of the GA-RC sub-layer can vary.

0183a) GA-RC Sub-Layer for Device Type FAP

0184For the FAP device type, the GA-RC sub-layer is in the GA-RC-DEREGISTERED state <b>1205</b> upon power-up of the FAP. In this state, the FAP has not registered successfully with the GANC. The FAP may initiate the Registration procedure when in the GA-RC-DEREGISTERED state <b>1205</b>. The FAP returns to GA-RC-DEREGISTERED state <b>1205</b> on loss of TCP or IPSec connection or on execution of the De-registration procedure. Upon transition to GA-RC-DEREGISTERED state <b>1205</b>, the FAP must trigger an implicit deregistration all the UEs currently camped on the FAP.

0185In the GA-RC-REGISTERED state <b>1210</b>, the FAP is registered with the Serving GANC. The FAP has an IPSec tunnel and a TCP connection established to the Serving GANC through which the FAP may exchange GA-RC, GA-CSR and GA-PSR signaling messages with the GANC. While the FAP remains in the GA-RC-REGISTERED state <b>1210</b> it performs application level keep-alive with the GANC.

0186b) GA-RC Sub-Layer for Device Type UE

0187For the UE device type, the GA-RC sub-layer in the FAP (for each UE) is in the GA-RC-DEREGISTERED state <b>1205</b> upon UE rove-in and creation of a subsequent TCP connection between the FAP and the GANC. In this state, the UE has not been registered successfully (by the FAP) with the GANC. The FAP may initiate the Registration procedure when UE specific GA-RC sub-layer is in the GA-RC-DEREGISTERED state <b>1205</b>. The GA-RC sub-layer returns to GA-RC-DEREGISTERED state <b>1205</b> on loss of TCP or IPSec connection or on execution of the De-registration procedure. Upon loss of TCP connection, FAP may attempt to re-establish the corresponding TCP session and perform the synchronization procedure. A failure to successfully re-establish the TCP session will result in GA-RC layer transitioning to GA-RC-DEREGISTERED state <b>1205</b>. The GA-RC sub-layer for UE can also transition to the GA-RC-DEREGISTERED state <b>1205</b> if the corresponding GA-RC sub-layer for the FAP is in GA-RC-DEREGISTERED state <b>1205</b>.

0188In the GA-RC-REGISTERED state <b>1210</b>, the UE has been registered successfully (by the FAP) with the Serving GANC. The FAP has a shared IPSec tunnel and a new TCP connection established to the Serving GANC through which the FAP may exchange GA-RC, GA-CSR and GA-PSR signaling messages (for each registered UE) with the GANC. For each of the UE device types, the FAP will perform an application level keep-alive with the GANC on the corresponding TCP session.

0189In the GA-RC-REGISTERED state, the UE is camped on the Femtocell and may either be idle or the UE may be active in the Femtocell (e.g., a RRC connection may have been established). In some embodiments, an idle UE is a UE that is not currently engaged in a voice or data communication.

0190B. GA-CSR (Generic Access Circuit Switched Resources)

0191The GA-CSR protocol provides a circuit switched services resource management layer which supports the following functions: (1) setup of transport channels for CS traffic between the FAP and GANC, (2) direct transfer of NAS messages between the UE (or the FAP if the FAP supports local services) and the core network, and (3) other functions such as CS paging and security configuration.

01921. States of the GA-CSR Sub-layer

0193<figref idref="DRAWINGS">FIG. 13</figref> illustrates the state diagram in some embodiments for GA-CSR in the FAP for each UE. As shown, the GA-CSR sub-layer in the FAP (for each UE) can be in two states: GA-CSR-IDLE <b>1305</b> or GA-CSR-CONNECTED <b>1310</b>.

0194The GA-CSR state for each UE enters the GA-CSR-IDLE state <b>1305</b> upon rove-in to the FAP and successful registration of the UE by the FAP with the Serving GANC. This switch may occur only when the GA-RC state for the UE is in the GA-RC-REGISTERED state <b>1210</b>.

0195The UE GA-CSR moves from the GA-CSR-IDLE state <b>1305</b> to the GA-CSR-CONNECTED state <b>1310</b> when the GA-CSR connection is established and returns to GA-CSR-IDLE state <b>1305</b> when the GA-CSR connection is released. Upon GA-CSR connection release, an indication that no dedicated CS resources exist is passed to the upper layers.

0196A GA-CSR connection for each UE is typically established by the FAP when upper layers messages (NAS layer) for the specific UE need to be exchanged with the network. The GA-CSR connection release can be triggered by the GANC or the FAP. If a FAP supports local services (Terminal Adaptor functionality) using the FAP SIM, there would be similar GA-CSR state for the FAP.

0197C. GA-PSR (Generic Access Packet Switched Resources)

0198The GA-PSR protocol provides a packet switched services resource management layer which supports the following functions: (1) setup of transport channels for PS traffic between the FAP (for each UE) and network, (2) direct transfer of NAS messages between the UE and the PS core network, (3) transfer of GPRS user plane data, and (4) other functions such as PS paging and security configuration.

01991. States of the GA-PSR Sub-Layer

0200<figref idref="DRAWINGS">FIG. 14</figref> illustrates the state diagram in some embodiments for GA-PSR in the FAP for each UE. As shown, the GA-PSR sub-layer for each UE can be in two states: GA-PSR-IDLE <b>1405</b> or GA-PSR-CONNECTED <b>1410</b>.

0201The GA-PSR state for each UE enters the GA-PSR-IDLE state <b>1405</b> upon rove-in to the FAP and successful registration of the UE by the FAP with the Serving GANC. This switch may occur only when the GA-RC state for the UE is in the GA-RC-REGISTERED state <b>1210</b>.

0202The UE GA-PSR moves from the GA-PSR-IDLE state to the GA-PSR-CONNECTED state <b>1410</b> when the GA-PSR connection is established and returns to GA-PSR-IDLE state <b>1405</b> when the GA-PSR connection is released. Upon GA-PSR connection release, an indication that no dedicated PS resources exist is passed to the upper layers. A GA-PSR connection for each UE is typically established by the FAP when upper layers messages (NAS layer) for the specific UE need to be exchanged with the network. The GA-PSR connection release can be triggered by the GANC or the FAP.

0203The GA-PSR Transport Channel (GA-PSR TC) provides the association between the FAP (for each UE) and GANC for the transport of PS user data over the Up interface. It is further described in “GA-PSR Transport Channel Management Procedures” Section, below. If a FAP supports local services (Terminal Adaptor functionality) using the FAP SIM, there would be similar GA-PSR state and GA-PSR TC for the FAP.

0204D. GA-CSR and GA-PSR Connection Handling

0205The GA-CSR and GA-PSR connections are logical connections between the FAP and the GANC for the CS and PS domain respectively. The GA-CSR (or the GA-PSR) connection is established when the upper layers in the FAP request the establishment of a CS (or PS) domain signaling connection and the corresponding GA-CSR (or GA-PSR) is in GA-CSR-IDLE (or GA-PSR-IDLE) state, i.e. no GA-CSR (or GA-PSR) connection exists between the FAP and GANC for the specific UE. In some embodiments, the upper layer in the FAP requests the establishment of GA-CSR (or the GA-PSR) connection, when the FAP receives a corresponding higher layer (i.e. NAS layer) message over the air interface (i.e. over the RRC connection) for the specific UE. In some embodiments, between the UE and the FAP, a single RRC connection is utilized for both CS and PS domain.

0206When a successful response is received from the network, GA-CSR (or GA-PSR) replies to the upper layer that the CS (or PS) domain signaling has been established and enters the corresponding connected mode (i.e., the GA-CSR-CONNECTED or GA-PSR-CONNECTED state). The upper layers have then the possibility to request transmission of a NAS messages for CS (or PS) services to the network over the corresponding GA-CSR (or GA-PSR) connection.

02071. FAP Initiated GA-CSR Connection Establishment

0208<figref idref="DRAWINGS">FIG. 15</figref> illustrates successful establishment of the GA-CSR connection when initiated by the FAP <b>1505</b> in some embodiments. As shown, the FAP <b>1505</b> initiates GA-CSR connection establishment by sending (in Step <b>1</b>) the GA-CSR REQUEST message to the INC <b>1510</b>. This message includes the Establishment Cause indicating the reason for GA-CSR connection establishment.

0209INC <b>1510</b> signals the successful response to the FAP <b>1505</b> by sending (in Step <b>2</b>) the GA-CSR REQUEST ACCEPT and the FAP <b>1505</b> enters the GA-CSR-CONNECTED state. Alternatively, the INC <b>1510</b> may return (in Step <b>3</b>) a GA-CSR REQUEST REJECT indicating the reject cause. As shown, MSC <b>1515</b> plays no role in the FAP initiated GA-CSR connection establishment.

02102. GA-CSR Connection Release

0211<figref idref="DRAWINGS">FIG. 16</figref> shows release of the logical GA-CSR connection between the FAP <b>1605</b> and the INC <b>1610</b> in some embodiments. As shown, the MSC <b>1615</b> indicates (in Step <b>1</b>) to the INC <b>1610</b> to release the CS resources (both control and user plane resources) allocated to the FAP <b>1605</b>, via the Tu Release Command message. The INC <b>1610</b> confirms (in Step <b>2</b>) resource release to MSC <b>1615</b> using the Tu Release Complete message.

0212The INC <b>1610</b> commands (in Step <b>3</b>) the FAP <b>1605</b> to release resources for the specific UE connection, using the GA-CSR RELEASE message. The FAP <b>1605</b> confirms (in Step <b>4</b>) resource release to the INC <b>1610</b> using the GA-CSR RELEASE COMPLETE message and the GA-CSR state in the FAP <b>1605</b> changes to GA-CSR-IDLE.

02133. FAP Initiated GA-PSR Connection Establishment

0214<figref idref="DRAWINGS">FIG. 17</figref> shows successful establishment of the GA-PSR Connection when initiated by the FAP <b>1705</b> in some embodiments. As shown, the FAP <b>1705</b> initiates GA-PSR connection establishment by sending (in Step <b>1</b>) the GA-PSR REQUEST message to the INC <b>1710</b>. This message includes the Establishment Cause indicating the reason for GA-PSR connection establishment.

0215The INC <b>1710</b> signals the successful response to the FAP <b>1705</b> by sending the GA-PSR REQUEST ACCEPT and the FAP <b>1705</b> enters the GA-PSR-CONNECTED state. Alternatively, the INC <b>1710</b> may return (in Step <b>3</b>) a GA-PSR REQUEST REJECT indicating the reject cause. As shown, SGSN <b>1715</b> plays no role in the FAP initiated GA-CSR connection establishment.

02164. GA-PSR Connection Release

0217<figref idref="DRAWINGS">FIG. 18</figref> illustrates release of the logical GA-PSR connection between the FAP <b>1805</b> and the GANC in some embodiments. As shown, the SGSN <b>1815</b> indicates (in Step <b>1</b>) to the INC <b>1810</b> to release the PS resources (both control and user plane resources) allocated to the FAP, via the Iu Release Command message.

0218The INC <b>1810</b> confirms (in Step <b>2</b>) resource release to SGSN <b>1815</b> by using the Iu Release Complete message. The INC <b>1810</b> commands (in Step <b>3</b>) the FAP <b>1805</b> to release resources for the specific UE connection, using the GA-PSR RELEASE message. The FAP <b>1805</b> confirms (in Step <b>4</b>) resource release to the GANC using the GA-PSR RELEASE COMPLETE message and the GA-PSR state in the FAP <b>1805</b> changes to GA-PSR-IDLE.

V. MOBILITY MANAGEMENT

0219A. UE Addressing

0220The IMSI associated with the SIM or USIM in the UE is provided by the FAP to the INC when it registers a specific UE attempting to camp on the FAP. The INC maintains a record for each registered UE. For example, IMSI is used by the INC to find the appropriate UE record when the INC receives a RANAP PAGING message.

0221B. Femtocell Addressing

0222The IMSI associated with the SIM or USIM in the FAP is provided by the FAP to the INC when it registers. The INC maintains a record for each registered FAP.

0223The Public IP address of the FAP is the address used by the FAP when it establishes an IPSec tunnel to the GANC Security Gateway. This identifier is provided by the GANC Security Gateway to the AAA server. In some embodiments, this identifier is used by the GANC network systems to support location services (including E911) and fraud detection. In some embodiments, this identifier is used by service providers to support QoS for IP flows in managed IP networks.

0224The Private IP address of the FAP (also referred to as the “remote IP address”) is used by the FAP “inside the IPSec tunnel.” This identifier is provided by the INC to the AAA server via the S1 interface when the FAP registers for Femtocell service. This identifier may be used by the Femtocell network systems in the future to support location services (including E911) and fraud detection.

0225In some embodiments, the Access Point ID (AP-ID) is the MAC address of the Femtocell access point through which the UE is accessing Femtocell services. This identifier is provided by the FAP to the INC via the Up interface, and by the INC to the AAA server via the S1 interface, when the FAP registers for Femtocell service. The AP-ID may be used by the Femtocell network systems to support location services (including E911, as described in “Location Based Routing” Section, below), and may also be used by the service provider to restrict Femtocell service access via only authorized FAPs (as described in “Femtocell Service Access Control” Section, below).

0226C. Femtocell Identification

0227The following points describe the Femtocell Identification strategy.

02281. Location Area, Routing Area, Service Area Identification

0229In order to facilitate the Mobility Management functions in UMTS, the coverage area is split into logical registration areas called Location Areas (for CS domain) and Routing Areas (for PS domain). UEs are required to register with the network each time the serving location area (or routing area) changes. One or more location areas identifiers (LAIs) may be associated with each MSC/VLR in a carrier's network. Likewise, one or more routing area identifiers (RAIs) may be controlled by a single SGSN.

0230The LA and the RA are used in particular when the UE is in idle mode and the UE does not have any active RRC connection. The CN would utilize the last known LA (for CS domain) and RA (for PS domain) for paging of the mobile when active radio connection is not available.

0231The Service Area Identifier (SAI) identifies an area consisting of one or more cells belonging to the same Location Area. The SAI is a subset of location area and can be used for indicating the location of a UE to the CN. SAI can also be used for emergency call routing and billing purposes.

0232The Service Area Code (SAC) which in some embodiments is 16 bits, together with the PLMN-Id and the Location Area Code (LAC) constitute the Service Area Identifier.

0233SAI=PLMN-Id∥LAC∥SAC

0234In some embodiments, it is necessary to assign a distinct LAI to each FAP in order to detect UE's mobility from the macro network to a FAP or from one FAP to another FAP. When a UE moves from the macro network to a FAP, the UE can camp on a FAP via its internal cell selection logic. However, if the UE is in idle mode, there will be no messages exchanged between the UE and the FAP, thus making it difficult for the FAP to detect the presence of the UE. In order to trigger an initial message from UE, upon its camping on a specific FAP, the FAP will need to be assigned distinct location areas than the neighboring macro cells. This will result in the UE's MM layer triggering a Location Update message to the CN via the camped cell i.e. FAP.

0235UE's mobility from one FAP to another FAP must also be detected. The UE's cell selection could select a neighboring FAP and it will camp on the neighboring FAP without any explicit messaging. The neighboring FAP's Service Access Control (SAC) may not allow the camping of that specific UE, but without an initial explicit messaging there wouldn't be a way for the neighboring FAP to detect and subsequently to reject the UE.

0236Assuming the MCC and MNC components of the LAI remain fixed for each operator, LAI distinctiveness would be ensured by allocating a distinct LAC to each FAP, such that the LAC assigned to the FAP is different from the neighboring macro network cells and other neighboring FAPs.

0237However, the LAC space is limited to maximum of 64K (due to the limitation of a 16 bit LAC attribute as specified in “Numbering, addressing and identification”), 3GPP TS 23.003, hereinafter “TS 23.003”. As a result, the LAC allocation scheme must provide a mechanism to re-use the LACs for a scalable solution, and at the same time minimize the operational impact on existing CN elements (MSC/SGSN).

0238In some embodiments, the following solution is utilized to meet the above requirements. The LAC allocation is split into two separate categories: (1) A pool of LACs managed by the FAP/AMS, and (2) A small set of LACs (one per “Iu” interface) managed by the INC.

0239The first set of LACs is used by the FAP/AMS to assign a unique LAC to each FAP such that it meets the following requirements (at the minimum): (1) Uniqueness with regards to the neighboring macro cells as well as other FAPs (this will ensure an initial message from the UE upon Femtocell selection and rove-in), and (2) Resolve conflicts with shared LACs where multiple FAPs sharing the same LAC are not neighbors but are accessed by the same UE (this is to allow the use of “LA not allowed” rejection code for UE rejection).

0240The second set of LACs (a much smaller set) is managed within each INC as follows, with the following key requirements: (1) Minimize the impact on the existing CN elements (such as minimal configuration and operational impact), (2) Seamlessly integrate the existing functionality for routing of emergency calls to appropriate PSAPs, and (3) Seamlessly integrate existing functionality for the generation of appropriate call detail records (CDRs) for billing purposes.

0241To meet the above requirements for the second set of LACs, each INC represents a “SuperLA” for a given Iu interface (i.e. MSC+SGSN interface). This implies the MSC/SGSN can be configured with single Super LAI/Super RAI information for that INC. Note: this does not limit the operator from configuring multiple Super LAI/Super RAI if necessary (e.g., to further subdivide the region served by a single INC into multiple geographic areas).

0242In addition, the INC shall utilize the following mapping functionality for assignment of SuperLA: (1) When macro coverage is reported by the FAP, INC shall support mapping of the reported macro coverage to a Super LAC, Super RAC and Service Area Code (SAC). The number of SACs utilized will be dependent on the granularity which the operator chooses for regional distribution (e.g. for emergency call routing, billing, etc), and (2) When no macro coverage is reported by the FAP, the INC shall have the following logic for the Super LAC/RAC/SAC assignment: (a) Query the AAA via the S1 interface for information on the “provisioned macro coverage” for the given FAP IMSI. If S1 reports macro coverage (based on information stored in the subscriber DB), INC uses S1 macro information to map Super LAC/RAC/SAC as above, and (b) If there is no information about the macro coverage from the S1 query, INC maps the FAP to default Super LAC/RAC/SAC; (this could result in the INC routing traffic to CN in sub-optimal mechanism). To prevent this sub-optimal routing of UE traffic to default MSC/SGSN, the following additional enhancement on the FAP may be utilized: (i) Upon a UE rove-in to this “no coverage” FAP, the FAP can gather information from the UE's initial location update (LU) request (since the UE will report last camped LAI), (ii) The FAP can collect information from multiple UEs and construct a “derived” macro coverage information (the number of UEs utilized to derive macro coverage could be algorithmic), (iii) Using this derived macro coverage information, the FAP shall send a GA-RC Register Update Uplink message to the INC, and (iv) The INC shall utilize the macro coverage information reported via the GA-RC Register Update Uplink message to map the FAP to an appropriate Super LAC/RAC/SAC as above.

0243A distinct LAI for each FAP also implies a distinct RAI since the RAI is composed of the LAI and Routing Area Code (RAC). The LAI and RAI are sent to the FAP via the “System Information” attribute upon successful registration of FAP. The SAI, on the other hand, is relayed to the CN in the “Initial UE message” (used to transfer initial L3 message from UE to the CN).

0244The FAP is expected to provide Super LAC/RAC replacement in the NAS messages from the network to the UE (e.g. LU Accept or RAU accept). The FAP must replace the “Super LAC/RAC” included in the relevant NAS messages from the network, with the appropriate locally assigned LAC/RAC information in messages sent to the UEs camped on the FAP.

02452. 3G Cell Identification

0246A 3G Cell Id identifies a cell unambiguously within a PLMN. A 3G cell identifier is composed as below.

02473G Cell Id=RNC-Id (12 bits)+cell Id (16 bits)

0248In some embodiments, the RNC-Id is 12 bits and cell Id is 16 bits, making the 3G Cell ID a 28 bits value. The 3G Cell Id in UMTS are managed within the UTRAN and are not exposed to the CN. As a result, the cell assignment logic can be localized to the UTRAN as long as it can ensure uniqueness within a given PLMN.

0249The 3G Cell Id assigned to each FAP must be distinct from its neighboring Femtocell primarily to avoid advertisement of the same cell Id in system information broadcast by two adjacent FAPs, considering the fact the physical deployment of the FAPs are ad-hoc and not controlled by the operator. In some embodiments, each INC will be statically provisioned with a unique RNC-Id and the RNC-id will be conveyed to the FAP via the System Information during registration. The FAP will be responsible for the assignment of the 16 bit cell Id locally and construct the 3G cell using the combination of INC supplied RNC-Id and locally assigned cell Id.

0250D. Femtocell Operating Configurations

0251Two Femtocell operating configurations are possible: common core configuration and separate core configuration. In common core configuration, the Femtocell LAI and the umbrella UTRAN's (e.g., the UTRAN that servers the subscriber's neighborhood) LAI are different, and the network is engineered such that the same core network entities (i.e., MSC and SGSN) serve both the Femtocells and the umbrella UMTS cells.

0252The primary advantage of this configuration is that subscriber movement between the Femtocell coverage area and the UMTS coverage area does not result in inter-system (i.e., MAP) signaling (e.g., location updates and handovers are intra-MSC). The primary disadvantage of this configuration is that it requires coordinated Femtocell and UMTS traffic engineering; e.g., for the purpose of MSC &amp; SGSN capacity planning.

0253In separate core configuration, the Femtocell LAI and umbrella UTRAN's LAI are different, and the network is engineered such that different core network entities serve the Femtocells and the umbrella UMTS cells.

0254The advantage of this configuration is that engineering of the Femtocell and UMTS networks can be more independent than in the Common Core Configuration. The disadvantage of this configuration is that subscriber movement between the Femtocell coverage area and the UMTS coverage area results in inter-system (i.e., MAP) signaling.

0255E. Femtocell Registration

0256The Femtocell registration process does not involve any signaling to the PLMN infrastructure and is wholly included within the Femtocell system (i.e., between the FAP, INC, and the AAA). There are two kinds of Femtocell registrations: FAP registration and UE registration.

0257In FAP registration, upon power-up, the FAP registers with the INC. FAP registration serves the following purposes: (1) It informs the INC that a FAP is now connected and is available at a particular IP address. In some embodiments, the FAP creates a TCP connection to the INC before registration. The TCP connection is identified by using one or more of the following information: source IP address, destination IP address, source TCP port, destination TCP port. The INC can extract the FAP IP address from the TCP connection, (2) It provides the FAP with the operating parameters (such as LAI, Cell-Id, etc) associated with the Femtocell service at the current location. The “System Information” content that is applicable to the GAN Femtocell service is delivered to the FAP during the registration process as part of GA-RC REGISTRATION ACCEPT message sent from the INC to the FAP. The FAP utilizes the information to transmit system parameters to the UE over the broadcast control channel and (3) It allows the Femtocell system to provide the service access control (SAC) and accounting functions (e.g., AP restriction and redirection). In some embodiments, the SAC and accounting is done through the S1 interface.

0258In UE registration, upon Femtocell selection and cell camping, the UE initiates a LU message towards the CN via the FAP. The FAP utilizes this message to detect presence of the UE on that specific FAP. The FAP then initiates a registration message towards INC for the camped UE. UE registration by the FAP serves the following purpose: (1) It informs the INC that a UE is now connected through a particular FAP and is available at a particular IP address. The INC keeps track of this information for the purposes of (for example) mobile-terminated calling, and (2) It allows the INC to provide SAC functionality (e.g. using the S1 interface, to validate if the specific UE should be allowed Femtocell services from a specific FAP).

0259F. Mobility Management Scenarios

0260The following scenarios illustrate the message flows involved for various mobility management scenarios via the Femtocell system.

02611. FAP Power On

0262In some embodiments, the FAP is initially provisioned with information (i.e. an IP address or a FQDN) about the Provisioning INC and the corresponding Provisioning SeGW related to that INC. This information can be in the format of either a FQDN or an IP-address or any combination of these. In case the FAP is not provisioned with information about the Provisioning SeGW, the FAP can derive a FQDN of the Provisioning SeGW from the IMSI (as described in TS 23.003). If the FAP does not have any information about either the Default INC or the Serving INC and the associated SeGW stored, then the FAP completes the Discovery procedure towards the Provisioning INC via the associated SeGW. If the FAP has stored information about the Default/Serving INC on which it registered successfully the last time, the FAP skips the discovery procedure and attempt registration with the Default/Serving INC as described below.

0263a) FAP Discovery Procedure

0264<figref idref="DRAWINGS">FIG. 19</figref> illustrates the case in some embodiments when the FAP <b>1905</b> powers on and does not have stored information on the Default/Serving INC, and then performs a discovery procedure with the provisioning GANC <b>1910</b>. The provisioning GANC <b>1910</b> includes a provisioning INC <b>1915</b>, a DNS <b>1920</b>, and a SeGW <b>1925</b>.

0265As shown, if the FAP <b>1905</b> has a provisioned or derived (as described in the FAP power on sub-section, above) FQDN of the Provisioning SeGW, the FAP <b>1905</b> performs (in Step <b>1</b>) a DNS query (via the generic IP access network interface) to resolve the FQDN to an IP address. If the FAP <b>1905</b> has a provisioned IP address for the Provisioning SeGW <b>1925</b>, the DNS steps (Steps <b>1</b> and <b>2</b>) are omitted. In some embodiments, the DNS Server <b>1935</b> is a public DNS server accessible from the FAP. The DNS Server <b>1935</b> returns (in Step <b>2</b>) a response including the IP Address of the Provisioning SeGW <b>1925</b>.

0266Next, the FAP <b>1905</b> establishes (in Step <b>3</b>) a secure tunnel (e.g., an IPSec tunnel) to the Provisioning SeGW <b>1925</b>. If the FAP <b>1905</b> has a provisioned or derived FQDN of the Provisioning INC <b>1915</b>, the FAP <b>1905</b> performs (in Step <b>4</b>) a DNS query (via the secure tunnel) to resolve the FQDN to an IP address. If the FAP has a provisioned IP address for the Provisioning INC <b>1915</b>, the DNS steps (Steps <b>4</b> and <b>5</b>) are omitted. The DNS Server <b>1920</b> of the provisioning GANC <b>1910</b> returns (in Step <b>5</b>) a response including the IP Address of the Provisioning INC <b>1915</b>.

0267Next, the FAP <b>1905</b> sets up a TCP connection to a well-defined port on the Provisioning INC. It then queries (in Step <b>6</b>) the Provisioning INC <b>1915</b> for the Default INC, using GA-RC DISCOVERY REQUEST. The message includes: (1) Cell Info: If the FAP detects macro network coverage then the FAP provides the detected UTRAN cell ID and the UTRAN LAI (for GSM, the FAP provides the GSM cell identification and the GSM LAI). If the FAP does not detect macro network coverage, the FAP provides the last LAI where the FAP successfully registered, along with an indicator that identifies the last GERAN/UTRAN cell (e.g., by including a GERAN/UTRAN coverage Indicator Information Element (IE) which identifies the GERAN or UTRAN cell coverage). The cell Info is the information of neighboring macro cells which can be either GSM or UTRAN cells. There are multiple ways for the FAP to obtain the neighboring cell information, e.g. using pre-configuration on the FAP, obtaining the macro neighbor configuration via AMS, or having the FAP radio scan the neighboring cells. If the macro coverage is GSM, then for the scan approach, the FAP must have the capability and mechanism for scanning GSM cells, (2) FAP Identity: IMSI, and (3) The physical MAC address of the FAP: AP-ID. Optionally, if the INC <b>1915</b> has been configured for Service Access Control (SAC) over S1 interface, the INC <b>1915</b> will via AAA server <b>1930</b> authorize the FAP <b>1905</b> using the information provided in the GA-RC DISCOVERY REQUEST (Steps <b>6</b><i>a</i>-<b>6</b><i>c</i>).

0268The Provisioning INC <b>1915</b> returns (in Step <b>7</b>) the GA-RC DISCOVERY ACCEPT message, using the information provided by the FAP (e.g. the cell ID), to provide the FQDN or IP address of the Default INC and its associated Default SeGW. This is done so the FAP <b>1905</b> is directed to a “local” Default INC in the HPLMN to optimize network performance. The DISCOVERY ACCEPT message also indicates whether the INC and SeGW address provided shall or shall not be stored by the FAP <b>1905</b>.

0269If the Provisioning INC <b>1915</b> cannot accept the GA-RC DISCOVERY REQUEST message, it returns (in Step <b>8</b>) a GA-RC DISCOVERY REJECT message indicating the reject cause. The secure IPSec tunnel to the Provisioning SeGW is released (Step <b>9</b>).

0270It is also be possible to reuse the same IPSec tunnel for FAP Registration procedures. This is the case where a discovery procedure results in the FAP to successfully find a “default” INC and a “default” SeGW. If the default SeGW is same as that used for discovery (i.e. the provisioning SeGW), then the same IPSEC tunnel can be reused. In this case the IPSec tunnel is not released.

0271b) FAP Registration Procedure

0272Following the Discovery procedure the FAP establishes a secure tunnel with the Security Gateway of the Default GANC, provided by the Provisioning GANC in the Discovery procedure, and attempts to register with the Default GANC. <figref idref="DRAWINGS">FIG. 20</figref> illustrates FAP power on registration procedure of some embodiments. The Default GANC may become the Serving GANC for that connection by accepting the registration, or the Default GANC may redirect the FAP to a different Serving GANC. GANC redirection may be based on information provided by the FAP during the Registration procedure, operator chosen policy or network load balancing.

0273As shown in <figref idref="DRAWINGS">FIG. 20</figref>, if the FAP <b>2005</b> was only provided the FQDN of the Default or Serving SeGW <b>2015</b>, the FAP <b>2005</b> performs (in Step <b>1</b>) a DNS query (via the generic IP access network interface) to resolve the FQDN to an IP address. If the FAP <b>2005</b> has a provisioned IP address for the SeGW, the DNS steps (Steps <b>1</b> and <b>2</b>) are omitted. The DNS Server <b>2010</b> returns (in Step <b>2</b>) a response including the IP address of the Default/Serving SeGW <b>2015</b>.

0274Next, the FAP <b>2005</b> sets up (in Step <b>3</b>) a secure IPSec tunnel to the SeGW <b>2015</b>. This step may be omitted if an IPSec tunnel is being reused from an earlier Discovery or Registration. If the FAP <b>2005</b> was provided the FQDN of the Default or Serving INC, the FAP then perform (in Step <b>4</b>) a DNS query (via the secure tunnel) to resolve the FQDN to an IP address. If the FAP <b>2005</b> has an IP address for the INC, the DNS steps (Steps <b>4</b> and <b>5</b>) are omitted. The DNS Server <b>2020</b> returns (in Step <b>5</b>) a response including the IP address of the Default/Serving INC <b>2025</b>.

0275The FAP then sets up a TCP connection to the INC <b>2025</b>. The TCP port can either be a well-known or one that has been earlier received from the network during Discovery or Registration. The FAP attempts to register (in Step <b>6</b>) on the INC <b>2025</b> by transmitting the GA-RC REGISTER REQUEST. In some embodiment, the message includes one or more of the following information: Registration Type, Cell Info, Neighboring FAP Info, the physical MAC address of the FAP, FAP Identity, and location information.

0276The Registration Type indicates that the registering device is a Femtocell AP. This is indicated using the “GAN Classmark” IE (IEs are defined further below). The Cell Info is the neighboring UTRAN/GERAN cell ID retrieved as a result of system scan for neighbor information. The FAP must determine (using either scan results or pre-configuration), a single suitable macro cell information to be sent in the registration.

0277Neighboring FAP Info is information about neighboring FAPs operating in the same PLMN and carrier frequency. This will help provide the INC with information such as the LAI and cell-ids in use by neighboring FAPs. In some embodiments, the neighboring FAP information will not be provided. The physical MAC address of the FAP is the AP-ID (in some embodiments, AP-ID is the MAC address of the FAP associated Ethernet port). The FAP Identity is the IMSI of the FAP. If GPS services are provided, location information is also supported.

0278Optionally, if the INC <b>2025</b> has been configured for Service Access Control (SAC) over S1 interface, the GANC will via AAA server <b>2030</b> authorize the FAP using the information provided in the REGISTER REQUEST (Steps <b>6</b><i>a</i>-<b>6</b><i>c</i>). If the INC <b>2025</b> accepts the registration attempt it responds (in Step <b>7</b>) with a GA-RC REGISTER ACCEPT. The message includes: (1) GAN Femtocell specific system information (e.g.) (i) Location-area identification comprising the mobile country code, mobile network code, and location area code corresponding to the Femtocell, and (ii) 3G Cell identity identifying the cell within the location area corresponding to the Femtocell. The message also includes GAN Femtocell Capability Information indicated via the use of “GAN Control Channel” IE. In some embodiments, the GAN Femtocell Capability Information include indications as to whether early Classmark sending is allowed, the GAN mode of operation, whether GPRS is available, and whether the GAN supports dual transfer mode.

0279In the case the INC <b>2025</b> accepts the registration attempt, the TCP connection and the secure IPSec tunnel are not released and are maintained as long as the FAP is registered to this GANC. INC does not provide operation parameters for radio management (such as carrier frequency, scrambling code, etc) to the FAP. It is expected that the FAP would obtain this information via the AMS or other pre-provisioning mechanisms.

0280Alternatively, the INC <b>2025</b> may reject the request. In this case, it responds (in Step <b>8</b>) with a GA-RC REGISTER REJECT indicating the reject cause. The TCP connection and the secure IPSec tunnel are released and the FAP <b>2005</b> shall act as defined in the “abnormal cases” Section, below. Alternatively, if the GANC has to redirect the FAP <b>2005</b> to (another) Serving GANC, it responds (in Step <b>9</b>) with a GA-RC REGISTER REDIRECT providing the FQDN or IP address of the target Serving INC and the associated SeGW. In this case the TCP connection is released (in Step <b>10</b>) and the secure IPSec tunnel is optionally released depending on if the network indicates that the same IPSec tunnel can be reused for the next registration. The GA-RC REGISTER REDIRECT message includes either a single Serving SeGW and GANC address or a list of PLMN identities and associated Serving SeGW and GANC addresses and an indication of whether GANC address(es) can be stored in the FAP for future use.

0281c) Abnormal Cases

0282If the Serving INC rejects the Register Request and does not provide redirection to another Serving INC, the FAP shall re-attempt Registration to the Default INC including a cause indicating the failed registration attempt and the Serving INC and SeGW with which the Register Request failed. The FAP should also delete all stored information about this Serving GANC.

0283If the Default INC rejects a Registration Request and is unable to provide redirection to suitable Serving INC, the FAP may re-attempt the Discovery procedure to the Provisioning INC (including a cause indicating the failed registration attempt and the Default INC provided in the last Discovery procedure). The FAP should also delete all stored information about the Default GANC. The possible register reject causes for FAP registration attempts are Network Congestion, Location Not Allowed, Geo-Location not know, IMSI not allowed, AP not allowed, and Unspecified.

02842. FAP Initiated FAP Synchronization after TCP Connection Reestablishment

0285In some embodiments, when FAP receives TCP Reset (TCP RST) after TCP connection failure, the FAP tries to re-establish the signaling connection using GA-RC Synchronization procedure. <figref idref="DRAWINGS">FIG. 21</figref> illustrates the messages associated with the FAP initiated synchronization procedure in some embodiments.

0286a) Initiation of the FAP Synchronization Procedure by the FAP

0287In some embodiments, when FAP receives TCP RESET after TCP connection failure, the FAP attempts to re-establish TCP connection once. After successfully re-establishing TCP connection, the FAP <b>2105</b> sends (in Step <b>1</b>) GA-RC SYNCHRONIZATION INFORMATION to the GANC <b>2110</b> to synchronize the state information. When the FAP is unsuccessful in re-establishing the TCP connection, the FAP releases the related local GA-CSR or GA-PSR resources, and continues as per sub-section “Handling of Lower Layer faults” described further below.

0288b) Processing of the FAP Synchronization Information Message by the GANC

0289Upon receiving the GA-RC SYNCHRONIZATION INFORMATION message from the FAP, the GANC updates the FAP state information as specified in the request. The GANC also verifies that the binding (IMSI, inner IP address) as received in the GA-RC SYNCHRONIZATION INFORMATION is the same as the one that the FAP used as identity for authentication to the GANC-SeGW.

02903. System Selection

0291In some embodiments, in the combined 3G network, both standard UMTS RNS and UMA Femtocell network coexists within the same or different PLMN. Standard UMTS UEs utilize both access options whichever is more optimal in a specific scenario. In these embodiment, no changes are required to the PLMN selection procedures in the NAS layers (MM and above) in the UE as described in “Non-Access-Stratum functions related to Mobile Station (MS) in idle mode”, 3GPP TS 23.122. Also, in these embodiments, no changes are required to the standard cell selection mechanism as described in “User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode”, 3GPP TS 25.304. The necessary configuration and the system behavior for rove-in to Femtocell coverage and rove-out to the macro network coverage are described in the following paragraphs.

0292During the service activation or provisioning update, the UMA Femtocell Network provides the FAP with radio parameters such as the operating UARFCN and a list of primary scrambling codes for the Femtocell. The provisioning parameters will also include the list of UARFCNs/scrambling codes associated with the neighboring macro cells.

0293The FAP then performs a neighborhood scan for the existence of macro coverage using the macro UARFCN information. If multiple macro network cells are detected in the FAP scan, the FAP selects the best suitable macro cell for the purpose of reporting it to the Serving INC during FAP registration. The FAP also stores the macro cell list to be provided as a neighbor list for the camping UEs.

0294The FAP also scans the neighborhood for the existence of other FAPs within the same PLMN. It then selects unused {UARFCN, SC} pair from the provisioned list of available pairs such that the selected {UARFCN, SC} does not conflict with any neighboring FAP's {UARFCN, SC} combination.

0295The FAP attempts to register with the Serving INC (obtained via Discovery/Registration mechanisms as described in the FAP discovery procedure and FAP registration procedure Sections above) and includes information about the selected macro cell and a list of neighboring FAPs. The Serving INC uses information provided during registration to assign network operating parameters for the registering FAP such as the LAI, 3G cell-id, service area, etc.

0296The Serving INC returns the network operating parameters to the registering FAP using the register accept message. The FAP uses a combination of information obtained through the initial provisioning and Registration and broadcasts appropriate System Information to UEs to be able to select Femtocell service and camp on the FAP.

0297The macro network RNCs are provisioned with the list of {UARFCN, SC} associated with Femtocell neighbors. Since the Femtocell network has to be able to scale to millions of FAPs and the deployment location cannot be controlled, the macro network RNCs are provisioned with a list of 5-10 {UARFCN, SC} combinations corresponding to the neighboring FAPs. As a result of the limitations associated with neighbor list provisioning on the macro RNC, the FAP will need to select one of the 5-10 provisioned {UARFC, SC} pairs for its operation such that no two neighboring FAPs (determined via FAPs' scan) shall re-use the same pair for its operation.

0298The macro RNC shall provide the FAP neighbor list information to the UEs camped on the macro network and using the specific RNC. This will result in the UEs making periodic measurements on the FAP neighbor list.

0299As the UE comes within the coverage area of the FAP and its signal level becomes stronger, the UE will select the Femtocell. The UE cell-reselection i.e. rove-in to FAP cell can be enhanced via two possible mechanisms: (1) The FAP cell can be in a different HPLMN (equivalent PLMN list) and will be selected via preferred equivalent PLMN selection. This assumes that the UE's current camped macro cell is not in the equivalent PLMN list, and (2) The FAP will broadcast system information (such as Qqualmin and Qrxlevmin) so that UE shall prefer the FAP cell in the presence of other macro cell coverage.

0300Upon cell reselection and camping on the FAP cell, the UE will initiate a location registration since the FAP LAI is different than the LAI of the previously camped macro cell.

03014. UE Registration

0302The UE, upon camping on the FAP (via its internal cell selection mechanism), will initiate a NAS layer Location Update procedure towards the CN via the FAP (The LU is triggered since the FAP broadcasts a distinct LAI than its neighboring macro cells and other neighboring Femtocells). The FAP will intercept the Location Update message and attempt to register the UE with the INC as illustrated in <figref idref="DRAWINGS">FIG. 22</figref>. A person of ordinary skill in the art would appreciate that a UE always initiates location update procedure towards the core network, i.e., the UE uses the upper protocol layers that are directly exchanged with the core network. As described in this sub-section and several other sub-sections below, the disclosed FAP has the capability to intercept this message and to attempt to register the UE with the INC.

0303As shown, the UE <b>2205</b> establishes (in Step <b>1</b><i>a</i>) a radio resource control (RRC) connection with the FAP <b>2210</b> on which it camps. The UE <b>2205</b> starts (in Step <b>1</b><i>b</i>) a Location Update procedure towards the CN. In some embodiments, for networks supporting network mode <b>1</b>, where there is a Gs interface between the MSC and SGSG, the UE triggers a combined Routing Area (RA)/Location Area (LA) update instead of the initial LA update upon rove-in to FAP. The FAP <b>2210</b> will intercept the Location Update request (or the combined RA/LA update request) and attempts to register the UE with the associated Serving INC over the existing IPSec tunnel. Optionally, the FAP may request (in Step <b>1</b><i>c</i>) the IMSI of the UE if the Location Update is done (in Step <b>1</b><i>d</i>) using the TMSI, since the initial registration for the UE must be done using the permanent identity i.e. the IMSI of the UE.

0304Next, the FAP <b>2210</b> sets up (in Step <b>2</b>) a separate TCP connection (for each UE) to a destination TCP port on the INC <b>2215</b>. The INC destination TCP port is the same as that used for FAP registration. The FAP <b>2210</b> attempts to register the UE <b>2205</b> on the INC <b>2215</b> using the UE specific TCP connection by transmitting (in Step <b>3</b>) the GA-RC REGISTER REQUEST. The message includes Registration Type (which indicates that the registering device is a UE. This is indicated using the “GAN Classmark” IE), Generic IP access network attachment point information (i.e., AP-ID), UE Identity (i.e., UE-IMSI), and FAP identity (i.e., FAP-IMSI). In some embodiments, the AP-ID is the MAC address of the FAP.

0305Optionally, if the INC <b>2215</b> has been configured for Service Access Control (SAC) over S1 interface, the INC <b>2215</b> will, via AAA server <b>2220</b>, authorize the UE using the information provided in the REGISTER REQUEST (Steps <b>3</b><i>a</i>-<b>3</b><i>c</i>). The authorization logic on the AAA server <b>2220</b> would also check to see if the UE <b>2205</b> is allowed Femtocell access using the specific FAP.

0306If the INC <b>2215</b> accepts the registration attempt it responds (in Step <b>4</b>) with a GA-RC REGISTER ACCEPT. Next, the FAP <b>2210</b> establishes (in Step <b>5</b>) a GA-CSR connection with the INC <b>2215</b>. The FAP <b>2210</b> encapsulates (in Step <b>6</b>) the Location Update NAS PDU within a GA-CSR UL DIRECT TRANSFER message that is forwarded to the INC <b>2215</b> via the existing TCP connection.

0307Next, the INC <b>2215</b> establishes a SCCP connection to the CN <b>2225</b> and forwards (in Step <b>7</b>) the Location Update request (or the combined RA/LA update request) NAS PDU to the CN <b>2225</b> using the RANAP Initial UE Message. Subsequent NAS messages between the UE <b>2205</b> and core network <b>2225</b> will be sent between INC <b>2215</b> and CN <b>2225</b> using the RANAP Direct Transfer message.

0308Next, the CN <b>2225</b> authenticates (in Step <b>8</b>) the UE <b>2205</b> using standard UTRAN authentication procedures. The CN <b>2225</b> also initiates the Security Mode Control procedure described in the Security Mode Control Subsection under Femtocell Security Section further below. The CN <b>2225</b> indicates (in Step <b>9</b>) it has received the location update and it will accept the location update using the Location Update Accept message to the INC <b>2215</b>.

0309The INC <b>2215</b> forwards (in Step <b>10</b>) this message to the FAP <b>2210</b> in the GA-CSR DL DIRECT TRANSFER. The FAP <b>2210</b> will relay (in Step <b>11</b>) the Location Update Accept over the air interface to the UE <b>2205</b>. Once the UE <b>2205</b> has been successfully registered (by the FAP) with the INC <b>2215</b> and performed a successful location update, the FAP <b>2210</b> will expect a periodic LU for that UE (the enabling and the periodicity of the LU is controlled by the FAP via System Information broadcast from the FAP to the UE). This exchange will serve as a keep-alive between the FAP <b>2210</b> and the UE <b>2205</b> and will help the FAP <b>2210</b> detect idle UE's moving away from the camped FAP <b>2210</b> without explicit disconnect from the network.

0310a) Abnormal cases

0311If the Serving INC rejects the UE specific Register Request, the FAP shall reject the corresponding “Location update” request from the UE using appropriate reject mechanisms (example: RRC redirection to another cell or reject the LU with reject cause of “Location Area not allowed”, etc). The FAP shall tear down the corresponding TCP session for the specific UE. The possible register reject causes for UE specific registration attempts are (1) AP not allowed (implies UE not allowed on FAP for the UE specific registration), (2) IMSI not allowed, (3) Location not allowed, (4) Unspecified, and (5) FAP not registered.

03125. UE Rove Out

0313<figref idref="DRAWINGS">FIG. 23</figref> scenario illustrates the case when the UE leaves the Femtocell coverage area while idle. As shown, upon successful GAN registration and location update (LU) of the UE <b>2305</b>, the FAP <b>2310</b> will monitor (in Step <b>1</b>) the UE <b>2305</b> via periodic location updates. The enabling and the periodicity of the LU is controlled by the FAP <b>2310</b> via System Information broadcast from the FAP to the UE. This exchange will serve as a keep-alive between the FAP and the UE.

0314Next, FAP <b>2310</b> determines (in Step <b>2</b>) that the UE <b>2305</b> is no longer camped on the FAP (roved out), as a result of missing a number of periodic location updates from the UE. Once, the FAP determines that the UE has roved out, the FAP informs the GANC that the UE has detached by sending (in Step <b>3</b>) a GA-RC DEREGISTER message to the INC <b>2315</b> using the associated TCP connection. Since a TCP connection from the FAP to the GANC is unique for each UE, sending GA-RC DEREGISTER message on the specific TCP connection implies deregistration of the specific UE. Next, the GANC removes (in Step <b>4</b>) any associated UE context upon receiving the deregister message on the UE specific TCP connection. In some embodiments, the context associated with a UE includes states and other information that the GANC keeps for each UE which is successfully registered. The FAP <b>2310</b> also releases (in Step <b>4</b>) the UE specific TCP connection to the INC.

03156. UE Power Down with IMSI Detach

0316<figref idref="DRAWINGS">FIG. 24</figref> illustrates the case when the UE powers down and performs an IMSI detach via the GAN network in some embodiments. As shown, UE <b>2405</b> in idle mode initiates (in Step <b>1</b>) power off sequence. Next, the UE <b>2405</b> establishes (in Step <b>2</b>) an RRC Connection with the FAP <b>2410</b>. The UE send (in Step <b>3</b>) a MM Layer IMSI-Detach message over the air interface to the FAP. The FAP <b>2410</b> establishes (in Step <b>4</b>) a GA-CSR connection with the INC <b>2415</b>.

0317The FAP <b>2410</b> encapsulates the IMSI-Detach NAS PDU within a GA-CSR UL DIRECT TRANSFER message that is forwarded (in Step <b>5</b>) to the INC <b>2415</b> via the existing TCP connection. The INC <b>2415</b> establishes a SCCP connection to the CN <b>2420</b> and forwards (in Step <b>6</b>) the IMSI-Detach NAS PDU to the CN <b>2420</b> using the RANAP Initial UE Message. The CN <b>2420</b> initiates (in Step <b>7</b>) a normal resource cleanup via RANAP Iu Release Command to the INC <b>2415</b>. The Iu Release from the CN <b>2420</b> results in INC <b>2415</b> tearing down (in Step <b>8</b>) the corresponding GA-CSR connection.

0318Next, INC <b>2415</b> acknowledges (in Step <b>9</b>) resource cleanup via RANAP Iu Release Complete message to the CN. FAP <b>2410</b> deregisters (in Step <b>10</b>) the UE using the UE specific TCP connection. In some embodiments, the FAP utilizes the mechanism described in Subsection “UE rove out” above to detect that the UE has roved and trigger the UE deregistration. As an optimization, the FAP can also monitors the IMSI-Detach NAS message from the UE and trigger deregistration of the UE.

0319Next, the FAP <b>2410</b> releases (in Step <b>11</b>) the UE specific TCP connection. FAP initiates (in Step <b>12</b>) RRC Connection release procedure towards the UE. Finally, the UE powers off (in Step <b>13</b>).

03207. UE Power Down Without IMSI Detach

0321The sequence of events is same as UE Roving out of Femtocell as described in Subsection “UE rove out” above.

03228. Loss of Up Interface Connectivity

0323<figref idref="DRAWINGS">FIG. 25</figref> illustrates the case when Up interface connectivity is lost. As shown, the UE <b>2505</b> is in idle mode. The FAP <b>2510</b> periodically sends (in Step <b>1</b>) GA-RC KEEP ALIVE message to the INC <b>2515</b> to check that the TCP connection exists. In Step <b>2</b>, the TCP (or IP) connectivity between the FAP <b>2510</b> and INC <b>2515</b> is lost (e.g., due to a broadband network problem).

0324If the INC detects (in Step <b>3</b>) the loss of connectivity, it releases the resources assigned to the FAP (e.g., TCP connection) and deletes the subscriber record (i.e., performs a local deregistration of the FAP). Optionally, the INC implementation may also delete UE specific connections originating on that FAP.

0325If the FAP <b>2510</b> detects (in Step <b>4</b>) the loss of TCP connectivity and if the loss is on the FAP specific TCP connection, the FAP <b>2510</b> attempts (in Step <b>5</b>) to re-establish the TCP connection and re-register with the INC. If the FAP re-establishes connectivity and re-registers before the INC detects the problem, the INC must recognize that the FAP is already registered and adjust accordingly (e.g., release the old TCP connection resources). In some embodiment, the FAP specific TCP is a unique TCP connection dedicated to the FAP and is used for FAP IMSI related signaling to the INC such as FAP registration, FAP call setup if the FAP offers local calling using the FAP IMSI, etc.

0326Different embodiments use different methods for the FAP to detect the loss of a TCP connection. In some embodiments, the TCP sub-layer (TCP stack) in the FAP indicates (to the upper layers) if the connectivity to the other end point (i.e., the INC) is lost. The notification from the TCP sub-layer on the FAP can happen either when the upper layers attempt to transmit data over the TCP connection or the stack can detect connectivity loss via a TCP Keep Alive mechanism.

0327When the FAP is unsuccessful in re-establishing connectivity, the FAP will do the followings (not shown) to deregister all the UEs currently camped on the FAP: (1) The FAP sends a GA-RC DEREGISTER message to the INC using the currently established TCP connection for each UE, (2) releases the TCP connection towards the GANC, and (3) releases all resources associated with the deregistered UE.

0328Additionally, the FAP <b>2510</b> forces (in Step <b>6</b>) all the UEs, currently camped on that FAP, to do a cell-reselection and rove out of Femtocell coverage. If the TCP connectivity loss is detected on the UE specific connection, the FAP will deregister the UE and trigger cell reselection on the UE immediately without attempting to re-establish the UE specific TCP connection. Finally, the UE <b>2505</b>, as a result of the cell re-selection, will switch (in Step <b>7</b>) to UMTS macro cell <b>2520</b> (if UMTS macro network coverage is available).

03299. INC-Initiated Deregister

0330In some embodiments, the INC deregisters the FAP under the following error cases: (1) INC receives GA-RC REGISTER UPDATE UPLINK message, but FAP is not registered, (2) INC receives GA-RC REGISTER UPDATEUPLINK message, but encounters a resource error and cannot process the message, (3) INC receives GA-RC REGISTER UPDATE UPLINK message with new macro network cell information, and the macro cell is Femtocell-restricted, and (4) INC receives a GA-RC REGISTER UPDATE UPLINK message and sends a request to the AAA server for a registered FAP, and one of the following happens: (a) INC receives an authentication failure for the user from AAA server, (b) INC doesn't receive a response from AAA server, and transaction timer expires, or (c) S1 interface is enabled but no AAA server is configured, so the user couldn't be authenticated. In some embodiments, the INC deregisters the UE when the INC receives GA-RC SYNCHRONIZATION INFORMATION message for a UE that is not registered.

033110. FAP-initiated Register Update

0332<figref idref="DRAWINGS">FIG. 26</figref> illustrates a scenario where the FAP initiates a registration update in some embodiments. As shown, a register update is triggered (in Step <b>1</b>) in the FAP <b>2605</b> (e.g., Detection of macro network coverage). The FAP sends (in Step <b>2</b>) a GA-RC REGISTER-UPDATE-UPLINK to the INC <b>2610</b>.

0333The INC <b>2610</b> exchanges (in Steps <b>3</b><i>a</i>-<b>3</b><i>c</i>) S1 RADIUS messages with the AAA server <b>2615</b> for service access control (SAC). Based on the outcome of SAC, additional procedures may be triggered (in Step <b>4</b>) by this operation (e.g., deregistration or register update downlink).

033411. INC-initiated Register Update

0335<figref idref="DRAWINGS">FIG. 27</figref> illustrates a scenario where the INC initiates a registration update. As shown, a register update is triggered (in Step <b>1</b>) in the INC <b>2715</b> (e.g. due to change in SAC list for the FAP, or change in System Information, etc).

0336Next, the INC <b>2715</b> sends (in Step <b>2</b>) a GA-RC REGISTER UPDATE DOWNLINK message to the FAP <b>2710</b>. As shown, some other procedures may be triggered (in Step <b>3</b>) by this operation (e.g. FAP <b>2710</b> rejecting UEs <b>2705</b> due to updated SAC list received from the INC).

033712. FAP Initiated UE Synchronization after TCP Connection Reestablishment

0338In some embodiments, when FAP receives TCP RST after TCP connection failure, the FAP tries to re-establish the signaling connection using GA-RC Synchronization procedure. <figref idref="DRAWINGS">FIG. 28</figref> illustrates the FAP initiated synchronization procedure in some embodiments.

0339a) Initiation of the UE Synchronization Procedure by the FAP

0340In some embodiments, when FAP receives TCP RST after TCP connection failure, the FAP attempts to re-establish TCP connection once. As shown in <figref idref="DRAWINGS">FIG. 28</figref>, after successfully re-establishing TCP connection, the FAP <b>2805</b> sends (in Step <b>1</b>) GA-RC SYNCHRONIZATION INFORMATION to the GANC <b>2810</b> to synchronize the UE's state information. When unsuccessful, the FAP releases the resources for the UE and forces the UE to rove-out of the FAP and select an alternate cell (either a macro cell or another FAP) for camping

0341b) Processing of the UE Synchronization Information Message by the GANC

0342Upon receiving the GA-RC SYNCHRONIZATION INFORMATION message from the FAP on a UE's TCP connection, the GANC updates the UE state information as specified in the request. The GANC also verifies that the associated FAP is in the registered state. When the FAP is not in registered state, the GANC deregisters the UE by sending a GA-RC-DEREGISTER message (not shown) with reject cause code “FAP not registered” to the FAP on the UE's TCP connection. When the GA-RC layer in the GANC has submitted the GA-RC DEREGISTER message to the TCP layer, it initiates the release of its half of the bidirectional TCP connection. The GANC also verifies that the binding (IMSI, TCP connection) as received in the GA-RC SYNCHRONIZATION INFORMATION is valid.

VI. CALL MANAGEMENT

0343A. Voice Bearer Establishment (Using Iu-UP over AAL2)

0344<figref idref="DRAWINGS">FIG. 29</figref> illustrates the normal procedures associated with successfully establishing the voice bearer between the UE and MSC for mobile originated (MO) or mobile terminated (MT) call purposes in some embodiments. As shown, the signaling for a call origination or termination is in progress (in Step <b>1</b>) between UE <b>2905</b>, FAP <b>2910</b>, GANC MGW <b>2915</b>, INC <b>2920</b>, and MSC <b>2925</b>. The MSC <b>2925</b> sends (in Step <b>2</b>) a RANAP Assignment Request (RAB) message to the INC <b>2920</b>. The assignment request includes the address for ALCAP signaling (an ATM E.164 or NSAP address) and also the binding-id.

0345Next, the INC <b>2920</b> requests (in Step <b>3</b>) the GANC MGW <b>2915</b> to prepare a bearer connection between the endpoints (VoIP towards the FAP and Iu-UP over AAL2 towards the MSC). The MGW <b>2915</b> initiates (in Step <b>4</b>) ALCAP signaling towards the MSC <b>2925</b> using the ATM address and the binding-id.

0346Next, the MSC <b>2925</b> acknowledges (in Step <b>5</b>) the AAL2 connection request using the ALCAP Establish confirm message. At this point (Step <b>6</b>) an AAL2 connection with appropriate QoS exists between the GANC MGW and the MSC. The GANC MGW then sends (in Step <b>7</b>) an Iu-UP control (Iu-INIT) message over this AAL2 connection to request Iu-UP initialization

0347The MSC <b>2925</b> responds (in Step <b>8</b>) with Iu-UP init acknowledgement (Iu-INIT ACK). Next, the MGW <b>2915</b> assigns a MGW IP address and port for the VoIP side of the connection. The MGW sends (in Step <b>9</b>) the VoIP information to the INC using a Prepare Bearer Ack message. Next, the INC <b>2920</b> sends (in Step <b>10</b>) a GA-CSR ACTIVATE CHANNEL message to the FAP <b>2910</b> and starts a timer (e.g., Tqueuing, as described in “UTRAN Iu interface Radio Access Network Application Part (RANAP) signaling”, 3GPP TS 25.413) to ensure that the RANAP Assignment Response is sent to the MSC on or before the expiry of Tqueuing. The GA-CSR ACTIVATE CHANNEL message includes the VoIP connection description created by the GANC MGW.

0348The FAP <b>2910</b> initiates (in Step <b>11</b>) appropriate RRC layer Radio Bearer Setup message towards the UE <b>2905</b>. The UE confirms (in Step <b>12</b>) the setup via Radio Bearer Setup Complete message to the FAP. The FAP sends (in Step <b>13</b>) a GA-CSR ACTIVATE-CHANNEL-ACKNOWLEDGE message to the INC, including the local IP address and port to be used for the VoIP connection.

0349The INC requests (in Step <b>14</b><i>a</i>) the GANC MGW, to modify the previously created connection and send the voice stream to the IP address and port provided by the FAP. The GANC MGW acknowledges (in Step <b>14</b><i>b</i>) the connection modification. The INC <b>2920</b> acknowledges (in Step <b>15</b>) completion of the traffic channel establishment to the FAP <b>2910</b> via the GA-CSR ACTIVATE-CHANNEL COMPLETE message.

0350The INC <b>2920</b> signals (in Step <b>16</b>) the MSC <b>2925</b> about the RAB assignment completion. At this point (Steps <b>17</b><i>a</i>-<b>17</b><i>c</i>), there is voice bearer between the UE <b>2905</b> and MSC <b>2925</b> via the FAP <b>2910</b> and the GANC MGW <b>2915</b>. The rest of the call establishment continues after the voice bearer establishment.

0351B. Call Management Scenarios

0352The following scenarios illustrate the message flows involved for various call management scenarios via the Femtocell.

03531. Mobile Originated Call

0354<figref idref="DRAWINGS">FIG. 30</figref> illustrates a mobile originated call in some embodiments. The scenario shown is for a mobile-to-PSTN call. As shown, the UE <b>3005</b> in GAN idle mode originates (in Step <b>1</b>) a call. The UE <b>3005</b> establishes (in Step <b>2</b>) a RRC connection with the FAP <b>3010</b>. Upon request from the upper layers, the UE sends (in Step <b>3</b>) the CM Service Request to the FAP.

0355The FAP performs (in Step <b>4</b>) the GA-CSR Connection Establishment procedure with the INC as described in previous sections. The FAP <b>3010</b> then forwards (in Step <b>5</b>) the CM Service Request to the INC <b>3015</b> using a GA-CSR UL DIRECT TRANSFER message. Next, the INC <b>3015</b> establishes a SCCP connection to the MSC <b>3020</b> and forwards (in Step <b>6</b>) the CM Service Request to the MSC using the RANAP Initial UE Message. Subsequent NAS messages between the UE and MSC will be sent between INC and MSC using the RANAP Direct Transfer message.

0356Next, the MSC <b>3020</b> authenticates (in Step <b>7</b>) the UE <b>3005</b> using standard UTRAN authentication procedures. The MSC also initiates (in Step <b>7</b>) the Security Mode Control procedure described in previous sections. The UE sends (in Step <b>8</b>) the Setup message to the FAP providing details on the call to the MSC and its bearer capability and supported codecs.

0357The FAP forwards (in Step <b>9</b>) this message within the GA-CSR UL DIRECT TRANSFER between the FAP and the INC. The INC relays (in Step <b>10</b>) the Setup message to the MSC using a RANAP Direct Transfer message.

0358The MSC <b>3020</b> indicates (in Step <b>11</b>) it has received the call setup and it will accept no additional call-establishment information using the Call Proceeding message to the INC. The INC forwards (in Step <b>12</b>) this message to the FAP in the GA-CSR DL DIRECT TRANSFER. The FAP then relays (in Step <b>13</b>) the Call Proceeding message to the UE over the air interface. At this point (Step <b>14</b>) an end to end bearer path is established between the MSC and UE using one of the procedures shown in previous section.

0359The MSC <b>3020</b> constructs (in Step <b>15</b>) an ISUP IAM using the subscriber address, and sends it towards the called party's destination exchange <b>3025</b>. The destination Exchange responds (in Step <b>16</b>) with an ISUP ACM message. The MSC then signals to the UE, with the Alerting message, that the called party is ringing. The message is transferred (in Step <b>17</b>) to the INC.

0360The INC forwards (in Step <b>18</b>) the Alerting message to the FAP in the GA-CSR DL DIRECT TRANSFER. The FAP relays (in Step <b>19</b>) the Alerting message to the UE and if the UE has not connected the audio path to the user, it shall generate ring back to the calling party. Otherwise, the network-generated ring back will be returned to the calling party.

0361The called party answers and the destination Exchange indicates this (in Step <b>20</b>) with an ISUP ANM message. The MSC signals that the called party has answered, via the Connect message. The message is transferred (in Step <b>21</b>) to the INC. The INC forwards (in Step <b>22</b>) the Connect message to the FAP in the GA-CSR DL DIRECT TRANSFER.

0362The FAP relays (in Step <b>23</b>) the Connect message to the UE and the UE connects the user to the audio path. If the UE is generating ring back, it stops and connects the user to the audio path. The UE sends (in Step <b>24</b>) the Connect Ack in response, and the two parties are connected for the voice call. The FAP relays (in Step <b>25</b>) this message within the GA-CSR UL DIRECT TRANSFER between the FAP and the INC.

0363The INC forwards (in Step <b>26</b>) the Connect Ack message to the MSC. The end-to-end two way path is now (Step <b>27</b>) in place and bi-directional voice traffic flows between the UE and MSC through the FAP and the INC. A FAP with local service can support MO using the FAP IMSI. The necessary message flows would be similar as above without the FAP-UE message exchanges over the air interface.

03642. Mobile Terminated Call

0365<figref idref="DRAWINGS">FIG. 31</figref> illustrates a mobile terminated call. The scenario shown is for a PSTN-to-mobile call. As shown, the MSC (i.e., the GMSC function) receives (in Step <b>1</b>) a call from party A intended for the Femtocell subscriber <b>3105</b>. The MSC <b>3120</b> sends (in Step <b>2</b>) a RANAP Paging message to the INC <b>3115</b> identified through the last Location Update received by it and includes the TMSI if available. The IMSI of the mobile being paged is always included in the request.

0366The INC <b>3115</b> identifies the UE registration context using the IMSI provided by the MSC. It then pages (in Step <b>3</b>) the associated FAP <b>3110</b> using the GA-CSR PAGING REQUEST message. The message includes the TMSI, if available in the request from the MSC, else it includes only the IMSI of the mobile.

0367The FAP <b>3110</b> relays (in Step <b>4</b>) the Paging request to the UE. The FAP may use Paging Type 1 or 2 based on the RRC state of the UE as described in “Radio Resource Control (RRC) protocol specification”, 3GPP TS 25.331, hereinafter “TS 25.331”. The UE <b>3105</b> establishes (in Step <b>4</b><i>a</i>) a RRC connection with the FAP <b>3110</b> if one doesn't exist. This step is omitted if there is an already existing RRC connection (e.g. an RRC connection may have been established for PS domain).

0368Next, the UE <b>3105</b> processes the paging request and sends (in Step <b>5</b>) the Paging response to the FAP <b>3110</b>. The FAP then performs (in Step <b>5</b><i>a</i>) the GA-CSR Connection Establishment procedure with the INC as described in previous sections. The FAP responds (in Step <b>6</b>) with a GA-CSR PAGING RESPONSE.

0369The INC <b>3115</b> establishes an SCCP connection to the MSC <b>3120</b>. The INC <b>3115</b> then forwards (in Step <b>7</b>) the paging response to the MSC using the RANAP Initial UE Message. Subsequent NAS messages between the UE and core network will be sent using the RANAP Direct Transfer message. The MSC then authenticates (in Step <b>8</b>) the UE using standard UTRAN authentication procedures. The MSC also initiates (in Step <b>8</b>) the Security Mode Control procedure described in previous sections.

0370The MSC initiates (in Step <b>9</b>) call setup using the Setup message sent to the FAP via INC. The INC then forwards (in Step <b>10</b>) this message to the FAP in the GA-CSR DL DIRECT TRANSFER message. The FAP relays (Step <b>11</b>) the Setup message to the UE

0371The UE <b>3105</b> responds (in Step <b>12</b>) with Call Confirmed after checking it's compatibility with the bearer service requested in the Setup and modifying the bearer service as needed. If the Setup included the signal information element, the UE alerts the user using the indicated signal, else the UE alerts the user after the successful configuration of the user plane

0372The FAP relays (in Step <b>13</b>) the Call Confirmed to the INC using the GA-CSR UL DIRECT TRANSFER message. The INC then forwards (in Step <b>14</b>) the Call Confirmed message to the MSC using RANAP direct transfer message. At this point (Step <b>15</b>) an end to end bearer path is established between the MSC <b>3120</b> and UE <b>3105</b> using the procedure for voice bearer establishment as described in previous sections.

0373The UE signals (in Step <b>16</b>) that it is alerting the user, via the Alerting message to the FAP. The FAP relays (in Step <b>17</b>) the Alerting message to the INC using the GA-CSR UL DIRECT TRANSFER. The INC (in Step <b>18</b>) forwards the Alerting message to the MSC.

0374The MSC <b>3120</b> returns (in Step <b>19</b>) a ISUP ACM message towards the originating PSTN Exchange <b>3125</b>. The UE signals (in Step <b>20</b>) that the called party has answered, via the Connect message. The FAP relays (in Step <b>21</b>) the Connect message to the INC in the GA-CSR UL DIRECT TRANSFER message.

0375Next, the INC forwards (in Step <b>22</b>) the Connect message to the MSC. The MSC then returns (in Step <b>23</b>) an ISUP ANM message towards the originating PSTN exchange <b>3125</b>. The MSC acknowledges (in Step <b>24</b>) via the Connect Ack message to the INC. The INC forwards (in Step <b>25</b>) this message to the FAP in the GA-CSR DL DIRECT TRANSFER.

0376The FAP relays (in Step <b>26</b>) the Connect Ack to the UE. The two parties on the call are connected on the audio path. The end-to-end two way path is now (Step <b>27</b>) in place and bi-directional voice traffic flows between the UE and MSC through the FAP and the INC. A FAP with local service can support MT using the FAP IMSI. The necessary message flows would be similar as above without the FAP-UE message exchanges over the air interface.

03773. Call Release by Femtocell Subscriber

0378<figref idref="DRAWINGS">FIG. 32</figref> illustrates a scenario where a Femtocell call is released by the Femtocell subscriber in some embodiments. As shown, the Femtocell subscriber <b>3205</b> requests (in Step <b>1</b>) call release (e.g., by pressing the END button). Upon request from the upper layers, the UE sends (in Step <b>2</b>) the Disconnect message to the FAP <b>3210</b>. The FAP forwards (in Step <b>3</b>) the Disconnect message to the INC (embedded in a GA-CSR UL DIRECT TRANSFER message).

0379The INC <b>3220</b> relays (in Step <b>4</b>) the Disconnect message to the MSC <b>3225</b> via RANAP Direct Transfer message. The MSC <b>3225</b> sends (in Step <b>5</b>) an ISUP RELEASE message towards the other party <b>3230</b>. The MSC sends (in Step <b>6</b>) a Release to the INC using RANAP Direct Transfer message.

0380Next, the INC forwards (in Step <b>7</b>) the Release message to FAP using GA-CSR DL DIRECT TRANSFER message. The FAP then sends (in Step <b>8</b>) the Release message to the UE over the air interface. The UE <b>3205</b> confirms (in Step <b>9</b>) the Release via the Release Complete message to the FAP. The FAP relays (in Step <b>10</b>) the Release Complete message to the INC using GA-CSR UL DIRECT TRANSFER message

0381The INC forwards (in Step <b>11</b>) the message to the MSC using RANAP Direct Transfer message. At this point, the MSC considers the connection released. Sometime after Step <b>5</b>, the MSC receives (in Step <b>12</b>) an ISUP RLC message from the other party's exchange.

0382The MSC <b>3225</b> sends (in Step <b>13</b>) an Iu Release command to the INC <b>3220</b> indicating a request to release the call resources. The SCCP Connection Identifier is used to determine the corresponding call. The INC <b>3220</b> requests (in Step <b>14</b>) the GANC MGW <b>3215</b> to release associated resources with the call. The GANC MGW <b>3215</b> confirms (in Step <b>15</b>) release of associated resources.

0383The INC initiates (in Step <b>16</b>) a GA-CSR Connection Release procedure towards the FAP (as described in previous sections). The FAP in turn releases (in Step <b>17</b>) any radio resource associated for the specific call. If there is an active PS session for the UE, the RRC connection may not be released by the FAP, and only the corresponding CS radio bearers are released. Finally, the INC acknowledges (in Step <b>18</b>) the resource release to the MSC using the Iu Release Complete message to the MSC. The SCCP connection associated with the call between the INC and the MSC is released as well

03844. Other Calling Scenarios

0385The following services are supported by the Femtocell solution: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0386"> Calling Line Identification Presentation (CLIP) </li><li id="ul0002-0002" num="0387"> Calling Line Identification Restriction (CLIR) </li><li id="ul0002-0003" num="0388"> Connected Line Identification Presentation (CoLP) </li><li id="ul0002-0004" num="0389"> Connected Line Identification Restriction (CoLR) </li><li id="ul0002-0005" num="0390"> Call Forwarding Unconditional </li><li id="ul0002-0006" num="0391"> Call Forwarding Busy </li><li id="ul0002-0007" num="0392"> Call Forwarding No Reply </li><li id="ul0002-0008" num="0393"> Call Forwarding Not Reachable </li><li id="ul0002-0009" num="0394"> Call Waiting (CW) </li><li id="ul0002-0010" num="0395"> Call Hold (CH) </li><li id="ul0002-0011" num="0396"> Multi Party (MPTY) </li><li id="ul0002-0012" num="0397"> Closed User Group (CUG) </li><li id="ul0002-0013" num="0398"> Advice of Charge (AoC) </li><li id="ul0002-0014" num="0399"> User User Signaling (UUS) </li><li id="ul0002-0015" num="0400"> Call Barring (CB) </li><li id="ul0002-0016" num="0401"> Explicit Call Transfer (ECT) </li><li id="ul0002-0017" num="0402"> Name Identification </li><li id="ul0002-0018" num="0403"> Completion of Calls to Busy Subscriber (CCBS) </li></ul></li></ul>

0404These supplementary services involve procedures that operate end-to-end between the UE and the MSC. Beyond the basic Direct Transfer Application Part (DTAP) messages already described for MO and MT calls, the following DTAP messages are used for these additional supplementary service purposes: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0405"> HOLD </li><li id="ul0004-0002" num="0406"> HOLD-ACKNOWLEDGE </li><li id="ul0004-0003" num="0407"> HOLD-REJECT </li><li id="ul0004-0004" num="0408"> RETRIEVE </li><li id="ul0004-0005" num="0409"> RETRIEVE-ACKNOWLEDGE </li><li id="ul0004-0006" num="0410"> RETRIEVE-REJECT </li><li id="ul0004-0007" num="0411"> FACILITY </li><li id="ul0004-0008" num="0412"> USER-INFORMATION </li><li id="ul0004-0009" num="0413"> CONGESTION-CONTROL </li><li id="ul0004-0010" num="0414"> CM-SERVICE-PROMPT </li><li id="ul0004-0011" num="0415"> START-CC </li><li id="ul0004-0012" num="0416"> CC-ESTABLISHMENT </li><li id="ul0004-0013" num="0417"> CC-ESTABLISHMENT-CONFIRMED </li><li id="ul0004-0014" num="0418"> RECALL </li></ul></li></ul>

0419These DTAP message are relayed between the UE and MSC by the INC in the same manner as in the other call control and mobility management scenarios described in this disclosure. A generic example is illustrated in <figref idref="DRAWINGS">FIG. 33</figref>. As shown (in Step <b>1</b>), there is an existing MM connection established between the UE and the MSC for an ongoing call. The user requests (in Step <b>2</b>) a particular supplementary service operation (e.g., to put the call on hold).

0420The UE <b>3305</b> sends (in Step <b>3</b><i>a</i>) the HOLD message to the FAP <b>3310</b> over the air. The FAP in turn forwards (in Step <b>3</b><i>b</i>) the message to INC <b>3315</b>), embedded in a GA-CSR UPLINK DIRECT TRANSFER message. The INC relays (in Step <b>3</b><i>c</i>) the DTAP HOLD message to the MSC <b>3320</b> over the Iu-interface.

0421Next, the DTAP HOLD-ACK message is sent (in Steps <b>4</b><i>a</i>-<b>4</b><i>c</i>) from MSC <b>3320</b> to UE <b>3305</b> through the INC and FAP. Later in the call, the user requests (in Step <b>5</b>) another supplementary service operation (e.g., to initiate a MultiParty call).

0422The UE sends (in Step <b>6</b><i>a</i>) the FACILITY message to the FAP over the air. The FAP in turn forwards (in Step <b>6</b><i>b</i>) the message to the INC. The INC relays (in Step <b>6</b><i>c</i>) the DTAP FACILITY message to the MSC over the Iu-interface. Finally, the DTAP FACILITY message including the response is sent (in Steps <b>7</b><i>a</i>-<b>7</b><i>c</i>) from MSC to UE through the INC and FAP.

VII. PACKET SERVICES

0423A. GA-PSR Transport Channel Management Procedures

0424The GA-PSR Transport Channel (GA-PSR TC) provides an association between the FAP and INC for the transport of the user data over the Up interface. Given that the Femtocell user data transport is UDP based, the GA-PSR Transport Channel is associated with corresponding FAP and INC IP addresses and UDP ports used for user data transfer. The FAP and INC manage the GA-PSR Transport Channel based on the requests for data transfer and the configurable GA-PSR TC Timer.

04251. States of the GA-PSR Sub-Layer

0426The GA-PSR Transport Channel (GA-PSR TC) management procedures are the basic procedures for PS services specified to facilitate the control of the GA-PSR connection for user data transfer. Given that the GTP-U user data transport is extended to the FAP in GAN solution for Femtocell support, these procedures are tightly integrated with RAB Assignment procedures for user data. GTP-U based connection between the FAP and the SGSN for user data transfer is referred to as the GA-PSR Transport Channel.

0427The GA-PSR Transport Channel consists of the following: (1) The IP address and destination UDP port number to be used for user data transfer at both the SGSN and FAP, and (2) The GA-PSR TC Timer. The FAP or INC will activate a GA-PSR Transport Channel only when needed; i.e., when the user data transfer is initiated.

0428The GA-PSR maintains a separate PS entity for each PDP context that is established. Each individual GA-PSR PS entity can be in two different states, GA-PSR-PS-STANDBY or GA-PSR-PS-ACTIVE state. The state of the GA-PSR PS entity and the corresponding transport channel are always synchronized.

0429In GA-PSR-PS-STANDBY state the FAP is not able to send or receive user data associated with the specific PDP context to and from the SGSN. The INC or the FAP needs to activate the GA-PSR Transport Channel before sending any user data for that PDP context. In this state a corresponding GA-PSR Transport Channel does not exist. When the GA-PSR Transport Channel is activated, the GA-PSR entity associated with that PDP context enters the GA-PSR-PS-ACTIVE state.

0430In GA-PSR-PS-ACTIVE state the FAP and UE are able to send and receive user data associated with the specific PDP context to and from the SGSN. Furthermore there exists a corresponding GA-PSR Transport Channel for this FAP/UE.

0431A GA-PSR TC Timer is also defined to control the transition from GA-PSR-PS-ACTIVE to GA-PSR-PS-STANDBY state as follows. The FAP GA-PSR layer implements a timer associated with each GA-PSR Transport Channel. The timer is started when that entity enters GA-PSR-PS-ACTIVE state and restarted each time a data packet for that PDP context is transmitted to or received from the network. When the timer expires, the FAP deactivates the GA-PSR Transport Channel and the corresponding PDP service entity enters GA-PSR-PS-STANDBY state.

0432The GA-PSR TC Timer value is provided to the FAP as part of the Femtocell Registration procedure (i.e., in GA-RC REGISTER ACCEPT message).

04332. FAP Initiated GA-PSR Transport Channel Activation

0434<figref idref="DRAWINGS">FIG. 34</figref> depicts the FAP initiated GA-PSR Transport Channel activation procedure of some embodiments. Initially, the corresponding GA-PSR PS PDP entity is in GA-PSR-PS-IDLE state when the uplink data transfer for that PDP context is requested. The FAP has to establish the GA-PSR Transport channel prior to resuming the uplink data transfer.

0435As shown, if the RRC connection does not exist, the UE <b>3405</b> initiates (in Step <b>1</b>) RRC Connection establishment procedure as per standard 3GPP procedure. Upon successful RRC Connection establishment, the UE <b>3405</b> forwards (in Step <b>2</b>) a Service Request message to the SGSN via the FAP <b>3410</b> indicating data transfer. The FAP performs (in Step <b>2</b><i>a</i>) the GA-PSR Connection Establishment procedure with the INC as described in “FAP initiated GA-PSR connection establishment” Subsection under “Resource Management” Section, above.

0436The FAP <b>3410</b> then encapsulates the request within the GA-PSR-UPLINK-DIRECT-TRANSFER message and forwards (in Step <b>3</b>) the request to the INC <b>3415</b>. The INC forwards (in Step <b>4</b>) the Service Request to the CN (SGSN) <b>3420</b> encapsulated within the Initial Iu Message or within the Direct Transfer message depending on PMM state. Optionally, the CN (SGSN) may initiate (in Step <b>5</b>) security function as specified in “Security Mode Control” Subsection and “Core network authentication” Subsections under “Femtocell Security” Section, further below. Optionally, upon receiving the request and if the UE was in PMM-CONNECTED state, the CN (SGSN) responds (in Step <b>6</b>) with a Service Accept message.

0437Optionally, if the Service Accept message was received, the INC <b>3415</b> forwards (in Step <b>7</b>) the message to the FAP <b>3410</b>. The FAP then forwards (in Step <b>8</b>) the message to the UE <b>3405</b>. The CN (SGSN) <b>3420</b> initiates (in Step <b>9</b>) RAB Assignment procedure and includes the RAB-ID, the CN Transport Layer Address (IP address) and the CN Iu Transport Association (GTP-U Terminal Endpoint Identifier (TEID)) for user data to be used with this GA-PSR Transport Channel.

0438Next, the INC forwards (in Step <b>10</b>) the GA-PSR ACTIVATE TC REQ to the FAP to activate the Transport Channel for user data transfer. The message includes the RAB-ID, and the INC IP Address and INC TEID. To allow the FAP to send GA-PSR TC packets (i.e., GTP-U messages) directly to the SGSN, the INC sets the INC IP Address to the CN IP Address and the INC TEID to the CN TEID. In an alternate embodiment, it is possible for the GANC to assume the role of a GTP-U proxy gateway, where two separate GTP-U tunnels exist for a given GA-PSR TC i.e. first GTP-U between FAP and GANC and the corresponding GTP-U between the GANC and the SGSN. The GANC is responsible for relaying the actual PS data packets between the two GTP-U tunnels. Next, corresponding Radio Bearers are established (in Step <b>11</b>) between the FAP <b>3410</b> and UE <b>3405</b>.

0439The FAP then responds (in Step <b>12</b>) to the INC with acknowledgment. The message includes the RAB-ID and a GTP-U TEID assigned by the FAP for the specific PS session. Upon receiving the acknowledgment, the INC sends (in Step <b>13</b>) the RAB Assignment Rsp message to the CN (SGSN) to complete the RAB Assignment procedure. To allow the SGSN to send GTP-U messages directly to the FAP, the INC sets the RAN IP Address to the FAP's IP Address and the RAN TEID to the TEID allocated by the FAP for the UE specific PS session.

0440The INC notifies (in Step <b>14</b>) the FAP that the procedure is complete and the FAP modifies the state of the corresponding GA-PSR PS PDP entity to GA-PSR-PS ACTIVE and starts GA-PSR PS TC Timer. The UE initiates (in Step <b>15</b>) uplink user data transfer via the established transport channel and the SGSN may use the same transport channel to send downlink user data packets. While the transport channel is active, both FAP and SGSN can continue sending user data associated with the same PDP context directly using this transport channel.

04413. FAP Initiated Deactivation of the GA-PSR Transport Channel

0442<figref idref="DRAWINGS">FIG. 35</figref> illustrates the scenario in some embodiments when the FAP deactivates the GA-PSR Transport Channel after the GA-PSR TC Timer expires. As shown, GA-PSR TC Timer associated with one of the active GA-PSR Transport Channels expires (in Step <b>1</b>). The FAP <b>3510</b> sends (in Step <b>2</b>) GA-PSR DEACTIVATE TC REQ message to the INC <b>3515</b> including the RAB-ID to identify the GA-PSR Transport Channel and indicating the normal release as a cause for deactivation.

0443The INC <b>3515</b> forwards (in Step <b>3</b>) RAB Release Req message to the CN (SGSN) <b>3520</b> to request the release of the associated RAB. The CN (SGSN) responds (in Step <b>4</b>) with the RAB Assignment Request indicating release for the requested RAB.

0444Next, the INC <b>3515</b> responds (in Step <b>5</b>) to the FAP with a GA-PSR DEACTIVATE TC ACK message to acknowledge successful deactivation. Upon receiving acknowledgment message, the FAP initiates (in Step <b>6</b>) release of the associated Radio Bearers. Finally, the INC sends (in Step <b>7</b>) RAB Assignment Rsp message to notify the SGSN that the RAB Release procedure is complete.

04454. Network Initiated Transport Channel Activation for PS Service

0446<figref idref="DRAWINGS">FIG. 36</figref> depicts a scenario when the CN (SGSN) initiates activation of a PS Transport Channel for user data service. This scenario covers the case when the SGSN receives a downlink user data packet from the GGSN and the RAB for that PDP context is not established. Initially, the CN (SGSN) received downlink user data to transfer to the UE and the associated RAB is not established. The UE is in PMM-IDLE state. The UE <b>3605</b> is in PMM-IDLE state and the CN (SGSN) <b>3610</b> sends (in Step <b>1</b>) the RANAP Paging request to the UE <b>3605</b> via the INC <b>3615</b> to locate the user. The paging request indicates paging for PS Domain. The INC <b>3615</b> forwards (in Step <b>2</b>) the GA-PSR PAGING message to the FAP <b>3610</b>.

0447Next, the FAP forwards (in Step <b>3</b>) the PS Page to the UE <b>3605</b> as per standard 3GPP procedure. The FAP may use Paging Type 1 or 2 based on the RRC state of the UE as described in TS 25.331. Next, an RRC connection is established (in Step <b>4</b>) between the UE <b>3605</b> and FAP <b>3610</b>. This step is omitted if there is an already existing RRC connection (e.g. a RRC connection may have been established for CS domain)

0448Next, the UE responds (in Step <b>5</b>) to the SGSN via the FAP with a Service request indicating PS paging response. The message is encapsulated within the RRC INITIAL DIRECT TRANSFER message. The FAP performs (in Step <b>5</b><i>a</i>) the GA-PSR Connection Establishment procedure with the INC as described in Subsection “FAP initiated GA-PSR connection establishment” under “RESOURCE MANAGEMENT” Section, above. The FAP forwards (in Step <b>6</b>) the PS paging response to the INC using GA-PSR PAGING RESPONSE message.

0449The INC forwards (in Step <b>7</b>) the Service Request message to the SGSN encapsulated in the RANAP Initial UE Message. Security function is performed (in Step <b>8</b>) as specified in “Security mode control” Subsection and “Core network authentication” under “FEMTOCELL SECURITY” Section, below. Steps <b>9</b> to <b>15</b> are same as described in the “FAP initiated GA-PSR transport channel activation” Subsection, above.

04505. Network Initiated Transport Channel Deactivation

0451<figref idref="DRAWINGS">FIG. 37</figref> depicts a network initiated GA-PSR Transport Channel deactivation procedure that includes Radio Access Barer release in some embodiments. Initially, active GA-PSR Transport Channel associated with the UE <b>3705</b> that is registered for Femtocell service is active.

0452As shown, optionally, the INC <b>3715</b> may initiate (in Step <b>1</b>) RAB Release procedure as a result of error handling procedure. This would trigger CN (SGSN) <b>3720</b> to release the corresponding RAB. The CN (SGSN) <b>3720</b> sends (in Step <b>2</b>) a RAB Assignment Request to request the release of the associated RAB. The release request may include one or more RABs.

0453The INC <b>3715</b> requests (in Step <b>3</b>) deactivation of the associated GA-PSR Transport Channel. As a result, the corresponding Radio Bearers are (in Step <b>4</b>) released. The FAP <b>3710</b> then updates (in Step <b>5</b>) the state of the corresponding GA-PSR PS PDP entity to STANDBY, stops GA-PSR TC Timer and sends the acknowledgment back to the INC. Steps <b>3</b>, <b>4</b> and <b>5</b> are repeated for each additional RAB that needs to be released. Finally, the INC <b>3715</b> notifies (in Step <b>6</b>) the CN (SGSN) <b>3720</b> that the release was successful.

0454B. User Data and Signaling Transport

04551. User Data Transport Procedures

0456<figref idref="DRAWINGS">FIG. 38</figref> illustrates the transport of user data packets via Femtocell in some embodiments. As shown, if the corresponding GA-PSR Transport Channel is not active, the GA-PSR TC activation procedure is initiated (in Step <b>1</b>) as specified in the “FAP initiated GA-PSR transport channel activation” Subsection, above. Upon the GA-PSR Transport Channel establishment, the FAP <b>3810</b> starts (in Step <b>2</b>) GA-PSR TC Timer.

0457The UE <b>3805</b> initiates (in Step <b>3</b>) the transfer of an uplink user data packet using PDCP Data service. The FAP <b>3810</b> forwards (in Step <b>4</b>) the packet using the standard GTP-U protocol as specified in “GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface”, 3GPP TS 29.060, and restarts (in Step <b>5</b>) GA-PSR TC Timer.

0458The CN (SGSN) <b>3820</b> transfers (in Step <b>6</b>) downlink user data packet utilizing the same GA-PSR Transport Channel associated with the specific PDP context. Downlink user data packets are transferred using the standard GTP-U protocol as specified in 3GPP TS 29.060. Upon receiving the downlink data packet, the FAP restarts (in Step <b>7</b>) GA-PSR TC Timer associated with the corresponding GA-PSR Transport Channel and forwards (in Step <b>8</b>) the packet to the UE via the PDCP.

0459Additional uplink and downlink user data packets are transferred (in Step <b>9</b>) via the same GA-PSR Transport Channel as described in steps <b>2</b> and <b>3</b> respectively. After the GA-PSR TC Timer expires (Step <b>10</b>), the FAP initiates (in Step <b>11</b>) GA-PSR Transport Channel deactivation procedure as described in the “FAP initiated deactivation of the GA-PSR transport channel” Subsection, above. A FAP with local service can support PS user plane activity using the FAP IMSI. The necessary message flows would be similar as above without the FAP-UE message exchanges over the air interface.

04602. GA-PSR Signaling Procedures

0461A single TCP connection per UE is established for the transport of signaling messages within the Femtocell. This TCP connection is used to transport all CS and PS related signaling and SMS messages.

0462a) UE Initiated PS Signaling Procedure

0463For UE initiated PS related signaling, the UE sends a PS signaling message to the CN, via the INC which forwards it to the CN over the Iu-ps interface as per standard UMTS; e.g. the signaling message may include GMM attach or SM PDP context activation message. The INC encapsulates the received signaling message within a RANAP Direct Transfer message that is forwarded to the SGSN over the Iu-ps interface. <figref idref="DRAWINGS">FIG. 39</figref> illustrates Uplink Control Plane Data Transport of some embodiments.

0464Initially, the UE <b>3905</b> is ready to send an uplink signaling message for PS services to the CN (SGSN) <b>3920</b>. This could be any of the GMM or SM signaling messages. As shown, if the RRC connection does not exist, the UE <b>3905</b> initiates (in Step <b>1</b>) RRC Connection establishment procedure as per standard 3GPP procedure.

0465Upon successful RRC Connection establishment, the UE forwards (in Step <b>2</b>) a Service Request message to the SGSN via the FAP <b>3910</b> indicating PS Signaling message. The FAP performs (in Step <b>2</b><i>a</i>) the GA-PSR Connection Establishment procedure with the INC as described in the “FAP initiated GA-PSR connection establishment” Subsection under the “RESOURCE MANAGEMENT” Section, above. The FAP encapsulates the Service Request within the GA-PSR-UPLINK-DIRECT-TRANSFER message and forwards (in Step <b>3</b>) the request to the INC <b>3910</b>.

0466Next, the INC forwards (in Step <b>4</b>) the Service Request to the SGSN encapsulated within the Initial Iu Message or within the Direct Transfer message depending on PMM state. Optionally, the CN (SGSN) may initiate (in Step <b>5</b>) security function as specified in Sections “Security Mode Control” and “Core Network Authentication”, below. The UE <b>3805</b> sends (in Step <b>6</b>) the PS signaling message to the FAP <b>3910</b> using RRC Uplink Direct Transfer service.

0467The FAP <b>3910</b> forwards (in Step <b>7</b>) the PS signaling message to the INC encapsulated within the GA-PSR-UPLINK-DIRECT-TRANSFER message. Finally, the INC <b>3915</b> forwards (in Step <b>8</b>) the PS signaling message to the CN (SGSN) <b>3920</b> using RANAP Direct Transfer procedure.

0468b) Network initiated PS Signaling Procedure

0469For Network initiated PS related signaling, the Core Network sends a PS signaling message to the INC via the IuPS interface as per standard UMTS; e.g. the signaling message may include GMM attach accept or SM PDP context activation accept message. The INC encapsulates the received signaling message within a GA-PSR-DOWNLINK-DIRECT-TRANSFER OR GA-PSR PAGING message that is forwarded to the FAP via the existing TCP signaling connection. <figref idref="DRAWINGS">FIG. 40</figref> illustrates Downlink Control Plane Data Transport of some embodiments. Initially, the CN (SGSN) <b>4020</b> is ready to send a downlink signaling message for PS services to the UE <b>4005</b>. This could be any of the GMM or SM signaling messages. Given that the signaling procedure is network initiated and if the UE is in PMM-IDLE state, the SGSN will first page the UE. If the UE is in PMM-CONNECTED state the SGSN will send the downlink PS signaling message using RANAP Direct Transfer procedure starting with Step <b>9</b>.

0470As shown, optionally, if the UE <b>4005</b> is in PMM-IDLE state, the CN (SGSN) <b>4020</b> sends (in Step <b>1</b>) the RANAP Paging request to the UE via the INC <b>4015</b> to locate the user. The paging request indicates paging for PS Domain. Optionally, if the paging request was received, the INC forwards (in Step <b>2</b>) the paging request using the GA-PSR PAGING message to the FAP <b>4010</b>.

0471Also, optionally, if the paging message is received, the FAP forwards (in Step <b>3</b>) the PS page to the UE as per standard 3GPP procedure. Optionally, if the RRC connection does not exist for that UE, it is established (in Step <b>4</b>) as per standard 3GPP procedure. Optionally, if the page for PS services was received, the UE responds (in Step <b>5</b>) to the SGSN via the FAP with a Service Request message indicating PS paging response. The Service Request message is encapsulated within the RRC INITIAL DIRECT TRANSFER message.

0472The FAP <b>4010</b> performs (in Step <b>5</b><i>a</i>) the GA-PSR Connection Establishment procedure with the INC as described in the “FAP initiated GA-PSR connection establishment” Subsection under the “RESOURCE MANAGEMENT” Section, above. The FAP forwards (in Step <b>6</b>) the response encapsulated within the GA-PSR PAGING RESPONSE message to the INC.

0473Next, the INC <b>4015</b> forwards (in Step <b>7</b>) the Service Request message to the SGSN <b>4020</b> encapsulated in the RANAP Initial UE Message. Optionally, the CN (SGSN) initiates (in Step <b>8</b>) Security Function.

0474The CN (SGSN) forwards (in Step <b>9</b>) the PS signaling message to the INC using RANAP Direct Transfer procedure. The INC forwards (in Step <b>10</b>) the PS signaling message to the FAP encapsulated within the GA-PSR-DOWNLINK-DIRECT-TRANSFER message. Finally, the FAP sends (in Step <b>11</b>) the signaling message to the UE using RRC Downlink Direct Transfer service. A FAP with local service can support PS signaling plane activity using the FAP IMSI. The necessary message flows would be similar as above without the FAP-UE message exchanges over the air interface.

VIII. ERROR HANDLING PROCEDURES

0475In some embodiments, the checks described in this section are applied to all messages exchanged in the Femtocell system. This section also specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called “error handling procedures”, but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. In some embodiments, Sub-sections A to F, below, are applied in order of precedence.

0476In this section the following terminology is used (1) An information element (IE) is defined to be syntactically incorrect in a message if it includes at least one value defined as “reserved” in the corresponding message, or if its value part violates rules of any corresponding messages. However it is not a syntactical error that an IE specifies in its length indicator a greater length than defined in for the specific message, and (2) A message is defined to have semantically incorrect contents if it includes information which, possibly dependent on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part of this specification. The procedures described in this sub-section apply to both GA-CSR and GA-PSR messages, unless explicitly specified otherwise.

0477A. Message Too Short

0478When a message is received that is too short to include a complete message header and all the mandatory information elements, that message is ignored.

0479B. Invalid Message Header

0480When the FAP receives a message over UDP with message type not defined or not implemented, the FAP ignores the message. When the FAP receives a message over TCP with protocol discriminator not defined or not implemented, the FAP ignores the message. When the FAP receives a message with Skip Indicator IE not encoded as 0000 or Length IE greater than 2048, the FAP ignores the message.

0481When the FAP receives a message over TCP with message type not defined for the specific PD (GA-CSR or GA-PSR) or not implemented, the FAP returns a GA-CSR STATUS or GA-PSR STATUS respectively, with cause “message type non-existent or not implemented”. When the FAP receives a message not compatible with the protocol state, the FAP ignores the message and shall return a (GA-CSR or GA-PSR) STATUS message with cause “Message type not compatible with protocol state”.

0482C. Invalid Information Elements

0483When the FAP receives a GA-RC OR GA-CSR OR GA-PSR message with a missing or syntactically incorrect mandatory IE, the FAP ignores the message and returns a (GA-RC or GA-PSR) STATUS message with cause “Invalid mandatory information”. The FAP also ignores all unknown IEs in received messages. The FAP further treats all optional IEs that are syntactically incorrect in a message as not present in the message.

0484When the FAP diagnoses a missing or unexpected conditional IE or when it receives at least one syntactically incorrect conditional IE, the FAP ignores the message and returns a (GA-RC or GA-PSR) STATUS message with cause value “conditional IE error”. When the FAP receives a message with semantically incorrect contents, the FAP ignores the message and returns a (GA-RC or GA-PSR) STATUS message with cause value “semantically incorrect message”.

0485D. Handling of Lower Layer Faults

0486The handling of lower layer failures in the FAP while in the GA-RC-DEREGISTERED state is as follows. If a TCP connection was established towards the Provisioning GANC, the FAP releases the connection. If a secure connection was established towards SeGW of the Provisioning GANC, the FAP releases the secure connection (as defined in “Internet Key Exchange (IKEv2) Protocol”, IETF RFC <b>4306</b>. additionally, when the lower layer failures happen during a Discovery procedure, the FAP doubles the current timer value for TU<b>3903</b> but not exceeding the maximum value (32 minutes). The FAP also starts timer TU<b>3903</b>.

0487When the lower layer failures happen during a Registration procedure, and if the registration is still unsuccessful after a number of attempts defined the FAP parameter “Up Connect Attempt Count” (maximum value of 3), and if the FAP had attempted the registration towards the Default GANC, then the FAP deletes the stored information about the Default GANC, increments Redirection Counter, and initiates the Discovery Procedure. When the lower layer failures happen during a Registration procedure, the registration is still unsuccessful after a number of attempts defined the FAP parameter “Up Connect Attempt Count” (maximum value of 3), and the FAP had attempted the registration towards a Serving GANC, then the FAP increments Redirection Counter and initiates Registration Procedure towards the Default GANC.

0488When the lower layer failures happen during a Registration procedure and the registration is successful before a number of attempts defined the FAP parameter “Up Connect Attempt Count” (maximum value of 3), then the FAP starts timer TU<b>3905</b> and waits for it to expire.

0489The handling of lower layer failures in the FAP while not in the GA-RC-DEREGISTERED state is as follows. For all lower layer failures in the FAP (for example related to DNS, IPSec or TCP failures other than RST) except the TCP connection failure which is handled as described in the “FAP initiated FAP Synchronization after TCP connection reestablishment” sub-section described above, the FAP (1) releases the TCP connection towards the current GANC, if established, (2) releases the secure connection towards SeGW of the current GANC, if established, (3) starts timer TU<b>3905</b> (for FAP TCP connection) or TU<b>3955</b> (for UE specific TCP connection), and (4) enters GA-RC-DEREGISTERED state.

0490E. Out of Sequence IEs

0491The FAP ignores all out of sequence IEs in a message. In some embodiments, the GANC also takes the same approach and ignores all out of sequence IEs in a message.

0492F. Unexpected Messages

0493The FAP silently discards all unexpected messages (unless specific behavior is defined for certain messages) which are either inconsistent with the current state of the device or out of sequence. The network should take the same approach.

IX. MESSAGE AND INFORMATION ELEMENTS USED

0494This section provides a list of messages and Information elements (IEs) used in some embodiments. IEs are similar to “attributes” or “parameters” and are used in messages to exchange information across interfaces.

0495Table IX-1 summarizes the messages for Generic Resources management. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE IX-1</entry></row><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Messages for Unlicensed Radio Resources management</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="35PT" align="left" /><colspec colname="1" colwidth="182PT" align="left" /><tbody valign="top"><row><entry /><entry>Discovery messages:</entry></row><row><entry /><entry>GA-RC DISCOVERY REQUEST</entry></row><row><entry /><entry>GA-RC DISCOVERY ACCEPT</entry></row><row><entry /><entry>GA-RC DISCOVERY REJECT</entry></row><row><entry /><entry>Registration messages:</entry></row><row><entry /><entry>GA-RC REGISTER REQUEST</entry></row><row><entry /><entry>GA-RC REGISTER ACCEPT</entry></row><row><entry /><entry>GA-RC REGISTER REDIRECT</entry></row><row><entry /><entry>GA-RC REGISTER REJECT</entry></row><row><entry /><entry>GA-RC DEREGISTER</entry></row><row><entry /><entry>GA-RC REGISTER UPDATE UPLINK</entry></row><row><entry /><entry>GA-RC REGISTER UPDATE DOWNLINK</entry></row><row><entry /><entry>Miscellaneous message:</entry></row><row><entry /><entry>GA-RC KEEP ALIVE</entry></row><row><entry /><entry>GA-RC SYNCHRONIZATION INFORMATION</entry></row><row><entry /><entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0496Table IX-2 summarizes the messages for Generic Access Circuit Switched Resources (GA-CSR) management <tables id="TABLE-US-00002" num="2"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE IX-2</entry></row><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Messages for GA-CSR management</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="35PT" align="left" /><colspec colname="1" colwidth="182PT" align="left" /><tbody valign="top"><row><entry /><entry>GA-CSR connection establishment messages:</entry></row><row><entry /><entry>GA-CSR REQUEST</entry></row><row><entry /><entry>GA-CSR REQUEST ACCEPT</entry></row><row><entry /><entry>GA-CSR REQUEST REJECT</entry></row><row><entry /><entry>Traffic Channel establishment messages:</entry></row><row><entry /><entry>GA-CSR ACTIVATE CHANNEL</entry></row><row><entry /><entry>GA-CSR ACTIVATE CHANNEL ACK</entry></row><row><entry /><entry>GA-CSR ACTIVATE CHANNEL FAILURE</entry></row><row><entry /><entry>GA-CSR ACTIVATE CHANNEL COMPLETE</entry></row><row><entry /><entry>Channel release messages:</entry></row><row><entry /><entry>GA-CSR RELEASE</entry></row><row><entry /><entry>GA-CSR RELEASE COMPLETE</entry></row><row><entry /><entry>GA-CSR CLEAR REQUEST</entry></row><row><entry /><entry>Paging messages:</entry></row><row><entry /><entry>GA-CSR PAGING REQUEST</entry></row><row><entry /><entry>GA-CSR PAGING RESPONSE</entry></row><row><entry /><entry>Security Mode messages:</entry></row><row><entry /><entry>GA-CSR SECURITY MODE COMMAND</entry></row><row><entry /><entry>GA-CSR SECURITY MODE COMPLETE</entry></row><row><entry /><entry>GA-CSR SECURITY MODE REJECT</entry></row><row><entry /><entry>Miscellaneous messages:</entry></row><row><entry /><entry>GA-CSR UPLINK DIRECT TRANSFER</entry></row><row><entry /><entry>GA-CSR DOWNLINK DIRECT TRANSFER</entry></row><row><entry /><entry>GA-CSR STATUS</entry></row><row><entry /><entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0497Table IX-3 summarizes the messages for Generic Access Packet Services Resource (GA-PSR) management. <tables id="TABLE-US-00003" num="3"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE IX-3</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Messages for Generic Access Radio Link Control management</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="140PT" align="left" /><colspec colname="2" colwidth="77PT" align="center" /><tbody valign="top"><row><entry /><entry>Transport Layer</entry></row><row><entry /><entry>used</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>GA-PSR Connection Management messages:</entry><entry /></row><row><entry>GA-PSR-REQUEST</entry><entry>TCP</entry></row><row><entry>GA-PSR REQUESTACCEPT</entry><entry>TCP</entry></row><row><entry>GA-PSR REQUEST REJECT</entry><entry>TCP</entry></row><row><entry>GA-PSR-RELEASE</entry><entry>TCP</entry></row><row><entry>GA-PSR RELEASE COMPLETE</entry><entry>TCP</entry></row><row><entry>GA-PSR TC Management messages:</entry></row><row><entry>GA-PSR-ACTIVATE-TC-REQ</entry><entry>TCP</entry></row><row><entry>GA-PSR-ACTIVATE-TC-ACK</entry><entry>TCP</entry></row><row><entry>GA-PSR-ACTIVATE-TC-CMP</entry><entry>TCP</entry></row><row><entry>GA-PSR-DEACTIVATE-TC-REQ</entry><entry>TCP</entry></row><row><entry>GA-PSR-DEACTIVATE-TC-ACK</entry><entry>TCP</entry></row><row><entry>GPRS Tunneling messages:</entry></row><row><entry>GA-PSR-UPLINK-DIRECT-TRANSFER</entry><entry>TCP</entry></row><row><entry>GA-PSR-DOWNLINK-DIRECT-TRANSFER</entry><entry>TCP</entry></row><row><entry>GAN Specific Signaling messages:</entry></row><row><entry>GA-PSR-PAGING</entry><entry>TCP</entry></row><row><entry>GA-PSR-PAGING RESPONSE</entry><entry>TCP</entry></row><row><entry>GA-PSR-STATUS</entry><entry>TCP</entry></row><row><entry>Security messages:</entry></row><row><entry>GA-PSR SECURITY MODE COMMAND</entry><entry>TCP</entry></row><row><entry>GA-PSR SECURITY MODE COMPLETE</entry><entry>TCP</entry></row><row><entry>GA-PSR SECURITY MODE REJECT</entry><entry>TCP</entry></row><row><entry>GA-PSR CLEAR REQUEST</entry><entry>TCP</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0498<tables id="TABLE-US-00004" num="4"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 9.2.1</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>IE type and identifiers for Unlicensed Radio Resources management</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="112PT" align="left" /><colspec colname="2" colwidth="77PT" align="center" /><tbody valign="top"><row><entry /><entry>IE</entry><entry>Identifier</entry></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="112PT" align="left" /><colspec colname="2" colwidth="77PT" align="char" char="." /><tbody valign="top"><row><entry /><entry>Mobile Identity (FAP)</entry><entry>1</entry></row><row><entry /><entry>GAN Release Indicator</entry><entry>2</entry></row><row><entry /><entry>Access Identity</entry><entry>3</entry></row><row><entry /><entry>GERAN Cell Identity</entry><entry>4</entry></row><row><entry /><entry>Location Area Identification</entry><entry>5</entry></row><row><entry /><entry>GERAN/UTRAN coverage Indicator</entry><entry>6</entry></row><row><entry /><entry>GAN Classmark</entry><entry>7</entry></row><row><entry /><entry>Geographical Location</entry><entry>8</entry></row><row><entry /><entry>GANC-SeGW IP Address</entry><entry>9</entry></row><row><entry /><entry>GANC-SeGW Fully Qualified</entry><entry>10</entry></row><row><entry /><entry>Domain/Host Name</entry></row><row><entry /><entry>Redirection Counter</entry><entry>11</entry></row><row><entry /><entry>Discovery Reject Cause</entry><entry>12</entry></row><row><entry /><entry>GAN Cell Description</entry><entry>13</entry></row><row><entry /><entry>GAN Control Channel</entry><entry>14</entry></row><row><entry /><entry>Description</entry></row><row><entry /><entry>Cell Identifier List</entry><entry>15</entry></row><row><entry /><entry>TU3907 Timer</entry><entry>16</entry></row><row><entry /><entry>GSM RR/UTRAN RRC State</entry><entry>17</entry></row><row><entry /><entry>Routing Area Identification</entry><entry>18</entry></row><row><entry /><entry>GAN Band</entry><entry>19</entry></row><row><entry /><entry>GA-RC/GA-CSR State</entry><entry>20</entry></row><row><entry /><entry>Register Reject Cause</entry><entry>21</entry></row><row><entry /><entry>TU3906 Timer</entry><entry>22</entry></row><row><entry /><entry>TU3910 Timer</entry><entry>23</entry></row><row><entry /><entry>TU3902 Timer</entry><entry>24</entry></row><row><entry /><entry>L3 Message</entry><entry>26</entry></row><row><entry /><entry>Channel Mode</entry><entry>27</entry></row><row><entry /><entry>Mobile Station Classmark 2</entry><entry>28</entry></row><row><entry /><entry>RR Cause</entry><entry>29</entry></row><row><entry /><entry>Cipher Mode Setting</entry><entry>30</entry></row><row><entry /><entry>GPRS Resumption</entry><entry>31</entry></row><row><entry /><entry>Handover From GAN Command</entry><entry>32</entry></row><row><entry /><entry>UL Quality Indication</entry><entry>33</entry></row><row><entry /><entry>TLLI</entry><entry>34</entry></row><row><entry /><entry>Packet Flow Identifier</entry><entry>35</entry></row><row><entry /><entry>Suspension Cause</entry><entry>36</entry></row><row><entry /><entry>TU3920 Timer</entry><entry>37</entry></row><row><entry /><entry>QoS</entry><entry>38</entry></row><row><entry /><entry>GA-PSR Cause</entry><entry>39</entry></row><row><entry /><entry>User Data Rate</entry><entry>40</entry></row><row><entry /><entry>Routing Area Code</entry><entry>41</entry></row><row><entry /><entry>AP Location</entry><entry>42</entry></row><row><entry /><entry>TU4001 Timer</entry><entry>43</entry></row><row><entry /><entry>Location Status</entry><entry>44</entry></row><row><entry /><entry>Cipher Response</entry><entry>45</entry></row><row><entry /><entry>Ciphering Command RAND</entry><entry>46</entry></row><row><entry /><entry>Ciphering Command MAC</entry><entry>47</entry></row><row><entry /><entry>Ciphering Key Sequence Number</entry><entry>48</entry></row><row><entry /><entry>SAPI ID</entry><entry>49</entry></row><row><entry /><entry>Establishment Cause</entry><entry>50</entry></row><row><entry /><entry>Channel Needed</entry><entry>51</entry></row><row><entry /><entry>PDU in Error</entry><entry>52</entry></row><row><entry /><entry>Sample Size</entry><entry>53</entry></row><row><entry /><entry>Payload Type</entry><entry>54</entry></row><row><entry /><entry>Multi-rate Configuration</entry><entry>55</entry></row><row><entry /><entry>Mobile Station Classmark 3</entry><entry>56</entry></row><row><entry /><entry>LLC-PDU</entry><entry>57</entry></row><row><entry /><entry>Location Black List indicator</entry><entry>58</entry></row><row><entry /><entry>Reset Indicator</entry><entry>59</entry></row><row><entry /><entry>TU4003 Timer</entry><entry>60</entry></row><row><entry /><entry>AP Service Name</entry><entry>61</entry></row><row><entry /><entry>GAN Service Zone Information</entry><entry>62</entry></row><row><entry /><entry>RTP Redundancy Configuration</entry><entry>63</entry></row><row><entry /><entry>UTRAN Classmark</entry><entry>64</entry></row><row><entry /><entry>Classmark Enquiry Mask</entry><entry>65</entry></row><row><entry /><entry>UTRAN Cell Identifier List</entry><entry>66</entry></row><row><entry /><entry>Serving GANC table indicator</entry><entry>67</entry></row><row><entry /><entry>Registration indicators</entry><entry>68</entry></row><row><entry /><entry>GAN PLMN List</entry><entry>69</entry></row><row><entry /><entry>Required GAN Services</entry><entry>71</entry></row><row><entry /><entry>Broadcast Container</entry><entry>72</entry></row><row><entry /><entry>3G Cell Identity</entry><entry>73</entry></row><row><entry /><entry>FAP Radio Identity</entry><entry>96</entry></row><row><entry /><entry>GANC IP Address</entry><entry>97</entry></row><row><entry /><entry>GANC Fully Qualified Domain/</entry><entry>98</entry></row><row><entry /><entry>Host Name</entry></row><row><entry /><entry>IP address for GPRS user data</entry><entry>99</entry></row><row><entry /><entry>transport</entry></row><row><entry /><entry>UDP Port for GPRS user data</entry><entry>100</entry></row><row><entry /><entry>transport</entry></row><row><entry /><entry>GANC TCP port</entry><entry>103</entry></row><row><entry /><entry>RTP UDP port</entry><entry>104</entry></row><row><entry /><entry>RTCP UDP port</entry><entry>105</entry></row><row><entry /><entry>GERAN Received Signal Level List</entry><entry>106</entry></row><row><entry /><entry>UTRAN Received Signal Level List</entry><entry>107</entry></row><row><entry /><entry>Integrity Protection Information</entry><entry>75</entry></row><row><entry /><entry>Encryption Information</entry><entry>76</entry></row><row><entry /><entry>Key Status</entry><entry>77</entry></row><row><entry /><entry>Chosen Integrity Algorithm</entry><entry>78</entry></row><row><entry /><entry>Chosen Encryption Algorithm</entry><entry>79</entry></row><row><entry /><entry>Security Mode Reject Cause</entry><entry>80</entry></row><row><entry /><entry>RAB ID</entry><entry>81</entry></row><row><entry /><entry>RAB Parameters</entry><entry>82</entry></row><row><entry /><entry>GTP TEID</entry><entry>83</entry></row><row><entry /><entry>Service Handover</entry><entry>84</entry></row><row><entry /><entry>PDP Type Information</entry><entry>85</entry></row><row><entry /><entry>Data Volume Reporting Indicator</entry><entry>86</entry></row><row><entry /><entry>DL GTP-PDU Sequence Number</entry><entry>86</entry></row><row><entry /><entry>UL GTP-PDU Sequence Number</entry><entry>88</entry></row><row><entry /><entry>DL N-PDU Sequence Number</entry><entry>89</entry></row><row><entry /><entry>UL N-PDU Sequence Number</entry><entry>90</entry></row><row><entry /><entry>Alternate RAB Parameter Values</entry><entry>91</entry></row><row><entry /><entry>Assigned RAB Parameter Values</entry><entry>92</entry></row><row><entry /><entry>Data Volume List</entry><entry>93</entry></row><row><entry /><entry>DRX Cycle Length Coefficient</entry><entry>94</entry></row><row><entry /><entry>Paging Cause</entry><entry>95</entry></row><row><entry /><entry>URA Identity</entry><entry>110</entry></row><row><entry /><entry>GA-PSR State</entry><entry>111</entry></row><row><entry /><entry>Mobile Identity (UE)</entry><entry>112</entry></row><row><entry /><entry>RABS Data Volume Report List</entry><entry>113</entry></row><row><entry /><entry>Allocation/Retention Priority</entry><entry>114</entry></row><row><entry /><entry>Information</entry></row><row><entry /><entry>NAS Synchronization Indicator</entry><entry>115</entry></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

X. SHORT MESSAGE SERVICES

0499The Femtocell system provides support for both circuit mode (CS mode) and packet mode (PS mode) SMS services. CS/PS mode of operation UEs may be able to send and receive short messages using either the MM sub-layer or the GMM sub-layer. PS mode of operation UEs may be able to send and receive short messages using only GMM sub-layer. Inter-working with Femtocell related to SMS services is described in the following sections.

0500A. Circuit Mode (CS Mode) SMS Services

0501The Femtocell protocol architecture related to CS mode SMS support builds on the circuit services signaling architecture described in the “CS domain—control plane architecture” Subsection under the “FEMTOCELL SYSTEM ARCHITECTURE” Section, above. <figref idref="DRAWINGS">FIG. 41</figref> illustrates the protocol architecture for CS mode SMS in some embodiments.

0502The Femtocell CS mode SMS support is based on the same mechanism that is utilized for CS mobility management and call control. On the UE <b>4105</b> side, the SMS layers <b>4110</b> (including the supporting CM sub-layer functions) utilize the services of the MM layer <b>4115</b> to transfer SMS messages per standard circuit mode implementation. The SM-CP protocol is effectively tunneled between the UE <b>4105</b> and the MSC <b>4115</b> using the message relay functions in the GA-CSR protocol. As with CS mobility management and call control procedures, SMS uses the UE specific TCP signaling connection between the FAP and the INC <b>4120</b>, providing reliable SMS delivery over the Up interface <b>4125</b>.

0503B. Packet Mode (PS Mode) SMS Services

0504The Femtocell protocol architecture related to PS mode SMS support builds on the packet services signaling architecture described in the “PS domain—control plane architecture” Subsection under the “FEMTOCELL SYSTEM ARCHITECTURE” Section, above. <figref idref="DRAWINGS">FIG. 42</figref> illustrates the GAN protocol architecture for packet mode SMS in some embodiments.

0505On the UE <b>4205</b> side, the SMS layers <b>4210</b> (including the supporting CM sublayer functions) utilize the services of the GMM layer <b>4215</b> to transfer SMS messages per the standard packet mode implementation. The SM-CP protocol is effectively tunneled between the UE <b>4205</b> and the SGSN <b>4220</b> using the message relay functions in the GA-PSR protocol. As with the packet services signaling procedures, SMS uses the UE specific TCP signaling connection between the FAP and the INC <b>4225</b>, providing reliable SMS delivery over the Up interface <b>4230</b>.

0506C. SMS Scenarios

0507The following scenarios illustrate the message flows involved for various SMS scenarios via the Femtocell.

05081. Circuit Mode Mobile-originated SMS

0509<figref idref="DRAWINGS">FIG. 43</figref> illustrates a mobile originated SMS transfer via GAN circuit mode in some embodiments. As shown, the user enters a message and invokes the mobile-originated SMS function on the UE <b>4305</b> in idle mode. Steps <b>4</b> to <b>10</b> in <figref idref="DRAWINGS">FIG. 43</figref> are Steps <b>2</b> to <b>7</b> in the “Mobile originated call” Subsection under the “CALL MANAGEMENT” Section, above. Next, the UE <b>4305</b> sends (in Step <b>8</b>) the SMS message encapsulated in a CP-DATA message to the FAP <b>4310</b> over the air interface.

0510The FAP relays (in Step <b>9</b>) the CP-DATA message encapsulated in a GA-CSR UL DIRECT TRANSFER message to the INC <b>4315</b>. The INC forwards (in Step <b>10</b>) the CP-DATA message to the MSC <b>4320</b> using RANAP Direct Transfer message. The MSC forwards (in Step <b>11</b>) the message to the SMSC via the SMS interworking MSC (IWMSC) <b>4325</b> using the MAP-MO-FORWARD-SM Invoke message.

0511The MSC sends (in Step <b>12</b>) CP-DATA-ACK to acknowledge the receipt of the CP-DATA message. The SM-CP is designed in a way that every CP-DATA block is acknowledged on each point-to-point connection between the UE and SMSC (SM Service Center) to ensure that the under-laying transport layer (in this case RANAP) works error free since there is no explicit ack to a RANAP Direct Transfer message.

0512The INC <b>4315</b> relays (in Step <b>13</b>) the acknowledgement to the FAP <b>4310</b>. The FAP forwards (in Step <b>14</b>) the CP-DATA-ACK to the UE <b>4305</b> over the air interface. The SMSC sends (in Step <b>15</b>) a SMS message in response to the IWMSC and the IWMSC sends the response to the MSC in the MAP-MO-FORWARD-SM Return Result message.

0513Next, the MSC <b>4320</b> relays the response (in Step <b>16</b>) to the INC <b>4315</b> in the CP-DATA message. The INC <b>4315</b> relays (in Step <b>17</b>) this to the FAP <b>4310</b> using GA-CSR DL DIRECT TRANSFER. The FAP relays (in Step <b>18</b>) the response to the UE over the air interface using the existing RRC connections.

0514As part of SM-CP ack process, the UE acknowledges (in Step <b>19</b>) the receipt of CP-DATA to the FAP. The FAP relays (in Step <b>20</b>) the acknowledgement to the INC. The INC forwards (in Step <b>21</b>) the acknowledgement to the MSC using the RANAP Direct Transfer message.

0515Next, the MSC <b>4320</b> sends (in Step <b>22</b>) Iu Release message to the INC indicating a request to release the session resources. The SCCP Connection Identifier is used to determine the corresponding session. The INC <b>4315</b> in turn releases (in Step <b>23</b>) the GA-CSR connection to the FAP for the specific session. Also, the FAP <b>4310</b> releases (in Step <b>24</b>) corresponding radio resources towards the UE. Finally, the INC acknowledges (in Step <b>25</b>) the release in an Iu Release Complete message to the MSC. The SCCP connection associated with the call between the INC and the MSC is released.

05162. CS Mode Mobile-Terminated SMS

0517<figref idref="DRAWINGS">FIG. 44</figref> illustrates a CS mode mobile terminated SMS transfer via Femtocell in some embodiments. As shown, the SMSC <b>4425</b> sends (in Step <b>1</b>) a SMS message destined for the UE <b>4405</b> to the SMS gateway MSC (GMSC) <b>4420</b>. The GMSC queries the HLR for routing information using the MAP-SEND-ROUTING-INFO-SM Invoke message.

0518The HLR responds (in Step <b>2</b>) with the MSC number associated with the serving MSC. The SMS GMSC delivers (in Step <b>3</b>) the SMS message to the MSC using the MAP MT-FORWARD-SM Invoke message. Steps <b>4</b> to <b>10</b> are the same as Steps <b>2</b> to <b>8</b> in “Mobile Terminated Call” Section above, except that the user is attempting to terminate an SMS message; therefore, only a signaling channel is necessary.

0519Next, the MSC <b>4420</b> sends (in Step <b>11</b>) the SMS message encapsulated in a CP-DATA message to the INC <b>4415</b>. The INC relays (in Step <b>12</b>) this to the FAP <b>4410</b> using GA-CSR DL DIRECT TRANSFER. The FAP relays (in Step <b>13</b>) the CP-DATA message to the UE <b>4405</b> over the air interface using the existing RRC connections.

0520As part of SM-CP ack process, the UE acknowledges (in Step <b>14</b>) the receipt of CP-DATA to the FAP. The FAP relays (in Step <b>15</b>) the acknowledgement to the INC. The INC forwards (in Step <b>16</b>) the acknowledgement to the MSC using the RANAP Direct Transfer message.

0521The SMS entity on the UE acknowledges (in Step <b>17</b>) the SMS message via another CP-DATA message (response) which is sent to the FAP over the air interface. The FAP relays (in Step <b>18</b>) the response CP-DATA message encapsulated in a GA-CSR UL DIRECT TRANSFER message to the INC. The INC forwards (in Step <b>19</b>) the response CP-DATA message to the MSC using RANAP Direct Transfer message.

0522Next, the MSC <b>4420</b> sends the response (in Step <b>20</b>) to the SMS GMSC <b>4425</b> in the MAP-MT-FORWARD-SM Return Result message. The GMSC relays the response to the SMSC. The MSC acknowledges (in Step <b>21</b>) the receipt of CP-DATA to the INC. The INC <b>4415</b> relays (in Step <b>22</b>) the CP-DATA-ACK to the FAP.

0523Next, the FAP <b>4410</b> forwards (in Step <b>23</b>) the CP-DATA-ACK to the UE <b>4405</b> over the air interface. The MSC <b>4420</b> sends (in Step <b>24</b>) Iu Release message to the INC <b>4415</b> indicating a request to release the session resources. The SCCP Connection Identifier is used to determine the corresponding session.

0524The INC <b>4415</b> in turn releases (in Step <b>25</b>) the GA-CSR connection to the FAP for the specific session. The FAP releases (in Step <b>26</b>) corresponding radio resources towards the UE. The INC acknowledges (in Step <b>27</b>) the release in an Iu Release Complete message to the MSC. The SCCP connection associated with the call between the INC and the MSC is released

XI. EMERGENCY SERVICES

0525Transparent support for emergency services is a key regulatory requirement. Femtocell emergency services support capabilities include support for flexible UMTS-to-Femtocell SAI mapping and INC assignment functionality. This allows the FAP to be assigned to an INC that is, in turn, connected to an MSC that can route calls to the PSAP in the Femtocell service area. It also allows the service provider to define Femtocell service areas that align with macro network service areas, to leverage the existing service area based PSAP routing approach.

0526Femtocell emergency services support capabilities also include support for the retrieval and storage of FAP location information from an external database, using the enhanced service access control functions. Femtocell emergency services support capabilities further include support for the RANAP Location Report procedure, by which the INC returns the FAP location information to the MSC during emergency call processing. Some embodiments do not support emergency calling from an un-authorized UE over a given FAP (due to the Service Access Control for the specific FAP).

0527One of the functions of the UMTS-Femtocell mapping process is to assign a Femtocell Service Area for calls made by the UE using the Femtocell. The FAP, during registration, provides information on macro coverage (such as macro LAI, macro 3G cell-id, etc) which can be mapped to a Femtocell Service Area Identification (SAI). This Femtocell SAI can be used to support the ability to route emergency calls to the correct PSAP; i.e., based on SAI. However, to meet the requirement to route the emergency call to the correct PSAP, there are actually two possible approaches: (1) Service Area (i.e. SAI) Based Routing, and (2) Location Based Routing.

0528A. Service Area Based Routing

0529With Service Area Based Routing, the PSAP routing decision is based on the Service Area Code (SAC) included within the SAI. <figref idref="DRAWINGS">FIG. 45</figref> illustrates a service area based routing scenario of some embodiments. As shown, the user originates (in Step <b>1</b>) an emergency call using the UE <b>4505</b> camped on the Femtocell. The UE establishes (in Step <b>2</b>) a RRC connection with the FAP with the establishment cause of emergency call.

0530Upon request from the upper layers, the UE sends (in Step <b>3</b>) the CM Service Request (with CM Service Type set to “Emergency Call Establishment”) to the FAP <b>4510</b>. The FAP performs (in Step <b>4</b>) the GA-CSR Connection Establishment procedure (with establishment cause indicating an Emergency call) with the INC <b>4515</b> as described in previous sections.

0531The FAP <b>4510</b> then forwards (in Step <b>5</b>) the CM Service Request to the INC <b>4515</b> using a GA-CSR UL DIRECT TRANSFER message. The INC <b>4515</b> establishes a SCCP connection to the MSC <b>4520</b> and forwards (in Step <b>6</b>) the CM Service Request to the MSC <b>4520</b> using the RANAP Initial UE Message. This initial message includes information about the location area (LAI) and service area (SAI) assigned to the specific FAP over which the emergency call was initiated.

0532The MSC <b>4520</b>, INC <b>4515</b> and UE <b>4505</b> continue (in Step <b>7</b>) call establishment signaling. The MSC determines the serving PSAP based on the service area of the calling UE and routes (in Step <b>8</b>) the emergency call to the appropriate PSAP. Additional signal messages are exchanged between the UE and PSAP and the emergency call is established (in Step <b>9</b>) between the UE and the appropriate serving PSAP.

0533B. Location Based Routing

0534One of the drawbacks service area based routing is that it would require that Femtocell service area be split into multiple service areas based on PSAP routing requirements. The location based routing method removes this limitation. Location based routing is also known as “X/Y routing” or “Routing by position” and is defined in “Location Services (LCS); Functional description; Stage 2”, 3GPP TS 23.271. Some embodiments support Location based routing while some other embodiments do not support Location based routing.

XII. FEMTOCELL SECURITY

0535GAN Femtocell supports security mechanisms at different levels and interfaces as depicted in <figref idref="DRAWINGS">FIG. 46</figref>. As shown, the security mechanisms over the Up interface <b>4605</b> protect signaling, voice and data traffic flows between the FAP <b>4610</b> and the GANC SeGW <b>4615</b> from unauthorized use, data manipulation and eavesdropping; i.e. authentication, encryption and data integrity mechanisms are supported.

0536Authentication of the subscriber by the core network occurs between the MSC/VLR or SGSN <b>4620</b> and the UE <b>4625</b> and is transparent to the GANC <b>4640</b>. The air interface between the UE <b>4625</b> and FAP <b>4610</b> is protected via encryption (ciphering) and integrity checks. In some embodiments the use of ciphering on the air interface is optional.

0537Additional application level security mechanisms may be employed in the PS domain to secure the end-to-end communication between the FAP <b>4605</b> and the application server <b>4630</b>. For example, the FAP may run the HTTP protocol over an SSL session for secure web access.

0538All signaling traffic and user-plane traffic sent between FAP and GANC over the Up interface <b>4605</b> is protected by a secure tunnel (e.g., an IPSec tunnel) between the FAP <b>4605</b> and GANC-SeGW <b>4615</b>, that provides mutual authentication (using SIM or USIM credentials), encryption and data integrity using the same mechanisms as specified in “3G security; Wireless Local Area Network (WLAN) interworking security”, 3GPP TS 33.234 standard, hereinafter “TS 33.234 standard”. The use of a single secure tunnel between the FAP <b>4610</b> and the GANC <b>4640</b> enables multiple UEs <b>4625</b> (only one is shown in <figref idref="DRAWINGS">FIG. 46</figref> for simplicity) as well as the Femtocell itself (e.g., the FAP signaling or when the FAP supports local service using the FAP IMSI, the signaling and the user plane for the FAP utilize the same IPSec tunnel). The advantages of using a single IPSec tunnel between the FAP and the GANC include relieving the SeGW from supporting a large number of secure tunnels.

0539A. Authentication

0540In some embodiments, the Up interface supports the ability to authenticate the FAP with the GANC (for the purposes of establishing the secure tunnel) using UMTS credentials. Authentication between FAP and GANC shall be performed using EAP-AKA or EAP-SIM within IKEv2.

0541The FAP and GANC-SeGW establish a security association for protecting signaling traffic and user-plane (voice and data) traffic. The protocol for authentication is IKEv2. Mutual authentication and key generation is provided by EAP-AKA or EAP-SIM.

0542The basic elements of these procedures are the following. The FAP connection with the GANC-SeGW is initiated by starting the IKEv2 initial exchanges (IKE_SA_INIT). The EAP-AKA or EAP-SIM procedure is started as a result of these exchanges. The EAP-SIM procedure for FAP with SIM only or FAP with USIM, but not capable of UMTS AKA, is performed between FAP and AAA server (that has access to the AuC/HLR/HSS to retrieve subscriber information). The EAP-AKA procedure for FAP with USIM and the FAP is capable of UMTS AKA, is performed between FAP and AAA server. The GANC-SeGW acts as relay for the EAP-SIM/EAP-AKA messages.

0543When the EAP-AKA/EAP-SIM procedure has completed successfully, the IKEv2 procedure can be continued to completion and the signaling channel between FAP and GANC-SeGW is secured. The FAP can then continue with the discovery or registration procedure. Signaling flows for EAP-AKA/EAP-SIM authentication are shown in the following subsection.

05441. EAP-SIM Procedure for Authentication

0545The EAP-SIM authentication mechanism is specified in “Extensible Authentication Protocol Method for GSM Subscriber Identity Modules (EAP-SIM)”, IETF RFC <b>4686</b>. This section describes how this mechanism is used in Femtocell. <figref idref="DRAWINGS">FIG. 47</figref> illustrates EAP-SIM authentication procedure in some embodiments. As shown, the FAP <b>4705</b> connects to the generic IP access network and obtains (in Step <b>1</b>) the IP address of the Default or the Serving SeGW via DNS query. In response, the DNS server <b>4710</b> returns (in Step <b>2</b>) the IP address of the SeGW.

0546Next, the FAP <b>4705</b> initializes the IKEv2 authentication procedure by starting (in Steps <b>3</b><i>a</i>-<b>3</b><i>c</i>) the IKE_SA_INIT exchange. It indicates the desire to use EAP by leaving out the AUTH payload from message <b>3</b>, the first message of the IKE_AUTH exchange, and the initiator identity is composed compliant with the Network Access Identifier (NAI) format specified in “The Network Access Identifier”, IETF RFC <b>2486</b>, hereinafter “IETF RFC <b>2486</b>”, which includes the IMSI and an indication that EAP-SIM should be used.

0547Next, the GANC-SeGW <b>4715</b> sends (in Step <b>4</b>) an EAP Response/Identity message to the AAA server <b>4720</b>, including the initiator identity included in the third IKE message. The leading digit of the NAI indicates that the FAP wishes to use EAP-SIM. The AAA server <b>4720</b> identifies the subscriber as a candidate for authentication with EAP-SIM, based on the received identity, and verifies that EAP-SIM shall be used based on subscription information. The AAA then sends (in Step <b>5</b>) the EAP Request/SIM-Start packet to GANC-SeGW <b>4715</b>.

0548The GANC-SeGW forwards (in Step <b>6</b>) the EAP Request/SIM-Start packet to FAP. The FAP chooses a fresh random number NONCE_MT. The random number is used in network authentication. The FAP sends (in Step <b>7</b>) the EAP Response/SIM-Start packet, including NONCE_MT, to the GANC-SeGW.

0549The GANC-SeGW forwards (in Step <b>8</b>) the EAP Response/SIM-Start packet to the AAA Server. The AAA server <b>4720</b> requests (in Step <b>9</b>) authentication data from the HLR <b>4725</b>, based on the IMSI. The AAA server could instead use cached triplets previously retrieved from the HLR to continue the authentication process.

0550Optionally, the AAA <b>4720</b> receives (in Step <b>10</b>) user subscription and multiple triplets from the HSS/HLR <b>4725</b>. AAA server determines the EAP method (SIM or AKA) to be used, according to the user subscription and/or the indication received from the FAP. In this sequence diagram, it is assumed that the FAP holds a SIM and EAP-SIM will be used.

0551The AAA server formulates an EAP-SIM/Challenge with multiple RAND challenges, and includes a message authentication code (MAC) whose master key is computed based on the associated Kc keys, as well as the NONCE_MT. A new re-authentication identity may be chosen and protected (i.e. encrypted and integrity protected) using EAP-SIM generated keying material. The AAA Server sends (in Step <b>11</b>) this RAND, MAC and re-authentication identity to the GANC-SeGW in the EAP Request/SIM-Challenge message. The GANC-SeGW forwards (in Step <b>12</b>) the EAP Request/SIM-Challenge message to the FAP.

0552The FAP runs (in Step <b>12</b>) N times the GSM A3/A8 algorithm in the SIM, once for each received RAND. This computing gives N SRES and Kc values. The FAP calculates its copy of the network authentication MAC with the newly derived keying material and checks that it is equal with the received MAC. If the MAC is incorrect, the network authentication has failed and the FAP cancels the authentication. The FAP continues the authentication exchange only if the MAC is correct. The FAP calculates a new MAC with the new keying material covering the EAP message concatenated to the N SRES responses. If a re-authentication ID was received, then the FAP stores this ID for future authentications.

0553The FAP <b>4705</b> sends (in Step <b>14</b>) EAP Response/SIM-Challenge including calculated MAC to the GANC-SeGW <b>4715</b>. The GANC-SeGW forwards (in Step <b>15</b>) the EAP Response/SIM-Challenge message to the AAA Server <b>4720</b>. The AAA Server verifies (in Step <b>16</b>) that its copy of the response MAC is equal to the received MAC.

0554If the comparison in step <b>16</b> is successful, then the AAA Server sends (in Step <b>17</b>) the EAP Success message to the GANC-SeGW. The AAA Server includes derived keying material for confidentiality and/or integrity protection between FAP and GANC-SeGW, in the underlying AAA protocol message (i.e. not at EAP level).

0555The GANC-SeGW informs (in Step <b>18</b>) the FAP about the successful authentication with the EAP Success message. Now the EAP-SIM exchange has been successfully completed, the IKE signaling can be completed (in Step <b>19</b>). The Secure Association between FAP and GANC-SeGW has been completed and the FAP can continue with the Femtocell discovery or registration procedure.

05562. EAP-AKA Procedure for Authentication

0557The EAP-AKA authentication mechanism is specified in “Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)”, IETF RFC <b>4187</b>. This section describes how this mechanism is used in Femtocell. <figref idref="DRAWINGS">FIG. 48</figref> illustrates EAP-AKA authentication procedure of some embodiments. As shown, the FAP <b>4805</b> connects to the generic IP access network and obtains (in Step <b>1</b>) the IP address of the Default or the Serving SeGW via DNS query. The DNS server <b>4810</b> returns (in Step <b>10</b>) the IP address of the SeGW.

0558The FAP <b>4805</b> initializes the IKEv2 authentication procedure by starting the IKE_SA_INIT exchange (Steps <b>3</b><i>a</i>-<b>3</b><i>c</i>). It indicates the desire to use EAP by leaving out the AUTH payload from message <b>3</b>, the first message of the IKE_AUTH exchange, and the initiator identity is composed compliant with the Network Access Identifier (NAI) format specified in the IETF RFC <b>2486</b> which includes the IMSI and an indication that EAP-AKA should be used.

0559Next, the GANC-SeGW <b>4815</b> sends (in Step <b>4</b>) an EAP Response/Identity message to the AAA server <b>4820</b>, including the initiator identity included in the third IKE message. The leading digit of the NAI indicates that the FAP wishes to use EAP-AKA. The AAA server identifies the subscriber as a candidate for authentication with EAP-AKA, based on the received identity, and verifies that EAP-AKA shall be used based on subscription information, The AAA server requests (in Step <b>5</b>) the user profile and UMTS authentication vector(s) from the HSS/HLR <b>4825</b>, if these are not available in the AAA server.

0560Optionally, the AAA receives (in Step <b>6</b>) user subscription and UMTS authentication vector(s) from the HSS/HLR. The UMTS authentication vector consists of random part (RAND), an authentication token (AUTN), an expected result part (XRES) and sessions keys for integrity check (IK) and encryption (CK). The AAA server determines the EAP method (SIM or AKA) to be used, according to the user subscription and/or the indication received from the FAP. In this sequence diagram, it is assumed that the FAP holds a USIM and EAP-AKA will be used.

0561Next, the AAA server <b>4820</b> formulates an EAP-Request/AKA Challenge with RAND, AUTN and includes a message authentication code (MAC) whose master key is computed based on the associated IK and CK. A new re-authentication identity may be chosen and protected (i.e. encrypted and integrity protected) using EAP-AKA generated keying material. The AAA Server sends (in Step <b>7</b>) the RAND, AUTN, MAC and re-authentication identity to the GANC-SeGW <b>4815</b> in the EAP Request/AKA-Challenge message.

0562The GANC-SeGW forwards (in Step <b>8</b>) the EAP Request/AKA-Challenge message to the FAP. The FAP runs (in Step <b>9</b>) UMTS algorithm on the USIM. The USIM verifies that the AUTN is correct and hereby authenticates the network. If AUTN is incorrect, the FAP rejects the authentication. If AUTN is correct, the USIM computes RES, IK and CK. The FAP calculates a new MAC with the new keying material (IK and CK) covering the EAP message. If a re-authentication ID was received, then the FAP stores this ID for future authentications.

0563The FAP then sends (in Step <b>10</b>) EAP Response/AKA-Challenge including calculated RES and MAC to the GANC-SeGW. The GANC-SeGW forwards (in Step <b>11</b>) the EAP Response/AKA-Challenge message to the AAA Server.

0564The AAA Server verifies (in Step <b>12</b>) the received MAC and compares XRES to the received RES. If the checks in Step <b>12</b> are successful, then the AAA Server sends (in Step <b>13</b>) the EAP Success message to the GANC-SeGW. The AAA Server includes derived keying material for confidentiality and/or integrity protection between FAP and GANC-SeGW, in the underlying AAA protocol message (i.e. not at EAP level).

0565The GANC-SeGW informs (in Step <b>14</b>) the FAP about the successful authentication with the EAP Success message. Now the EAP-SIM exchange has been successfully completed, the IKE signaling can be completed (in Step <b>15</b>). The Security Association between FAP and GANC-SeGW has been completed and the FAP can continue with the Femtocell discovery or registration procedure.

05663. Fast Re-Authentication

0567When the authentication process is performed frequently, especially with a large number of connected Femtocell Access Points, performing fast re-authentication can reduce the network load resulting from this authentication. The fast re-authentication process allows the AAA server to authenticate a user based on keys derived from the last full authentication process.

0568The FAP and GANC-SeGW can use a procedure for fast re-authentication in order to re-authenticate an FAP e.g. when setting up a new SA because the IP address of the FAP has changed. Fast re-authentication is provided by EAP-AKA, and does not make use of the UMTS algorithms. The FAP may use the re-authentication ID in the IKE_SA_INIT. The decision to make use of the fast re-authentication procedure is taken by the AAA server.

0569The basic elements of these procedures are the following. The FAP initiates a new SA with a GANC-SeGW that it was previously connected to and uses the re-authentication ID (re-authentication ID received during the previous full authentication procedure) in the IKE_SA_INIT exchange. The EAP-AKA procedure is started as a result of these exchanges. The AAA server and FAP re-authenticate each other based on the keys derived on the preceding full authentication.

0570B. Encryption

0571All control and user plane traffic over the Up interface shall be sent through the IPSec tunnel that is established as a result of the authentication procedure. Encryption shall use the negotiated cryptographic algorithm, based on core network policy, enforced by the GANC-SeGW.

0572The FAP and GANC-SeGW set up one Security Association through which all traffic is sent. A single negotiated ciphering algorithm is applied to the connection.

05731. Establishment of a Security Association

0574After the authentication procedure, the FAP shall request an IP address on the network protected by the GANC-SeGW (i.e. the public IP interface of the INC). The FAP shall set up one IPSec Security Association (SA) between FAP and GANC-SeGW.

0575The FAP shall initiate the creation of the SA; i.e. it shall act as initiator in the Traffic Selector negotiation. The protocol ID field in the Traffic Selectors (TS) shall be set to zero, indicating that the protocol ID is not relevant. The IP address range in the TSi shall be set to the address assigned to the FAP (within the network protected by the GANC-SeGW). The IP address range in the TSr shall be set to 0.0.0.0-255.255.255.255. The FAP and GANC-SeGW shall use the IKEv2 mechanisms for detection of NAT, NAT traversal and keep-alive.

0576All control and user plane data over the Up interface between FAP and INC shall be sent through the SA. The ciphering mode is negotiated during connection establishment. During setup of the SA, the FAP includes a list of supported encryption algorithms as part of the IKE signaling, which include the mandatory and supported optional algorithms defined in the IPSec profile, and NULL encryption. The GANC-SeGW selects one of these algorithms, and signals this to the FAP.

0577When NULL encryption is applied, both control and user-plane traffic is sent unencrypted. This configuration can be selected e.g. when the connection between the generic IP access network and the GANC is under operator control. The integrity algorithm is the same as for either configuration i.e. non-ciphered traffic is still integrity protected.

0578C. Profile of IKEv2

0579In some embodiments, profile of IKEv2 for Femtocell system is similar to the profile defined in TS 43.318 standard.

0580D. Profile of IPSec ESP

0581In some embodiments, profile of IPSEC ESP for Femtocell system is similar to the profile defined in TS 43.318 standard.

0582E. Security Mode Control

0583<figref idref="DRAWINGS">FIG. 49</figref> illustrates the message flow for security mode control in some embodiments. As shown, the CN (VLR/SGSN) <b>4920</b> and the UE <b>4905</b> perform (in Step <b>1</b>) mutual authentication using AKA procedures. The CN authentication is initiated by the CN as a result of the CN processing an initial L3 message from the UE.

0584Upon successful authentication, the CN sends (in Step <b>2</b>) RANAP “Security Mode Command” message to GANC. This message includes the integrity key (IK) key, the ciphering (or encryption) key (CK), the user integrity algorithm (UIA), and the ciphering (or user encryption) algorithm (UEA) to be used for ciphering.

0585In some embodiments, the GANC stores the ciphering and integrity keys and the algorithms. The GANC sends (in Step <b>3</b>) a GA-CSR SECURITY MODE COMMAND with the ciphering and integrity keys and algorithms associated with the specific UE IMSI to the FAP <b>4910</b>. The FAP stores the ciphering and integrity keys and algorithm (in Step <b>4</b>) for the specific UE. The FAP should ensure that these keys are not accessible to 3^rdparty applications or any other module on the FAP. Additionally, these keys should not be stored on any persistent storage. The CK and UEA are used to protect the air interface between the FAP and the UE by encrypting the traffic between the FAP and the UE. The IK and the UIA are used to ensure the integrity of the messages exchanged between the FAP and the UE over the air interface, for example by determining that the messages are not changed. In some embodiments, the UIA and the UEA are software methods executed by a processor.

0586The FAP generates a random number (FRESH) and computes the downlink (i.e., from the FAP to the UE) message authentication code (MAC) using the integrity key (IK) and integrity algorithms (MAC-I) and sends (in Step <b>5</b>) the Security Mode command to the UE <b>4905</b> along with the computed message authentication code for integrity (MAC-I) and the FRESH. The FRESH variable represents a random number or nonce as defined in “3G Security; Security architecture”, 3GPP TS 33.102 standard, hereinafter “TS 33.102 standard”. The UE computes (in Step <b>6</b>) the MAC-I locally (expected MAC-I or XMAC-I) and verifies (in Step <b>6</b>) that the received downlink MAC-I is same. The UE computes XMAC-I on the message received by using the indicated UIA, COUNT-I generated from the stored START and the received FRESH parameter as defined in TS 33.102 standard. The downlink integrity check is started from this message onwards. For all subsequent messages sent from the FAP to the UE (the downlink messages), steps similar to Steps <b>5</b> to <b>6</b> are used to ensure the integrity of the messages.

0587Upon successful verification of the MAC, the UE responds back (in step <b>7</b>) with the Security Mode Complete command and also sends the MAC-I for the uplink (i.e., from the UE to the FAP) message. The FAP computes (in Step <b>8</b>) XMAC-I for the uplink message and verifies (in Step <b>8</b>) the received MAC-I is same as that of computed XMAC-I. The uplink integrity check is started from this message onwards. For all subsequent messages sent from the UE to the FAP (the uplink messages), steps similar to Steps <b>7</b> to <b>8</b> are used to ensure the integrity of the messages.

0588MAC-I is the sender's computed MAC-I and XMAC-I is the expected MAC-I computed by the receiver. As described above, the computation is done for a given message using the algorithms and other variables which are known to the sender and receiver only. This prevents a man-in-the-middle attack, as the middle entity will not have the necessary information to compute MAC-I and hence cannot tamper the message.

0589Upon successful verification of the uplink MAC, the FAP sends (in Step <b>9</b>) the GA-CSR Security mode complete command to the GANC. The GANC relays (in Step <b>10</b>) the Security Mode Complete command to the CN via corresponding RANAP message.

0590F. Core Network Authentication

0591The core network AKA based authentication provides mutual authentication between the user and the network. The AKA procedure is also used to generate the ciphering keys (encryption and integrity) which in turn provide confidentiality and integrity protection of signaling and user data. The basis of mutual authentication mechanism is the master key K (permanent secret with a length of 128 bits) that is shared between the USIM of the user and home network database. The ciphering key (Ck) and the integrity key (<b>1</b><i>k</i>) are derived from this master key K.

0592<figref idref="DRAWINGS">FIG. 50</figref> illustrates the AKA procedure used for mutual authentication in some embodiments. As shown, when the UE <b>5005</b> camps on the Femtocell Access Point <b>5010</b>, it initiates (in Step <b>1</b>) a Location Update Request (or Location Updating Request) towards the CN. The INC <b>5015</b> forwards) in Step <b>2</b>) the Location Update request in a RANAP message to the VLR/SGSN <b>5020</b>.

0593This triggers the authentication procedure in the VLR/SGSN and it sends (in Step <b>3</b>) an authentication data request MAP message to the Authentication Center (AuC) in the Home Environment (HE) <b>5025</b>. The AuC includes the master keys of the UEs and based on the IMSI, the AuC will generate the authentication vectors for the specific UE. The vector list is sent back (in Step <b>4</b>) to the VLR/SGSN in the authentication data response MAP message.

0594The VLR/SGSN selects (in Step <b>5</b>) one authentication vector from the list (only 1 vector is needed for each run of the authentication procedure). The VLR/SGSN sends (in Step <b>6</b>) user authentication request (AUTREQ) message to the INC. This message also includes two parameters RAND and AUTN (from the selected authentication vector).

0595The INC <b>5015</b> relays (in Step <b>7</b>) the AUTREQ message to the FAP <b>5010</b> in a GA-CSR DL DIRECT TRANSFER message. The FAP forwards (in Step <b>8</b>) the AUTREQ to the UE over the air interface. The USIM on the UE includes the master key K and using it with the parameters RAND and AUTN as inputs, the USIM carries out computation resembling generation of authentication vectors in the AuC. From the generated output, the USIM verifies (in Step <b>9</b>) if the AUTN was generated by the right AuC.

0596The USIM computation also generates (in Step <b>10</b>) a RES which is sent towards the CN in an authentication response message to the CN. The FAP forwards (in Step <b>11</b>) the Authentication Response to INC. The INC relays (in Step <b>12</b>) the response along with the RES parameter in a RANAP message to the CN.

0597The VLR/SGSN verifies (in Step <b>13</b>) compares the UE response RES with the expected response XRES (which is part of authentication vector). If there is a match, authentication is successful. The CN may then initiate (in Step <b>14</b>) a Security Mode procedure (as described in the Subsection “Security mode control”, above) to distribute the ciphering keys to the INC.

0598G. Service Theft in Femtocell

0599By definition, the FAP has a radio interface (Uu) to communicate with UEs and a network interface (Up) to the mobile network. The FAP relays messages between the UE and core network and can eavesdrop and intercept these messages. The FAP, if compromised, becomes the infamous ‘man’ of the man-in-the-middle security exposure.

0600In normal operation, the macro cell network directs UEs to scan for the Femtocell UTRA Absolute Radio Frequency Channel Number (UARFCN) and scrambling code (SC) so when a UE detects FAP radio coverage, the UE can attempt to camp on the FAP. The FAP {UARFCN, SC} is expected to be configured in the macro network RNC's neighbor cell list so that RNC can provide the UE with this neighbor cell list, thus resulting in the UE performing the scans of the neighbors cells and eventual cell selection of a better neighbor for camping. The UE performs a location update, provides its identity, whether IMSI or TMSI, expects to be authenticated, and then proceeds to camp on the Femtocell for mobile service. This is exactly what is supposed to happen when the UE visits a network authorized FAP.

0601When the FAP is compromised or is a rogue, then the UE could be exposing itself to theft of service. When the UE provides its identity to the FAP, the FAP can masquerade as the UE to the mobile network. Normally, UE authentication would prevent this kind of identity theft, but being in the middle of the communication between the core network and the UE, the FAP can relay authentication requests to the victim UE to defeat authentication.

0602The UE believes it is being authenticated by the network and provides the correct authentication response to the FAP. The FAP sends the correct response to the core network and the core network now believes the FAP has been authenticated. In between network initiated authentication requests, the FAP can request and receive service from the mobile network disguised as the victim UE. For example, calls originated by the FAP would now be charged to the victim UE. UMTS signaling message integrity mechanisms do not help in this case because the integrity protection is provided over the air interface between the UE and the FAP.

0603Since the FAP is in the possession of the end user and communicates with the GANC over the Internet, it is possible for a compromised or rogue FAP to attempt to circumvent the UMTS security architecture. A rogue FAP is the classical man-in-the-middle attacker between the UE and the CN. Without adequate network security validations and the enforcement of access policies, rogue FAPs can masquerade as a victim UE and use mobile network services using the victim UE's identity. A FAP is categorized in the following three access control modes: closed access, semi-open access, or open access.

0604In a closed access case, access to complete Femtocell services over a given FAP is restricted to a closed group of subscribers. In a semi-open access case, limited access is provided to all subscribers. A subscriber who is not part of the closed group is allowed to receive incoming calls and SMS over the semi-open FAP. Additionally, the subscriber is also allowed to make emergency calls using the FAP operating in semi-open access mode. All other services, such as outgoing calls, are blocked. Finally, in an open access case, all subscribers of a given operator are allowed full service access over a FAP operating in open access mode. The following techniques are used in some embodiments to protect against UE masquerade and theft of service at a FAP operating in one of above mentioned modes.

06051. Closed Access Points

0606In a closed access FAP, UEs that are members of the FAP's private user group cannot be victimized because the FAP and the UEs in the private user group are linked by the subscription process. The GANC can enforce network-based service access controls to prevent victim UEs from being trapped by a rogue FAP. If the UE is not a member of the private user group of the rogue FAP, the GANC will deny service access to the UE. This means the rogue FAP is prevented from stealing service with the victim UE's identity.

0607The GANC also strictly binds transactions performed under each UE registration context to the original authorized UE identity to prevent a rogue FAP from piggybacking messages using a victim UE identity through the authorized UE context. The strict binding requires the GANC to track the identity of each UE even as it is assigned TMSI and P-TMSI for User Identity Confidentiality. Prevention of service theft in a closed access mode is described in detail further below.

06082. Semi-Open and Open Access Points

0609The potential for a rogue FAP to masquerade as a victim UE is only available on the semi-open and open access points. The victim UEs would be the UEs that the network allows to camp on the rogue FAP but is not a member of the FAP's private user group. For those UEs, the theft of service potential is real because the rogue FAP has an incentive to charge its usage to the victim UE subscription account.

0610Note, the theft-of-service scenario is only possible while a victim UE is camped on the rogue FAP. The rogue FAP can authenticate to the core network (CN) as the UE and then request services from the CN masquerading as the UE. So long that the victim UE remains camped at the rogue FAP, the FAP can continue to pass authentication requests and carry on the masquerade.

0611For semi-open FAPs, by definition, prevents outgoing services to be initiated by UEs that are not a member of the FAP's private user group. Network-based enforcement of the semi-open access controls can prevent rogue FAPs from stealing service by masquerading as a victim UE. However, a rogue FAP can block incoming calls to the victim UE or eavesdrop on the conversation while the victim UE is camped on the rogue FAP. The semi-open FAP scenario is similar to the open FAP scenario described below.

0612For open FAPs, the GANC by definition cannot place restrictions on the usage of mobile network services for any UE. It is also not possible to determine on a per call basis whether the call was legitimately made by the UE or whether the FAP is masquerading as a victim UE. This makes network enforcement of UE access controls ineffective for preventing UE masquerade. The prevention method must focus on ensuring only genuine and unmodified FAPs are granted open access.

06133. Enhanced Security Solution for Open Access Points

0614Open FAPs can be misused through the following two scenarios: (1) Complete replacement of a genuine FAP with rogue equipment and (2) Modification of the existing software executing on the FAP from an authorized vendor.

0615a) Detection of Genuine FAP

0616The replacement of a genuine FAP with rogue equipment can be prevented using a technique based on public and private keys. In this solution the FAP is required to provide a Message Authentication Code (MAC), computed from the vendor's private key, with the UMA Registration message. The GANC, using the AAA, can verify the MAC on the UMA Registration message by comparing the MAC with one computed with the FAP vendor's public key. Only genuine FAP s can provide the correct MAC in the UMA Registration message.

0617Procedure details are as follows. Each FAP vendor generates a private/public key pair. The public key is stored in a FAP database in the network. When the FAP registers with the GANC, the GANC sends a Register challenge message by including a RAND number in the challenge. The FAP sends the challenge response and includes the MAC (message authentication code) generated using the vendor's private key. The MAC is generated using the standard algorithms for SHA1.

0618The GANC relays the random number and the generated MAC to the AAA via the S1 interface. The AAA retrieves the public key from the FAP database and computes its expected MAC. If the locally computed MAC is the same as that received over the network, then AAA has verified the FAP is genuine. If the MAC check in the AAA fails, the registration is rejected thus preventing access to services using the GANC. Note there is one private key for all FAP s from the same vendor so every FAP has the same image. The private key should never be stored in an unencrypted fashion. This detection method must be combined with the following method to protect the private keys from being extracted from the FAP.

0619b) Ensuring Unmodified FAPs

0620The FAP hardware may implement a “software authentication” technique to ensure only authentic, authorized software is allowed to execute on the FAP hardware. Some embodiments perform the following software authentication technique. The “bootloader” software, which is responsible for establishing the initial state of the system, so that the proper operating system and application can be loaded, will control the download and authorization of the software. The “bootloader” software must be implicitly trusted and therefore needs to be immutable. This requirement can be met, for example, by implementing the bootloader software in ROM or OTP flash.

0621The software loaded on the FAP is signed using the private key for each vendor. The bootloader software would be responsible for verification of this signature using the public key of the vendor. A failed signature check will prevent the “rogue” software from executing successfully. Note that the public key can be delivered to the bootloader software via signed certificates or it can be stored directly locally in the bootloader.

0622The above technique prevents the loading of software onto the FAP hardware by anyone except the vendor. Only the vendor possesses the private key necessary to sign the software and pass the “software authentication.”

06234. High Level Procedure

0624<figref idref="DRAWINGS">FIG. 51</figref> illustrates the high level procedure which can result in theft of service by a rogue FAP. The following description of the Femtocell service theft procedure assumes the following: (1) the Rogue FAP is a closed AP i.e. Femtocell service access is limited to a trusted list of UEs (in this example, only UE-<b>1</b> associated with identity IMSI-<b>1</b>/TMSI-<b>1</b> is allowed Femtocell service access using the Rogue FAP), (2) closed AP has implied security as part of mutual trust between FAP and the associated UEs. The close AP behavior is ensured by the network using service access control (SAC) at the time of UE registration, (3) victim UE is associated with identity IMSI-<b>2</b>/TMSI-<b>2</b> and is NOT allowed service on this Rogue FAP, and (4) the ‘Rogue’ FAP has been compromised and is attempting to steal services using victim UE identity outside the trust list. Although FIGS. <b>51</b> to <b>53</b> illustrate steps related to circuit switched resources (CSR), a person of ordinary skill in the art would be able to apply the same techniques to packet switched resources (PSR).

0625As shown in <figref idref="DRAWINGS">FIG. 51</figref>, the authorized UE <b>5110</b> establishes (in Step <b>1</b><i>a</i>) a RRC connection with the FAP <b>5115</b> on which it camps. The UE <b>5110</b> starts (in Step <b>1</b><i>b</i>) a Location Update procedure towards the CN <b>5130</b>. The FAP <b>5115</b> will intercept the Location Update request and attempts to register the UE <b>5110</b> with the associated Serving GANC <b>5120</b> over the existing IPSEC tunnel. The FAP <b>5115</b> may request (in Step <b>1</b><i>c</i>) and receive (in Step <b>1</b><i>d</i>) the IMSI of the UE <b>5110</b> if the Location Update is done using the TMSI, since the IMSI is required for the initial registration of the UE.

0626Next, the FAP <b>5115</b> attempts to register the UE <b>5110</b> on the GANC <b>5120</b> using the UE specific TCP connection by transmitting (in Step <b>2</b>) the GA-RC REGISTER REQUEST. The message includes: (1) Registration Type: Indicates that the registering device is a UE, (2) Generic IP access network attachment point information: AP-ID, (3) UE Identity: UE-IMSI, and (4) FAP identity: FAP-IMSI. The GANC <b>5120</b> will, via AAA server <b>5125</b>, authorize (in Steps <b>2</b><i>a</i>-<b>2</b><i>c</i>) the UE <b>5110</b> using the information provided in the REGISTER REQUEST. The authorization logic on the AAA server <b>5125</b> would also check to see if the UE <b>5110</b> is allowed Femtocell access using the specific FAP <b>5115</b>.

0627When the GANC <b>5115</b> accepts the registration attempt, the GANC responds (in Step <b>3</b>) with a GA-RC REGISTER ACCEPT. The FAP <b>5115</b> encapsulates (in Step <b>4</b>) the Location Update NAS PDU within a GA-CSR UL DIRECT TRANSFER message that is forwarded to the GANC <b>5120</b> via the existing TCP connection.

0628The GANC <b>5120</b> establishes a SCCP connection to the CN and forwards (in Step <b>5</b>) the Location Update request NAS PDU to the CN using the RANAP Initial UE Message. Subsequent NAS messages between the UE and core network will be sent between GANC and CN using the RANAP Direct Transfer message. The CN <b>5130</b> authenticates (in Step <b>6</b>) the UE <b>5110</b> using standard UTRAN authentication procedures. The CN <b>5130</b> also initiates (also in Step <b>6</b>) the standard Security Mode Control procedure as described in TS 33.102 standard, which results in distribution of the security keys {CK, IK} for the specific UE to the FAP via the GANC.

0629Next, the CN <b>5130</b> indicates (in Step <b>7</b>) that it has received the location update and it will accept the location update using the Location Update Accept message to the GANC <b>5120</b>. The GANC <b>5120</b> forwards this message to the FAP <b>5115</b> in the GA-CSR DL DIRECT TRANSFER. Next, the FAP relays (in Step <b>9</b>) the Location Update Accept over the air interface to the UE <b>5120</b>.

0630At this point, a session authorized for the specific UE-<b>1</b> using its credentials IMSI-<b>1</b> is established (in Step <b>10</b>) between the FAP <b>5115</b> and GANC <b>5120</b>. Next, a victim UE <b>5105</b>, in the vicinity of the rogue FAP <b>5115</b>, upon discovering the FAP <b>5115</b> over the air interface, will attempt to camp on the rogue FAP <b>5115</b> based on its internal cell selection logic. This will trigger the UE <b>5105</b> to establish (in Step <b>11</b><i>a</i>) an RRC connection with the Rogue FAP <b>5115</b>. The UE will then start (in Step <b>11</b><i>b</i>) a Location Update procedure towards the CN <b>5130</b>. The FAP <b>5115</b> will intercept the Location Update request. The FAP will then request (in Step <b>11</b><i>c</i>) and receive (in Step <b>11</b><i>d</i>) the IMSI of the victim UE <b>5105</b> if the Location Update is done using the TMSI.

0631The rogue FAP instead of attempting a registration of the victim UE <b>5105</b> with the GANC <b>5120</b>, will re-use the existing authorized session of UE-<b>1</b><b>5110</b> (as described in step <b>10</b>) to transfer messages to the CN <b>5130</b> via GANC <b>5120</b>. It is important to note that if the registration for the victim UE was attempted by the rogue FAP using the victim UE credentials (i.e. IMSI-<b>2</b>), the network based SAC would have rejected the registration request since the victim UE-<b>2</b><b>5105</b> is not authorized to use Femtocell service over the specific rogue FAP <b>5115</b>.

0632The FAP <b>5115</b> encapsulates the Location Update NAS PDU within a GA-CSR UL DIRECT TRANSFER message that is forwarded (in Step <b>13</b>) to the GANC <b>5120</b> via the existing TCP connection of UE-<b>1</b><b>5110</b>. The GANC <b>5120</b> establishes a SCCP connection to the CN <b>5130</b> and forwards (in Step <b>14</b>) the Location Update request NAS PDU to the CN <b>5130</b> using the RANAP Initial UE Message. Subsequent NAS messages between the UE <b>5105</b> and core network <b>5130</b> will be sent between GANC <b>5120</b> and CN <b>5130</b> using the RANAP Direct Transfer message.

0633Next, the CN <b>5130</b> authenticates (in Step <b>15</b>) the victim UE-<b>2</b> using standard UTRAN authentication procedures. The authentication messages are relayed transparently to the UE <b>5105</b> by the GANC <b>5120</b> and FAP <b>5115</b>. The CN <b>5130</b> also initiates (in Step <b>15</b>) the standard Security Mode Control procedure as described in TS 33.102 standard, which results in distribution of the security keys {CK, IK} for the victim UE to the FAP via the GANC.

0634Upon completion of the authentication, the CN <b>5130</b> indicates (in Step <b>16</b>) it has received the location update and it will accept the location update using the Location Update Accept message to the GANC <b>5120</b>. The GANC <b>5120</b> forwards (in Step <b>17</b>) this message to the FAP <b>5115</b> in the GA-CSR DL DIRECT TRANSFER. The FAP <b>5115</b> relays (in Step <b>17</b>) the Location Update Accept over the air interface to the victim UE.

0635The CN <b>5130</b> now thinks that the victim UE <b>5105</b> has been authenticated via the FAP <b>5115</b> and the GANC <b>5120</b> and will accept service requests from the victim UE <b>5105</b> without additional authentication for a specific time window. This time window, during which no addition authentication is performed for a given subscriber, is typically controlled by the CN <b>5130</b> based on specific implementation. The FAP <b>5115</b> takes advantage of this window and can now initiate service requests using the victim UE <b>5105</b> credentials and identity e.g. the FAP <b>5115</b> can now originate a Mobile Originated (MO) call using IMSI-<b>2</b> as the subscriber identity resulting in fraudulent charge to the victim UE's subscription. It is important to note that even if the CN <b>5130</b> decides to authenticate every service request from a given subscriber (such as MO), the FAP <b>5115</b> can relay the authentication messages to the victim UE <b>5105</b> and accomplish successful authentication to the CN <b>5130</b>.

0636H. Mechanisms for Preventing Service Theft in Femtocell

0637In this sub-section, a GANC is disclosed that protects the mobile network from the kind of man-in-the-middle theft scenario described above. The theft-of-service risk is different for different classes of UEs. For UEs that are affiliated with the FAP through a linked subscription account such as a family plan, the theft-of-service risk can be mitigated through the design of the plan pricing to remove any incentive to mislead the network. The FAP would only be stealing service from its own account.

0638For UEs that are not affiliated with the FAP, the theft of service potential is real because the rogue FAP now has an incentive to charge its usage to a victim UE account. The GANC has the responsibility to prevent non-affiliated UEs from being captured by the FAP. The GANC does this by restricting each FAP to serve a defined list of affiliated UEs. The disclosed GANC AAA-based service access controls provides the decision logic to enable this UE restriction. Every UE access is individually authorized through the AAA during the UE UMA registration. The AAA only authorizes UE access after validating that the UE and the FAP are affiliated and the UE access originated from the same IP address, through the same IPSec tunnel as the FAP. The GANC enforces the AAA authorization decision by accepting or denying the UMA registration request for the UE.

0639In addition, all subsequent communications from the UE are validated by the GANC to prevent rogue FAPs from attempting to insert control plane messages for the victim UE into previously authorized registration contexts. The GANC monitors the allocation of TMSI and P-TMSI to the UE so it can associate the UE with any of the UE's identities: IMSI, TMSI, and P-TMSI. This allows the GANC to enforce the UE-FAP affiliation on communication between the UE and the core network no matter whether the control plane messages are addressed with the UE IMSI, TMSI, or P-TMSI. The following two sub-sections describe the high level procedures with two different approaches which prevent attempted service theft by a rogue FAP

06401. Service Theft Prevention—Approach 1

0641<figref idref="DRAWINGS">FIG. 52</figref> illustrates the Femtocell service theft prevention approach of some embodiments. Steps <b>1</b>-<b>7</b> are the same as Step <b>1</b>-<b>7</b> described in relation with <figref idref="DRAWINGS">FIG. 51</figref> above. The GANC <b>5220</b> monitors (in Step <b>8</b>) allocation of new temporary identity to the UE <b>5210</b> by the CN <b>5230</b>, i.e. TMSI for CS services and P-TMSI for PS services, and creates an association between the TMSI or P-TMSI and session identity for the specific UE. The GANC will utilize this information to perform security checks on session identity for subsequent NAS layers messages originating on the UE specific session.

0642The GANC <b>5220</b> forwards (in Step <b>9</b>) the Location Update information received from the CN <b>5230</b> to the FAP <b>5215</b> using a GA-CSR DL DIRECT TRANSFER message. The FAP <b>5215</b> relays (In Step <b>10</b>) the Location Update Accept over the air interface to the UE <b>5210</b>.

0643At this point, a session authorized for the specific UE-<b>1</b> using its credentials IMSI-<b>1</b> is established (in Step <b>11</b>) between the FAP <b>5215</b> and GANC <b>5220</b>. Next, a victim UE <b>5205</b>, in the vicinity of the rogue FAP <b>5215</b>, upon discovering the FAP <b>5215</b> over the air interface, attempts to camp on the rogue FAP based on its internal cell selection logic. This will trigger the UE <b>5205</b> to establish (in Step <b>12</b><i>a</i>) a RRC connection with the Rogue FAP. The UE <b>5205</b> then starts (in Step <b>12</b><i>b</i>) a Location Update procedure towards the CN <b>5230</b>. The FAP <b>5215</b> intercepts the Location Update request. The FAP will then request (in Step <b>12</b><i>c</i>) and receives (in Step <b>12</b><i>d</i>) the IMSI of the victim UE <b>5205</b> if the Location Update is done using the TMSI.

0644The rogue FAP <b>5215</b> instead of attempting a registration of the victim UE <b>5205</b> with the GANC <b>5220</b>, re-uses (in Step <b>13</b>) the existing authorized session of UE-<b>1</b><b>5210</b> (as described in Step <b>11</b> above) to transfer messages to the CN <b>5230</b> via GANC <b>5220</b>. It is important to note that if the registration for the victim UE <b>5205</b> was attempted by the rogue FAP <b>5215</b> using the victim UE <b>5205</b> credentials (i.e. IMSI-<b>2</b>), the network based SAC would have rejected the registration request since the victim UE-<b>2</b><b>5205</b> is not authorized Femtocell service over the specific rogue FAP <b>5215</b>.

0645Next, the FAP <b>5215</b> encapsulates the Location Update NAS PDU within a GA-CSR UL DIRECT TRANSFER message that is forwarded (in Step <b>14</b>) to the GANC <b>5220</b> via the existing TCP connection of UE-<b>1</b><b>5210</b>. The GANC <b>5220</b> performs (in Step <b>15</b>) a security check on the session identity. Since the identity carried in the Location Update messages i.e. IMSI-<b>2</b> does not match any of the known identities for the session (IMSI-<b>1</b> which is the identity used for registration and authorization or the TMSI learnt by the GANC <b>5220</b> as described in Step <b>8</b> above), the GANC <b>5220</b> is able to detect the attempted service theft.

0646The GANC prevents the attempted service theft by deregistering the session for UE-<b>1</b><b>5210</b>. The GANC <b>5220</b> sends (in Step <b>16</b>) a deregistration message to the FAP <b>5215</b> on the specific session (the authorized session for UE-<b>1</b>) on which the service theft was being attempted.

06472. Service Theft Prevention—Approach 2

0648<figref idref="DRAWINGS">FIG. 53</figref> illustrates the Femtocell service theft prevention in some embodiments.

0649Steps <b>1</b>-<b>15</b> are the same as Step <b>1</b>-<b>15</b> described in relation with <figref idref="DRAWINGS">FIG. 52</figref> above. Since the identity carried in the NAS PDU does not match any of the known identities for that session, GANC <b>5320</b> replaces the identity in the Location Update message with the original authorized identity for the specific session i.e., IMSI-<b>2</b> is replace with IMSI-<b>1</b> in the NAS PDU. The GANC establishes a SCCP connection to the CN <b>5330</b> and forwards (in Step <b>16</b>) the modified Location Update request NAS PDU to the CN <b>5330</b> using the RANAP Initial UE message. The CN <b>5330</b> receives a service request with UE-<b>1</b>'s identity in the request and will associate the request with UE-<b>1</b><b>5310</b> subscriber data including billing, etc.

XIII. FEMTOCELL SERVICE ACCESS CONTROL

0650Femtocell service access control (SAC) and accounting services are based on the S1 interface between the INC and one or more AAA servers. The S1 interface functions are defined in detail in the above mentioned U.S. application Ser. No. 11/349,025.

0651The objective of Femtocell service access control is to provide operators with the tools to properly implement their Femtocell service plans based on real-time information from the subscriber and non real-time information provisioned within the operator's IT systems and service databases. Using service policies, the operator can implement a range of creative services and controls to be applied on a per individual subscriber basis, which results in the acceptance or rejection of any discrete Femtocell session registration request. Primarily, service policies are used to identify whether a subscriber's current request for access meets the conditions of the service plan to which they are subscribed.

0652In some embodiments, Femtocell SAC encompasses the discovery, registration and redirection functions as well as enhanced service access control functions, such as restricting Femtocell service access based on the reported FAP MAC address or neighboring macro network UMTS cell information.

0653A local SAC may be performed by the FAP for performance reasons (example: FAP may use local SAC for faster rejection of UEs which are not allowed access to either Femtocell services or not allowed access to Femtocell services via the specific FAP).

0654Key elements of the service access control design approach are as follows: <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0655"> 1) There are two service access control configuration options: <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0656"> a) Basic service access control: The S1 (INC-AAA) interface is not deployed and a limited set of service access control capabilities is provided by the INC. <ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0657"> i) The INC is responsible for the Femtocell discovery, registration and redirection functions. </li><li id="ul0008-0002" num="0658"> ii) The UMTS-to-Femtocell mapping logic and data is in the INC; i.e., this is used to support the discovery, registration and redirection functions and to assign service areas to specific FAPS. </li><li id="ul0008-0003" num="0659"> iii) There is no subscriber or FAP-specific service access control. </li></ul></li><li id="ul0007-0002" num="0660"> b) Enhanced service access control: The S1 interface is deployed and the AAA provides expanded service access control features, including custom features per service provider requirements. <ul id="ul0009" list-style="none"><li id="ul0009-0001" num="0661"> i) The UMA discovery, registration and redirection functions remain on the INC. </li><li id="ul0009-0002" num="0662"> ii) The UMTS-to-Femtocell mapping logic and data remains in the INC. </li><li id="ul0009-0003" num="0663"> iii) The AAA supports interfaces to external database servers; e.g., via LDAPv3. </li></ul></li><li id="ul0007-0003" num="0664"> iv) The details of these enhanced service access control functions are defined in the above mentioned U.S. application Ser. No. 11/349,025. </li></ul></li><li id="ul0006-0002" num="0665"> 2) Enablement of the enhanced service access control support functions (i.e., the service access control functions of the S1 interface) is an INC configuration option; if enabled, the INC forwards attributes received in the discovery and registration requests to the AAA using RADIUS. This allows the AAA to (for example): <ul id="ul0010" list-style="none"><li id="ul0010-0001" num="0666"> a) Determine when UE registration attempts should be allowed or rejected (e.g., limiting service to a single FAP) </li><li id="ul0010-0002" num="0667"> b) Retrieve FAP location information from an external database and send the information to the INC. </li><li id="ul0010-0003" num="0668"> c) Provide a billing rate indicator to the INC that is incorporated in the UMTS-to-Femtocell SAI mapping process. </li><li id="ul0010-0004" num="0669"> d) Indicate that hand-in, hand-out, or both are enabled or disabled for the subscriber. </li></ul></li></ul></li></ul>

0670A. UMTS-to-Femtocell Mapping

0671The UMTS-to-Femtocell mapping processes include the following: <ul id="ul0011" list-style="none"><li id="ul0011-0001" num="0000"><ul id="ul0012" list-style="none"><li id="ul0012-0001" num="0672"> 1) UMTS-INC Mapping (or “INC Selection”) serves the following functions: <ul id="ul0013" list-style="none"><li id="ul0013-0001" num="0673"> a) It allows an INC functioning as a “provisioning INC” to direct a mobile station to its designated “default INC”. </li><li id="ul0013-0002" num="0674"> b) It allows an INC functioning as a “default INC” to direct a mobile station to an appropriate “serving INC” (e.g., in case the FAP is outside its normal default INC coverage area). </li><li id="ul0013-0003" num="0675"> c) It allows the INC to determine if the UMTS coverage area is Femtocell-restricted and, if so, to deny service. </li></ul></li><li id="ul0012-0002" num="0676"> 2) UMTS-Femtocell Service Area Mapping (or “Femtocell Service Area Selection”) serves the following functions: <ul id="ul0014" list-style="none"><li id="ul0014-0001" num="0677"> a) It allows an INC functioning as a “default or serving INC” to assign the Femtocell service area that shall be associated with the FAP registration (and all the UEs camped on that specific FAP). The service area can then be utilized for emergency call routing as described in the “Service area based routing” Subsection under the “EMERGENCY SERVICES” Section, above. </li></ul></li></ul></li></ul>

0678B. Service Access Control (SAC) Examples

0679The following example service access control are described in this section: (1) new FAP connects to GAN Femtocell network, (2) FAP connects to GAN Femtocell network (redirected connection), (3) FAP attempts to connect in a restricted UMTS coverage area, (4) authorized UE roves into an authorized FAP for Femtocell service, and (5) unauthorized UE roves into an authorized FAP for Femtocell service.

06801. New FAP Connects to GAN Femtocell Network

0681<figref idref="DRAWINGS">FIG. 54</figref> illustrates SAC for new FAP connecting to Femtocell network in some embodiments. As shown, if the FAP <b>5405</b> has a provisioned or derived FQDN of the Provisioning SeGW, it performs (in Step <b>1</b>) a DNS query (via the generic IP access network interface) to resolve the FQDN to an IP address. If the FAP has a provisioned IP address for the Provisioning SeGW, the DNS step is omitted.

0682The DNS Server <b>5410</b> returns (in Step <b>2</b>) a response including the IP Address of the Provisioning SeGW <b>5415</b>. The FAP <b>5405</b> establishes (in Step <b>15</b>) a secure tunnel to the Provisioning SeGW <b>5415</b> using IKEv2 and EAP-AKA or EAP-SIM.

0683If the FAP has a provisioned or derived FQDN of the Provisioning INC, it performs (in Step <b>4</b>) a DNS query (via the secure tunnel) to resolve the FQDN to an IP address. If the FAP has a provisioned IP address for the Provisioning INC, the DNS step (step <b>4</b>) will be omitted. The DNS Server <b>5420</b> returns (in Step <b>5</b>) a response including the IP Address of the Provisioning INC.

0684Next, the FAP <b>5405</b> sets up (in Step <b>6</b>) a TCP connection to a well-defined port on the Provisioning INC <b>5425</b>. The FAP <b>5405</b> then queries (in Step <b>7</b>) the Provisioning INC for the Default INC, using GA-RC DISCOVERY REQUEST. The message includes Cell Info and FAP Identity. For Cell Info, if the FAP detects macro network coverage, then it provides the detected UTRAN cell ID and the UTRAN LAI. If the FAP does not detect macro network coverage it provides the last LAI where the FAP successfully registered, along with an indicator stating which one it is. For FAP Identity, the message includes IMSI.

0685The INC <b>5425</b> sends (in Step <b>8</b>) a RADIUS Access-Request message to the AAA server <b>5435</b>, including attributes derived from GA-CSR DISCOVERY REQUEST message. The AAA server <b>5435</b> queries (in Step <b>9</b>) the Femtocell subscriber database <b>5440</b> for a record matching the IMSI of the FAP. The subscriber record is returned (in Step <b>9</b>) to the AAA server. The AAA server verifies that FAP IMSI is authorized and FAP is allowed (based on AP-ID i.e., MAC address of the FAP).

0686AAA server returns (in Step <b>10</b>) selected Femtocell location information based on AP-ID and IMSI to the INC <b>5425</b> using the Access Accept message. The INC <b>5425</b> determines (in Step <b>11</b>) the default security gateway and INC (e.g., INC #<b>2</b><b>5430</b>) using the UMTS-Femtocell mapping function (see UMTS-to-Femtocell Mapping Section, above). This is done so the FAP <b>5405</b> is directed to a “local” Default INC in the HPLMN to optimize network performance.

0687The Provisioning INC <b>5425</b> returns (in Step <b>12</b>) the default INC information in the GA-RC DISCOVERY ACCEPT message. The DISCOVERY ACCEPT message also indicates whether the INC and SeGW address provided shall or shall not be stored by the FAP. The FAP releases (in Step <b>13</b>) the TCP connection and IPSec tunnel and proceeds to register on INC #<b>2</b>.

0688The FAP performs (in Step <b>14</b>) a private DNS query using the assigned Default INC FQDN. The private DNS server <b>5420</b> returns (in Step <b>15</b>) the IP address of INC #<b>2</b><b>5430</b>. The FAP establishes (in Step <b>16</b>) a TCP connection to INC #<b>2</b><b>5430</b>. The FAP sends (in Step <b>17</b>) a GA-RC REGISTER REQUEST message to the INC.

0689The INC sends (in Step <b>18</b>) a RADIUS Access-Request message to the AAA server, including attributes derived from GA-RC REGISTER REQUEST message. The AAA server queries (in Step <b>19</b>) the Femtocell subscriber database for a record matching the FAP IMSI. The subscriber record is returned (in Step <b>19</b>) to the AAA server. The AAA server verifies that IMSI is authorized and FAP is allowed (based on AP-ID).

0690Next, the AAA server returns (in Step <b>20</b>) selected Femtocell service attributes to the INC. The INC determines (in Step <b>21</b>) that it is the correct serving INC for the mobile current location using the UMTS-Femtocell mapping function. It also determines (in Step <b>21</b>) the Femtocell service area to associate with the FAP using the UMTS-Femtocell mapping functions. The INC returns (in Step <b>22</b>) a GA-RC REGISTER ACCEPT message to the MS

06912. FAP Connects to GAN Femtocell Network (Redirected Connection)

0692<figref idref="DRAWINGS">FIG. 55</figref> illustrates SAC for the FAP getting redirected in Femtocell network in some embodiments. Steps <b>1</b> to <b>10</b> are the same steps as described in the “New FAP connects to GAN Femtocell network” Subsection, above. Next, the INC <b>5525</b> uses the UMTS-Femtocell mapping function to determine (in Step <b>11</b>) that the FAP <b>5505</b> should be served by another INC.

0693The INC <b>5525</b> sends (in Step <b>12</b>) the new serving SeGW and INC FQDNs to the FAP <b>5505</b> in the GA-RC REGISTER REDIRECT message. The FAP releases (In Step <b>13</b>) the TCP connection and IPSec tunnel and proceeds to register with the designated INC.

06943. FAP Attempts to Connect in a Restricted UMTS Coverage Area

0695<figref idref="DRAWINGS">FIG. 56</figref> illustrates the SAC for FAP registering in restricted UMTS coverage area in some embodiments. As shown, Steps <b>1</b> to <b>10</b> are the same steps as described in the “New FAP connects to GAN Femtocell network” Subsection, above. Next, the INC <b>5625</b> uses the UMTS-Femtocell mapping function to determine (in Step <b>11</b>) that the FAP <b>5605</b> is in an UMTS area that is Femtocell restricted (i.e., Femtocell access is not allowed in the area).

0696The INC sends (in Step <b>12</b>) a GA-RC REGISTER REJECT message to the FAP, including reject cause “Location not allowed”. The FAP releases (in Step <b>13</b>) the TCP connection and IPSec tunnel and does not attempt to register again from the same UMTS coverage area until powered-off.

06974. Authorized UE Roves into an Authorized FAP for Femtocell Service

0698The sequence of events is same as described in UE Registration Section, above.

06995. Unauthorized UE Roves into an Authorized FAP for Femtocell Service

0700An unauthorized UE (unauthorized for Femtocell service over the specific FAP), upon camping on the FAP (via its internal cell selection mechanism), will initiate a NAS layer Location Update procedure towards the CN via the FAP (The LU is triggered since the FAP broadcasts a distinct LAI than its neighboring macro cells and other neighboring Femtocells). The FAP will intercept the Location Update message and attempt to register the UE with the INC as described below. <figref idref="DRAWINGS">FIG. 57</figref> illustrates the SAC for Unauthorized UE accessing authorized FAP in some embodiments.

0701As shown, the UE <b>5705</b> establishes (in Step <b>1</b><i>a</i>) a RRC connection with the FAP on which it camps. The UE starts (in Step <b>1</b><i>b</i>) a Location Update procedure towards the CN. The FAP <b>5710</b> will intercept the Location Update request and attempts to register the UE with the associated Serving INC over the existing IPSec tunnel. Optionally, the FAP may request (in Step <b>1</b><i>c</i>) the IMSI of the UE if the Location Update is done using the TMSI, since the initial registration for the UE must be done using the permanent identity i.e. the IMSI of the UE.

0702The FAP sets up a separate TCP connection (for each UE) to a destination TCP port on the INC <b>5715</b>. The INC destination TCP port is the same as that used for FAP registration. The FAP attempts to register the UE on the INC by transmitting (in Step <b>2</b>) the GA-RC REGISTER REQUEST. The message includes (1) Registration Type which indicates that the registering device is a UE, (2) the UE Identity which is UE-IMSI, and (3) the FAP identity which is FAP-IMSI.

0703Optionally, if the INC has been configured for Service Access Control (SAC) over S1 interface, the INC will (in Step <b>3</b>), via AAA server <b>5420</b>, authorize the UE <b>5405</b> using the information provided in the REGISTER REQUEST. The authorization logic on the AAA server also checks (in Step <b>4</b>) to see if the UE is allowed Femtocell access using the specific FAP. The AAA SAC logic indicates that the registering UE is not authorized to access Femtocell service over the specific FAP.

0704Next, the AAA <b>5720</b> sends (in Step <b>5</b>) Access Reject (with reject cause equivalent to “UE not allowed on FAP”) to the INC <b>5715</b>. The INC maps (in Step <b>6</b>) the Access Reject to a GA-RC REGISTER REJECT message to the FAP indicating the reject cause.

0705The FAP <b>5710</b> in turn sends (in Step <b>7</b>) a Location Updating Reject to the UE <b>5705</b> with cause of “Location Area Not Allowed”. This will prevent the UE from attempting to camp on the specific FAP again. While some embodiments use “Location Area Not Allowed” as a mechanism for rejecting unauthorized UEs, other embodiments may use other appropriate UE rejection mechanisms.

XIV. COMPUTER SYSTEM

0706<figref idref="DRAWINGS">FIG. 58</figref> conceptually illustrates a computer system with which some embodiments of the invention are implemented. The computer system <b>5800</b> includes a bus <b>5805</b>, a processor <b>5810</b>, a system memory <b>5815</b>, a read-only memory <b>5820</b>, a permanent storage device <b>5825</b>, input devices <b>5830</b>, and output devices <b>5835</b>.

0707The bus <b>5805</b> collectively represents all system, peripheral, and chipset buses that support communication among internal devices of the computer system <b>5800</b>. For instance, the bus <b>5805</b> communicatively connects the processor <b>5810</b> with the read-only memory <b>5820</b>, the system memory <b>5815</b>, and the permanent storage device <b>5825</b>.

0708From these various memory units, the processor <b>5810</b> retrieves instructions to execute and data to process in order to execute the processes of the invention. In some embodiments the processor comprises a Field Programmable Gate Array (FPGA), an ASIC, or various other electronic components for executing instructions. The read-only-memory (ROM) <b>5820</b> stores static data and instructions that are needed by the processor <b>5810</b> and other modules of the computer system. The permanent storage device <b>5825</b>, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instruction and data even when the computer system <b>5800</b> is off. Some embodiments of the invention use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device <b>5825</b>. Some embodiments use one or more removable storage devices (flash memory card or memory stick) as the permanent storage device.

0709Like the permanent storage device <b>5825</b>, the system memory <b>5815</b> is a read-and-write memory device. However, unlike storage device <b>5825</b>, the system memory is a volatile read-and-write memory, such as a random access memory. The system memory stores some of the instructions and data that the processor needs at runtime.

0710Instructions and/or data needed to perform processes of some embodiments are stored in the system memory <b>5815</b>, the permanent storage device <b>5825</b>, the read-only memory <b>5820</b>, or any combination of the three. For example, the various memory units include instructions for processing multimedia items in accordance with some embodiments. From these various memory units, the processor <b>5810</b> retrieves instructions to execute and data to process in order to execute the processes of some embodiments.

0711The bus <b>5805</b> also connects to the input and output devices <b>5830</b> and <b>5835</b>. The input devices enable the user to communicate information and select commands to the computer system. The input devices <b>5830</b> include alphanumeric keyboards and cursor-controllers. The output devices <b>5835</b> display images generated by the computer system. The output devices include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Finally, as shown in <figref idref="DRAWINGS">FIG. 58</figref>, bus <b>5805</b> also couples computer <b>5800</b> to a network <b>5865</b> through a network adapter (not shown). In this manner, the computer can be a part of a network of computers (such as a local area network (“LAN”), a wide area network (“WAN”), or an Intranet) or a network of networks (such as the Internet).

0712It should be recognized by one of ordinary skill in the art that any or all of the components of computer system <b>5800</b> may be used in conjunction with the invention. For instance, some or all components of the computer system described with regards to <figref idref="DRAWINGS">FIG. 58</figref> comprise some embodiments of the UE, FAP, GANC, and GGSN described above. Moreover, one of ordinary skill in the art will appreciate that any other system configuration may also be used in conjunction with the invention or components of the invention.

XV. DEFINITIONS AND ABBREVIATIONS

0713The following is a list of definitions and abbreviations used: <ul id="ul0015" list-style="none"><li id="ul0015-0001" num="0714"> AAA Authentication, Authorization, and Accounting </li><li id="ul0015-0002" num="0715"> ACL Access Control List </li><li id="ul0015-0003" num="0716"> AES Advanced Encryption Standard </li><li id="ul0015-0004" num="0717"> AH Authentication Header (IPSec) </li><li id="ul0015-0005" num="0718"> AKA Authentication and Key Agreement </li><li id="ul0015-0006" num="0719"> ALI Automatic Location Identification </li><li id="ul0015-0007" num="0720"> AMS access Point Management System </li><li id="ul0015-0008" num="0721"> ANI Automatic Number Identification </li><li id="ul0015-0009" num="0722"> AP Access Point </li><li id="ul0015-0010" num="0723"> APN Access Point Name </li><li id="ul0015-0011" num="0724"> ATM Asynchronous Transfer Mode </li><li id="ul0015-0012" num="0725"> AuC Authentication Center </li><li id="ul0015-0013" num="0726"> CBC Cell Broadcast Center </li><li id="ul0015-0014" num="0727"> CBC Cipher Block Chaining </li><li id="ul0015-0015" num="0728"> CC Call Control </li><li id="ul0015-0016" num="0729"> CDR Call Detail Records </li><li id="ul0015-0017" num="0730"> CMDA Code Division Multiple Access </li><li id="ul0015-0018" num="0731"> CGI Cell Global Identification </li><li id="ul0015-0019" num="0732"> CgPN Calling Party Number </li><li id="ul0015-0020" num="0733"> CLIP Calling Line Presentation </li><li id="ul0015-0021" num="0734"> CK Cipher Key </li><li id="ul0015-0022" num="0735"> CM Connection Management </li><li id="ul0015-0023" num="0736"> CM-sub Connection Management sublayer </li><li id="ul0015-0024" num="0737"> CN Core Network </li><li id="ul0015-0025" num="0738"> CPE Customer Premises Equipment </li><li id="ul0015-0026" num="0739"> CRC Cyclic Redundancy Code </li><li id="ul0015-0027" num="0740"> CRDB Coordinate Routing Database </li><li id="ul0015-0028" num="0741"> CS Circuit Switched </li><li id="ul0015-0029" num="0742"> CTM Cellular Text telephone Modem, as specified in 3GPP 26.226 </li><li id="ul0015-0030" num="0743"> DL Downlink </li><li id="ul0015-0031" num="0744"> DNS Domain Name System </li><li id="ul0015-0032" num="0745"> EAP Extensible Authentication protocol </li><li id="ul0015-0033" num="0746"> EAPOL EAP over LANs </li><li id="ul0015-0034" num="0747"> ECB Electronic Code Book (AES Mode) </li><li id="ul0015-0035" num="0748"> ELID Emergency Location Information Delivery </li><li id="ul0015-0036" num="0749"> E-OTD Enhanced Observed Time Difference </li><li id="ul0015-0037" num="0750"> ESN Emergency Services Number </li><li id="ul0015-0038" num="0751"> ESP Emergency Services Protocol or Encapsulating Security Payload (IPSec) </li><li id="ul0015-0039" num="0752"> ESRD Emergency Services Routing Digits </li><li id="ul0015-0040" num="0753"> ESRK Emergency Services Routing Key </li><li id="ul0015-0041" num="0754"> ETSI European Telecommunications Standards Institute </li><li id="ul0015-0042" num="0755"> FCAPS Fault, Configuration, Accounting, Performance, and Security management </li><li id="ul0015-0043" num="0756"> FAP Femtocell Access Point </li><li id="ul0015-0044" num="0757"> FCC US Federal Communications Commission </li><li id="ul0015-0045" num="0758"> FQDN Fully Qualified Domain Name </li><li id="ul0015-0046" num="0759"> GA-CSR Generic Access—Circuit Switched Resources </li><li id="ul0015-0047" num="0760"> GAN Generic Access Network </li><li id="ul0015-0048" num="0761"> GANC GAN Network Controller </li><li id="ul0015-0049" num="0762"> GA-PSR Generic Access—Packet Switched Resources </li><li id="ul0015-0050" num="0763"> GA-RC Generic Access—Resource Control </li><li id="ul0015-0051" num="0764"> GDP Generic Digits Parameter </li><li id="ul0015-0052" num="0765"> GERAN GSM EDGE Radio Access Network </li><li id="ul0015-0053" num="0766"> GGSN Gateway GPRS Support Node </li><li id="ul0015-0054" num="0767"> GMLC Gateway Mobile Location Center </li><li id="ul0015-0055" num="0768"> GMM/SM GPRS Mobility Management and Session Management </li><li id="ul0015-0056" num="0769"> GMSC Gateway MSC </li><li id="ul0015-0057" num="0770"> GPRS General Packet Radio Service </li><li id="ul0015-0058" num="0771"> GPS Global Positioning System </li><li id="ul0015-0059" num="0772"> GMM-sub GPRS Mobility Management sublayer </li><li id="ul0015-0060" num="0773"> GRR-sub GPRS Radio Resource sublayer in GSM </li><li id="ul0015-0061" num="0774"> GSM Global System for Mobile communications </li><li id="ul0015-0062" num="0775"> GSN GPRS Support Node </li><li id="ul0015-0063" num="0776"> GTP GPRS Tunnelling Protocol </li><li id="ul0015-0064" num="0777"> GTT GSM Global Text Telephony or SS7 Global Title Translation </li><li id="ul0015-0065" num="0778"> HLR Home Location Register </li><li id="ul0015-0066" num="0779"> HMAC Hashed Message Authentication Code </li><li id="ul0015-0067" num="0780"> HPLMN Home PLMN </li><li id="ul0015-0068" num="0781"> IAM Initial Address Message </li><li id="ul0015-0069" num="0782"> ICMP Internet Control Message Protocol </li><li id="ul0015-0070" num="0783"> IETF Internet Engineering Task Force </li><li id="ul0015-0071" num="0784"> IK Integrity Key </li><li id="ul0015-0072" num="0785"> IKEv2 Internet Key Exchange Version 2 </li><li id="ul0015-0073" num="0786"> IMEI International Mobile station Equipment Identity </li><li id="ul0015-0074" num="0787"> IMSI International Mobile Subscriber Identity </li><li id="ul0015-0075" num="0788"> INC IP Network Controller </li><li id="ul0015-0076" num="0789"> IP Internet Protocol </li><li id="ul0015-0077" num="0790"> IPSec IP Security </li><li id="ul0015-0078" num="0791"> IPv4 Internet Protocol version 4 </li><li id="ul0015-0079" num="0792"> IPv6 Internet Protocol version 6 </li><li id="ul0015-0080" num="0793"> ISDN Integrated Services Digital Network </li><li id="ul0015-0081" num="0794"> ISP Internet Service Provider </li><li id="ul0015-0082" num="0795"> ISUP ISDN User Part </li><li id="ul0015-0083" num="0796"> Iu Interface UTRAN </li><li id="ul0015-0084" num="0797"> IV Initialization Vector </li><li id="ul0015-0085" num="0798"> LA Location Area </li><li id="ul0015-0086" num="0799"> LAC Location Area Code </li><li id="ul0015-0087" num="0800"> LAI Location Area Identity </li><li id="ul0015-0088" num="0801"> LAU Location Area Update </li><li id="ul0015-0089" num="0802"> LU Location Update </li><li id="ul0015-0090" num="0803"> LCS Location Service </li><li id="ul0015-0091" num="0804"> LEAP Lightweight EAP (same as EAP-Cisco) </li><li id="ul0015-0092" num="0805"> LLC Logical Link Control </li><li id="ul0015-0093" num="0806"> LLC-sub Logical Link Control sublayer </li><li id="ul0015-0094" num="0807"> LMSI Local Mobile Subscriber Identity </li><li id="ul0015-0095" num="0808"> LSB Least Significant Bit </li><li id="ul0015-0096" num="0809"> LSP Location Services Protocol </li><li id="ul0015-0097" num="0810"> M Mandatory </li><li id="ul0015-0098" num="0811"> M3UA MTP3 User Adaptation Layer </li><li id="ul0015-0099" num="0812"> MAC Media Access Control or Message Authentication Code (same as MIC) </li><li id="ul0015-0100" num="0813"> MAC Address Media Access Control Address </li><li id="ul0015-0101" num="0814"> MAC-I Message Authentication Code for Integrity </li><li id="ul0015-0102" num="0815"> MAP Mobile Application Part </li><li id="ul0015-0103" num="0816"> MDN Mobile Directory Number </li><li id="ul0015-0104" num="0817"> ME Mobile Equipment </li><li id="ul0015-0105" num="0818"> MIC Message Integrity Check (same as Message Authentication Code) </li><li id="ul0015-0106" num="0819"> MG or MGW Media Gateway </li><li id="ul0015-0107" num="0820"> MM Mobility Management </li><li id="ul0015-0108" num="0821"> MM-sub Mobility Management sublayer </li><li id="ul0015-0109" num="0822"> MPC Mobile Positioning Center </li><li id="ul0015-0110" num="0823"> MS Mobile Station </li><li id="ul0015-0111" num="0824"> MSB Most Significant Bit </li><li id="ul0015-0112" num="0825"> MSC Mobile Switching Center </li><li id="ul0015-0113" num="0826"> MSISDN Mobile Station International ISDN Number </li><li id="ul0015-0114" num="0827"> MSRN Mobile Station Roaming Number </li><li id="ul0015-0115" num="0828"> MTP1/2/3 Message Transfer Part Layer 1/2/3 </li><li id="ul0015-0116" num="0829"> NAS Non Access Stratum </li><li id="ul0015-0117" num="0830"> NCAS Non Call Associated Signaling </li><li id="ul0015-0118" num="0831"> NDC National Destination Code </li><li id="ul0015-0119" num="0832"> NS Network Service </li><li id="ul0015-0120" num="0833"> NSAPI Network layer Service Indoor Base Station Identifier </li><li id="ul0015-0121" num="0834"> NSS Network SubSystem </li><li id="ul0015-0122" num="0835"> O Optional </li><li id="ul0015-0123" num="0836"> OCB Offset Code Book (AES Mode) </li><li id="ul0015-0124" num="0837"> OTP One Time Programmable </li><li id="ul0015-0125" num="0838"> pANI pseudo-ANI: Either the ESRD or ESRK </li><li id="ul0015-0126" num="0839"> PCS Personal Communications Services </li><li id="ul0015-0127" num="0840"> PCU Packet Control Unit </li><li id="ul0015-0128" num="0841"> PDCH Packet Data CHannel </li><li id="ul0015-0129" num="0842"> PDE Position Determining Entity </li><li id="ul0015-0130" num="0843"> PDN Packet Data Network </li><li id="ul0015-0131" num="0844"> PDP Packet Data Protocol, e.g., IP or X.25 </li><li id="ul0015-0132" num="0845"> PDU Protocol Data Unit </li><li id="ul0015-0133" num="0846"> PEAP Protected EAP </li><li id="ul0015-0134" num="0847"> PKI Public Key Infrastructure </li><li id="ul0015-0135" num="0848"> PLMN Public Land Mobile Network </li><li id="ul0015-0136" num="0849"> POI Point of Interface </li><li id="ul0015-0137" num="0850"> PPF Paging Proceed Flag </li><li id="ul0015-0138" num="0851"> PPP Point-to-Point Protocol </li><li id="ul0015-0139" num="0852"> PSAP Public Safety Answering Point </li><li id="ul0015-0140" num="0853"> PSTN Public Switched Telephone Network </li><li id="ul0015-0141" num="0854"> PTM Point To Multipoint </li><li id="ul0015-0142" num="0855"> P-TMSI Packet TMSI </li><li id="ul0015-0143" num="0856"> PTP Point To Point </li><li id="ul0015-0144" num="0857"> PVC Permanent Virtual Circuit </li><li id="ul0015-0145" num="0858"> QoS Quality of Service </li><li id="ul0015-0146" num="0859"> R Required </li><li id="ul0015-0147" num="0860"> RA Routing Area </li><li id="ul0015-0148" num="0861"> RAB RANAP Assignment Request </li><li id="ul0015-0149" num="0862"> RAC Routing Area Code </li><li id="ul0015-0150" num="0863"> RADIUS Remote Authentication Dial-In User Service </li><li id="ul0015-0151" num="0864"> RAI Routing Area Identity </li><li id="ul0015-0152" num="0865"> RAN Radio Access Network </li><li id="ul0015-0153" num="0866"> RANAP Radio Access Network Application Part </li><li id="ul0015-0154" num="0867"> RFC Request for Comment (IETF Standard) </li><li id="ul0015-0155" num="0868"> RLC Radio Link Control </li><li id="ul0015-0156" num="0869"> RNC Radio Network Controller </li><li id="ul0015-0157" num="0870"> RR-sub Radio Resource Management sublayer </li><li id="ul0015-0158" num="0871"> RSN Robust Security Network </li><li id="ul0015-0159" num="0872"> RTCP Real Time Control Protocol </li><li id="ul0015-0160" num="0873"> RTP Real Time Protocol </li><li id="ul0015-0161" num="0874"> SAC Service Access Control </li><li id="ul0015-0162" num="0875"> SAC Service Area Code SC Scrambling Code </li><li id="ul0015-0163" num="0876"> SCCP Signaling Connection Control Part </li><li id="ul0015-0164" num="0877"> SDCCH Standalone Dedicated Control Channel </li><li id="ul0015-0165" num="0878"> SDU Service Data Unit </li><li id="ul0015-0166" num="0879"> SeGW GANC Security Gateway </li><li id="ul0015-0167" num="0880"> SGSN Serving GPRS Support Node </li><li id="ul0015-0168" num="0881"> SK Service Key </li><li id="ul0015-0169" num="0882"> SIM Subscriber Identity Module </li><li id="ul0015-0170" num="0883"> SM Session Management </li><li id="ul0015-0171" num="0884"> SMLC Serving Mobile Location Center </li><li id="ul0015-0172" num="0885"> SMS Short Message Service </li><li id="ul0015-0173" num="0886"> SM-AL Short Message Application Layer </li><li id="ul0015-0174" num="0887"> SM-TL Short Message Transfer Layer </li><li id="ul0015-0175" num="0888"> SM-RL Short Message Relay Layer </li><li id="ul0015-0176" num="0889"> SM-RP Short Message Relay Protocol </li><li id="ul0015-0177" num="0890"> SMR Short Message Relay (entity) </li><li id="ul0015-0178" num="0891"> SM-CP Short Message Control Protocol </li><li id="ul0015-0179" num="0892"> SMC Short Message Control (entity) </li><li id="ul0015-0180" num="0893"> SM-SC Short Message Service Centre </li><li id="ul0015-0181" num="0894"> SMS-GMSC Short Message Service Gateway MSC </li><li id="ul0015-0182" num="0895"> SMS-IWMSC Short Message Service Interworking MSC </li><li id="ul0015-0183" num="0896"> SNDCP SubNetwork Dependent Convergence Protocol </li><li id="ul0015-0184" num="0897"> SN-PDU SNDCP PDU </li><li id="ul0015-0185" num="0898"> S/R Selective Router </li><li id="ul0015-0186" num="0899"> SS Supplementary Service </li><li id="ul0015-0187" num="0900"> SSID Service Set Identifier (also known as “Network Name”) </li><li id="ul0015-0188" num="0901"> SSL Secure Socket Layer </li><li id="ul0015-0189" num="0902"> STA Station (802.11 client) </li><li id="ul0015-0190" num="0903"> TA Timing Advance </li><li id="ul0015-0191" num="0904"> TCAP Transaction Capabilities Application Part </li><li id="ul0015-0192" num="0905"> TCP Transmission Control Protocol </li><li id="ul0015-0193" num="0906"> TDOA Time Difference of Arrival </li><li id="ul0015-0194" num="0907"> TEID Terminal Endpoint Identifier </li><li id="ul0015-0195" num="0908"> TID Tunnel Identifier </li><li id="ul0015-0196" num="0909"> TKIP Temporal Key Integrity Protocol </li><li id="ul0015-0197" num="0910"> TLLI Temporary Logical Link Identity </li><li id="ul0015-0198" num="0911"> TLS Transport Layer Security </li><li id="ul0015-0199" num="0912"> TMSI Temporary Mobile Subscriber Identity </li><li id="ul0015-0200" num="0913"> TOA Time of Arrival </li><li id="ul0015-0201" num="0914"> TRAU Transcoder and Rate Adaptation Unit </li><li id="ul0015-0202" num="0915"> TTY Text telephone or teletypewriter </li><li id="ul0015-0203" num="0916"> UARFCN UMTS Absolute Radio Frequency Channel Number </li><li id="ul0015-0204" num="0917"> UDP User Datagram Protocol </li><li id="ul0015-0205" num="0918"> UE User Equipment </li><li id="ul0015-0206" num="0919"> UL Uplink </li><li id="ul0015-0207" num="0920"> UMA Unlicensed Mobile Access </li><li id="ul0015-0208" num="0921"> UMTS Universal Mobile Telecommunication System </li><li id="ul0015-0209" num="0922"> USIM UMTS Subscriber Identity Module/Universal Subscriber Identity Module </li><li id="ul0015-0210" num="0923"> USSD Unstructured Supplementary Service Data </li><li id="ul0015-0211" num="0924"> UTC Coordinated Universal Time </li><li id="ul0015-0212" num="0925"> UTRAN UMTS Terrestrial Radio Access Network </li><li id="ul0015-0213" num="0926"> VLR Visited Location Register </li><li id="ul0015-0214" num="0927"> VMSC Visited MSC </li><li id="ul0015-0215" num="0928"> VPLMN Visited Public Land Mobile Network </li><li id="ul0015-0216" num="0929"> VPN Virtual Private Network </li><li id="ul0015-0217" num="0930"> W-CDMA Wideband Code Division Multiple Access </li><li id="ul0015-0218" num="0931"> WEP Wired Equivalent Privacy </li><li id="ul0015-0219" num="0932"> WGS-84 World Geodetic System 1984 </li><li id="ul0015-0220" num="0933"> WPA Wi-Fi Protected Access </li><li id="ul0015-0221" num="0934"> WZ1 World Zone1 </li></ul>

0935The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that specific details are not required in order to practice the invention. Thus, the foregoing descriptions of specific embodiments of the invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed; obviously, many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, they thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. Moreover, while the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention.

0936In some examples and diagrams, two components may be described or shown as connected to each other. The connection may be a direct wire connection or the two components may be communicatively coupled to each other through other components or through wireless or broadband links. Thus, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims.