WO2005060292A1

WO2005060292A1 - Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system

Info

Publication number: WO2005060292A1
Application number: PCT/US2004/042456
Authority: WO
Inventors: Michael D. Gallagher; Rajeev Gupta; Jason Shi
Original assignee: Kineto Wireless, Inc.
Priority date: 2003-12-16
Filing date: 2004-12-16
Publication date: 2005-06-30
Also published as: US7640008B2; US7949326B2; US20090054070A1; US20050186948A1

Abstract

A system includes a network controller to communicate with a telecommunications network. The network controller is coupled to one or more unlicensed wireless base stations service one or more unlicensed wireless access areas. Each unlicensed wireless access area is mapped to one or more licensed wireless access areas. The system includes a mobile station to communicate with the telecommunications network using a licensed wireless communication channel serviced by the telecommunications network in a licensed wireless access area, and an unlicensed wireless communication channel in an unlicensed wireless access area. The mobile station is associated with a licensed wireless network identifier and a licensed wireless location identifier when the mobile station is in the licensed wireless access area and is associated with an unlicensed wireless network identifier and an unlicensed wireless location identifier when the mobile station is in the unlicensed wireless access area.

Description

APPARATUS AND METHOD FOR EXTENDING THE COVERAGE AREA OF A LICENSED WIRELESS COMMUNICATION SYSTEM USING AN UNLICENSED WIRELESS COMMUNICATION SYSTEM

[0001] This application is a Continuation in Part of U.S. Nonprovisional Application Serial No. 10/688,470, entitled "Apparatus and Method for Extending the Coverage Area of a Licensed Wireless Communication System Using an Unlicensed Wireless Communication System," filed October 17, 2003.

[0002] This application claims the benefit of U.S. Provisional Application Serial No. 60/530,141, entitled "Unlicensed Mobile Access Architecture," filed March 16, 2004. This application also claims the benefit of U.S. Provisional Application Serial No. , entitled "Unlicensed Mobile Access Mobility Management and

Emergency Services," filed December 16, 2003.

CROSS REFERENCE TO RELATED APPLICATIONS [0003] This application is also related to commonly owned U.S. Applications: Serial No. 10/115,833, entitled "Unlicensed Wireless Communications Base Station to Facilitate Unlicensed and Licensed Wireless Communications with a Subscriber Device, and Method of Operation," filed April 2, 2002; Application Serial No. 10/251,901, entitled "Apparatus for Supporting the Handover of a Telecommunication Session between a Licensed Wireless System and an Unlicensed Wireless System," filed September 20, 2002; Provisional Application Serial No. 60/447,575, entitled "Mobile Station Functionality in Support of a System for Extending the Coverage Area of a Licensed Wireless Communication System using an Unlicensed Wireless Communication," filed February 14, 2003; and Provisional Application Serial No. 60/468,336, entitled "Method for Installation of Broadband Customer Premise Equipment without User/Operator Configuration," filed May 5, 2003, the contents of each of which are hereby incorporated by reference.

TECHNICAL FIELD [0004] This invention relates generally to telecommunications. More particularly, this invention relates to a technique for seamlessly integrating voice and data telecommunication services across a licensed wireless system and an unlicensed wireless system.

BACKGROUND OF THE INVENTION [0005] Licensed 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.

[0006] Licensed wireless systems utilize wireless signal frequencies that are licensed from governments. Large fees are paid for access to these frequencies. Expensive base station equipment is used to support communications on licensed frequencies. Base stations are typically installed approximately a mile apart from one another. As a result, the quality of service (voice quality and speed of data transfer) in 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. [0007] Landline (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. [0008] Currently, unlicensed wireless communication systems are deployed to increase the mobility of an individual using a landline. The mobility range associated with such systems is typically on the order of 100 meters or less. A common unlicensed wireless communication system includes a base station with a physical connection to a landline. The base station has a RF transceiver to facilitate communication with a wireless handset that is operative within a modest distance of the base station. Thus, this option provides higher quality services at a lower cost, but the services only extend a modest distance from the base station. [0009] Thus, there are significant shortcomings associated with current landline systems and licensed wireless systems. For this reason, individuals commonly have one telephone number for landline communications and one telephone number for licensed wireless communications. This leads to additional expense and inconvenience for an individual. It would be highly desirable if an individual could utilize a single telephone number for both landline communications and licensed wireless communications. Ideally, such a system would allow an individual, through seamless handoffs between the two systems, to exploit the benefits of each system.

SUMMARY OF THE INVENTION [0010] A method of integrating a licensed wireless system and an unlicensed wireless system includes initiating a wireless communication session in a first region serviced by a first wireless system and maintaining the wireless communication session in a second region serviced by a second wireless system. The first wireless system is selected from the group including a licensed wireless system and an unlicensed wireless system. The second wireless system is the unselected system from the group including the licensed wireless system and the unlicensed wireless system.

[0011] The invention also allows the subscriber to roam outside the range of the unlicensed base station without dropping communications. Instead, roaming outside the range of the unlicensed base station results in a seamless handoff (also referred to as a hand over) wherein communication services are automatically provided by the licensed wireless system.

[0012] In one embodiment of a system, a mobile station includes a first level 1, level 2, and level 3 protocols for a licensed wireless service. The mobile station also includes a second level 1, level 2, and level 3 protocols for an unlicensed wireless service. An indoor base station is operable to receive an unlicensed wireless channel from the mobile station when the mobile station is within an unlicensed wireless service area. An indoor network controller is coupled to the indoor base station and is adapted to exchange signals with a telecommunications network. The indoor network controller and indoor base station are configured to convert the second level 1, second level 2, and second level 3 protocols into a standard base station controller interface recognized by the telecommunications network. The mobile station, indoor base station, and indoor network controller are configured to establish a communication session on an unlicensed wireless channel using the base station controller interface when the mobile station is within the unlicensed wireless service area.

BRIEF DESCRIPTION OF THE FIGURES [0013] The invention is more fully appreciated in connection with the following detailed description taken in conjunction with the accompanying drawings, in which like reference numerals refer to corresponding parts throughout the several views of the drawings:

[0014] Figure 1 A provides an overview of the indoor access network (IAN) mobile service solution in accordance with one embodiment of the present invention;

[0015] Figure IB illustrates protocol layers of a mobile set in accordance with one embodiment;

[0016] Figure IC illustrates a method of protocol conversion in accordance with one embodiment;

[0017] Figure 2 illustrates two indoor access network (IAN) options in accordance with one embodiment;

[0018] Figure 3 illustrates an indoor access network (IAN) Broadband architecture in accordance with one embodiment;

[0019] Figure 4 illustrates an IAN Hybrid architecture in accordance with one embodiment;

[0020] Figure 5 illustrates components of a GSM mobile set for providing level 1, level 2, and level 3 layers for a licensed wireless service and an unlicensed wireless service in accordance with one embodiment; [0021] Figure 6 illustrates components of mobile set for providing level 1 , level 2, and level 3 layers for a GSM licensed wireless service and an unlicensed wireless service in accordance with one embodiment;

[0022] Figure 7A illustrates an IAN protocol architecture in support of GSM mobility management (MM) and connection management (CM) signaling, as well as IAN-specific signaling in accordance with one embodiment;

[0023] Figure 7B illustrates an IAN protocol architecture in support of GSM mobility management (MM) and connection management (CM) signaling, as well as IAN-specific signaling in accordance with one embodiment;

[0024] Figure 8 illustrates an IAN protocol architecture in support of GSM voice transmission in accordance with one embodiment;

[0025] Figure 9 illustrates components for level 1, level 2, and level 3 layers in a GPRS mobile set in accordance with one embodiment;

[0026] Figure 10 illustrates components for level 1, level 2, and level 3 layers in a GPRS mobile set in accordance with one embodiment of the present invention;

[0027] Figure 11 A illustrates an IAN protocol architecture in support of

GPRS data transmission in accordance with one embodiment;

[0028] Figure 1 IB illustrates an IAN protocol architecture in support of

GPRS data transmission in accordance with one embodiment;

[0029] Figure 12 illustrates a conventional GSM/GPRS registration area concept in accordance with one embodiment; [0030] Figure 13 illustrates registration areas for a licensed wireless network and an unlicensed wireless network in accordance with one embodiment;

[0031] Figure 14 illustrates registration areas for a licensed wireless network and an unlicensed wireless network in accordance with one embodiment;

[0032] Figure 15 illustrates several possible GSM and IAN coverage scenarios in accordance with one embodiment;

[0033] Figure 16 illustrates exemplary message flows involved in the normal, successful case when a mobile station is powered on in an area with both GSM and IAN coverage in accordance with one embodiment;

[0034] Figure 17 illustrates exemplary message flows involved in the normal, successful case when a mobile station is powered on in an area with both GSM and IAN coverage in accordance with one embodiment;

[0035] Figure 18 illustrates exemplary message flows involved in the normal, successful case when a powered up mobile station enters IAN coverage from

GSM coverage while in the idle mode in accordance with one embodiment;

[0036] Figure 19 illustrates exemplary message flows involved in the normal, successful case when a powered up, idle mobile station re-enters IAN coverage following a temporary absence and prior to the expiration of timer TI in accordance with one embodiment;

[0037] Figure 20 illustrates exemplary message flows involved in the normal, successful case when a powered up mobile station re-enters IAN coverage following a temporary absence and after the expiration of timer TI but prior to the expiration of timer T2 in accordance with one embodiment;

[0038] Figure 21 illustrates exemplary message flows involved in the normal, successful case when the IBS and mobile station detect the loss of the IAN connection and both timer TI and T2 expire in accordance with one embodiment;

[0039] Figure 22 illustrates exemplary message flows in a first stage of voice bearer establishment for the IAN broadband architecture in accordance with one embodiment;

[0040] Figure 23 illustrates exemplary message flows in a first stage of bearer establishment for the IAN hybrid architecture in accordance with one embodiment;

[0041] Figure 24 illustrates exemplary message flows in an optimized IAN voice bearer establishment process associated with the hybrid architecture in accordance with one embodiment;

[0042] Figure 25 illustrates exemplary message flows involved in the normal, successful case for a mobile originated call in accordance with one embodiment;

[0043] Figure 26 illustrates exemplary message flows involved in the normal, successful case for a mobile terminated call in accordance with one embodiment;

[0044] Figure 27 illustrates exemplary message flows involved in the normal, successful case when a IAN-mode call is released by the IAN mobile station in accordance with one embodiment; [0045] Figure 28 illustrates exemplary message flows involved in the normal, successful case when a IAN-mode call is released by the other, non-IAN party in the call in accordance with one embodiment;

[0046] Figure 29 is an example of the relay of DTAP supplementary service messages in accordance with one embodiment;

[0047] Figure 30 illustrates exemplary mobility management functions in one embodiment; and

[0048] Figure 31 illustrates a reference model for enhanced emergency service support in accordance with one embodiment.

DETAILED DESCRIPTION [0049] The present invention is directed towards seamlessly providing wireless services to a mobile station (MS) using both a licensed wireless system and an unlicensed wireless system. The unlicensed wireless system is a short- range wireless system, which may be described as an "indoor" solution. However, it will be understood through the application that the unlicensed wireless system includes unlicensed wireless systems that cover not only a portion of a building but also local outdoor regions, such as outdoor portions of a corporate campus serviced by an unlicensed wireless system. The mobile station may, for example, be a wireless phone, smart phone, personal digital assistant, or mobile computer. The "mobile station" may also, for example, be a fixed wireless device providing a set of terminal adapter functions for connecting Integrated Services Digital Network (ISDN) or Plain Old Telephone Service (POTS) terminals to the wireless system. Representative of this type of device is the Phonecell line of products from Telular Corporation of Chicago, Illinois. Application of the present invention to this type of device enables the wireless service provider to offer so-called landline replacement service to users, even for user locations not sufficiently covered by the licensed wireless system. Throughout 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 specific to this application is included in Appendix I. [0050] Figure IA illustrates an Indoor Access Network (IAN) system 100 in accordance with one embodiment of the present invention. As indicated by first arrow 104, a licensed wireless communication session is conducted with a mobile station (MB) 102 to a voice or data telecommunications network 114 (e.g., including a mobile switching center (MSC) 116 for voice data or a serving GPRS support node (SGSN) 118 for a data network). The first path 104 includes a wireless channel 106 of a licensed wireless system, a base transceiver station (BTS) 108, private trunks 110, and a base station controller (BSC) 112. The base station controller 112 communicates with telecommunications network 114 through a standard base station controller interface 190. For example, the base station controller 112 may communicate with the MSC via the GSM A-interface for circuit switched voice services and with the SGSN via the GSM Gb interface for packet data services (GPRS). Conventional licensed voice and data networks 114 include protocols to permit seamless handoffs from one recognized base station controller 112 to another base station controller 112 (not shown). [0051] However, if the mobile station is within range of an indoor base station (IBS) 128, a wireless session is conducted using an unlicensed channel of an unlicensed wireless system. In one embodiment, the service area of indoor base station 128 is an indoor portion of a building, although it will be understood that the service region of indoor base station 128 may include an outdoor portion of a building or campus. As indicated by second arrow 124, the mobile station 102 may be connected to the telecommunications network 114 via a second data path 124 including an unlicensed wireless channel 126, an unlicensed wireless service indoor base station (IBS) 128, an access network 130, and an indoor network controller (LNC) 132 (also described by the inventors of the present application as an "Iswitch") to voice/data network 114. The indoor network controller 132 also communicates with network 114 using a base station controller interface 190. As described below in more detail, indoor base station 128 and indoor network controller 132 may include software entities stored in memory and executing on one or more microprocessors (not shown in Figure IA) adapted to perform protocol conversion.

[0052] The unlicensed wireless channel 126 may be an unlicensed, free spectrum (e.g., spectrum around 2.4 GHz or 5 GHz). The unlicensed wireless service may have an associated communication protocol. As examples, the unlicensed wireless service may be a Bluetooth compatible wireless service, or a wireless local area network (LAN) service (e.g., the 802.11 IEEE wireless standard). This provides the user with potentially improved quality of service in the service regions of the unlicensed wireless service. Thus, when a subscriber is within range of the unlicensed base station, the subscriber may enjoy low cost, high speed, and high quality voice and data services. In addition, the subscriber enjoys extended service range since the handset can receive services deep within a building. This type of service range is not reliably provided by a licensed wireless system. However, the subscriber can roam outside the range of the unlicensed base station without dropping communications. Instead, roaming outside the range of the unlicensed base station results in a seamless handoff (also referred to as a hand over) wherein communication services are automatically provided by the licensed wireless system, as described in more detail in U.S. Pat. App. Ser. No. 10/115,833, the contents of which are hereby incorporated by reference.

[0053] Mobile station 102 has a microprocessor and memory (not shown) that includes computer program instructions for executing wireless protocols for managing communication sessions. As illustrated in Figure IB, in one embodiment the mobile station 102 includes a layer 1 protocol layer 142, layer 2 protocol layer 144, and a layer 3 signaling protocol layer for the licensed wireless service that includes a radio resource (RR) sublayer 146, a mobility management (MM) sublayer 148, and a call management (CM) layer 150. It will be understood that the level 1 , level 2, and level 3 layers may be implemented as software modules, which may also be described as software "entities." In accordance with a common nomenclature for licensed wireless services, layer 1 is the physical layer, i.e., the physical baseband for a wireless communication session. The physical layer is the lowest layer of the radio interface and provides functions to transfer bit streams over physical radio links. Layer 2 is the data link layer. The data link layer provides signaling between the mobile station and the base station controller. The RR-sublayer is concerned with the management of an RR-session, which is the time that a mobile station is in a dedicated mode, as well as the configuration of radio channel, power controller, discontinuing transmission and reception, and handovers. The mobility management layer manages issues that arise from the mobility of the subscriber. The mobility management layer may, for example, deal with mobile station location, security functions, and authentication. The call control management layer provides controls for end-to-end call establishment. These functions for a licensed wireless system are well known by those in the art of wireless communication. [0054] In one embodiment of the present invention, the mobile station also includes an unlicensed wireless service physical layer 152 (i.e., a physical layer for unlicensed wireless service such as Bluetooth, Wireless local area network, or other unlicensed wireless channel). The mobile station also includes an unlicensed wireless service level 2 link layer 154. The mobile station also includes an unlicensed wireless service radio resource sublayer(s) 156. An access mode switch 160 is included for the mobile management 148 and call management layers 150 to access the unlicensed wireless service radio resource sublayer 156 and unlicensed wireless service link layer 154 when the mobile station 102 is within range of an unlicensed wireless service indoor base station 128

[0055] The unlicensed radio resource sublayer 156 and unlicensed link layer 154 may include protocols specific to the unlicensed wireless service utilized in addition to protocols selected to facilitate seamless handoff between licensed and unlicensed wireless systems, as described below in more detail. Consequently, the unlicensed radio resource sublayer 156 and unlicensed link layer 154 need to be converted into a format compatible with a conventional base station controller interface protocol 190 recognized by a MSC, SGSN, or other voice or data network.

[0056] Referring to Figure IC, in embodiment of the present invention, the mobile station 102, indoor base station 128 and indoor network controller 132 provide an interface conversion function to convert the level 1, level 2, and level 3 layers of the unlicensed service into a conventional base station subnetwork (BSS) interface 190 (e.g., an A-interface or a Gb-interface). As a result of the protocol conversion, a communication session may be established that is transparent to the voice network/data network 114, i.e., the voice/data network 114 uses its standard interface and protocols for the communication session as it would with a conventional communication session handled by a conventional base transceiver station. For example, in some embodiments the mobile station 102 and indoor network controller 132 are configured to initiate location update and service requests that ordinarily originate from a base station controller. As a result, protocols for a seamless handoff of services that is transparent to voice/data network 114 are facilitated. This permits, for example, a single phone number to be used for both the licensed wireless service and the unlicensed wireless service. Additionally, the present invention permits a variety of services that were traditionally offered only through licensed wireless services to be offered through an unlicensed wireless service. The user thus gets the benefit of potentially higher quality service when their mobile station is located within the area serviced by a high bandwidth unlicensed wireless service while also having access to conventional phone services.

[0057] The licensed wireless service may comprise any licensed wireless service having a defined BSS interface protocol 190 for a voice/data network 114. In one embodiment, the licensed wireless service is a GSM/GPRS radio access network, although it will be understood that embodiments of the present invention include other licensed wireless services. For this embodiment, the indoor network controller 132 interconnects to the GSM core network via the same base station controller interfaces 190 used by a standard GSM BSS network element. For example, in a GSM application, these interfaces are the GSM A- interface for circuit switched voice services and the GSM Gb interface for packet data services (GPRS). In a UMTS application of the invention, the indoor network controller 132 interconnects to the UMTS network using a UMTS Iu-cs interface for circuit switched voice services and the UMTS Iu-ps interface for packet data services. In a CDMA application of the invention, the indoor network controller 132 interconnects with the CDMA network using the CDMA Al and A2 interfaces for circuit switched voice services and the CDMA A10 and Al 1 interfaces for packet data services.

[0058] In a GSM/GPRS embodiment, indoor network controller 132 appears to the GSM/GPRS core network as a GSM BSS network element and is managed and operated as such. In this architecture the principle elements of transaction control (e.g., call processing) are provided by higher network elements; namely the MSC 116 visitor location registry (VLR) and the SGSN. Authorized mobile stations are allowed access to the GSM/GPRS core network either directly through the GSM radio access network if they are outside of the service area of an indoor base station or via the indoor access network system 100 if they are within the service area of an indoor base station 128.

[0059] Since a communication session to the IAN system 100 is transparent to a voice or data network 114, the unlicensed wireless service may support all user services that are typically offered by the wireless service provider. In the GSM case, this preferably includes the following basic services: Telephony; Emergency call (e.g., E911 calling in North America); Short message, mobile- terminated point-to-point (MT/PP); Short message, mobile-originated point-to- point (MO/PP); GPRS bearer services; Handover (outdoor-to-indoor, indoor-to- outdoor, voice, data, SMS, SS). Additionally for GSM, this preferably includes the following supplementary services: Call Deflection; Calling Line Identification Presentation; Calling Line Identification Restriction; Connected Line Identification Presentation; Connected Line Identification Restriction; Call Forwarding Unconditional; Call Forwarding on Mobile Subscriber Busy; Call Forwarding on No Reply; Call Forwarding on Mobile Subscriber Not Reachable; Calling Name Presentation; Call Waiting; Call Hold; Multi Party Service; Closed User Group; Advice of Charge (Information); Advice of Charge (Charging); User-to-user signaling; Barring of All Outgoing Calls; Barring of Outgoing International Calls; Barring of Outgoing International Calls except those directed to the Home PLMN Country; Barring of All Incoming Calls; Barring of Incoming Calls when Roaming Outside the Home PLMN Country; Explicit Call Transfer; Support of Private Numbering Plan; Completion of calls to busy subscribers; Unstructured Supplementary Services Data; SIM Toolkit. Moreover, it preferably includes Regulatory and Other Services such as: lawfully authorized electronic surveillance (also known as "wiretap"); TTY (also known as Telecommunications Device for the Deaf); and Location services. [0060] Figure 2 illustrates embodiments of the access network 130 configuration for coupling the indoor base station 128 to the indoor network controller 132. In one embodiment, the access network is broadband only. In this architecture, all traffic between the indoor network controller 132 and the customer premise equipment (i.e., indoor base station and mobile station), including all voice service, data service and signaling traffic, is conveyed using a broadband access network. In a hybrid version, both Broadband and POTS are used. In this architecture, all data service and signaling traffic between the indoor network controller 132 and the customer premise equipment is conveyed using a broadband access network; however, voice traffic is conveyed using common PSTN bearer channels (e.g., POTS or Plain Old Telephone Service). We refer to this as the "hybrid architecture" in this application. [0061] Figure 3 illustrates one embodiment of an IAN broadband architecture. A Kl interface 305 between the mobile station 102 and the indoor base station 128 is illustrated along with a K2 interface 310 between the indoor base station 128 and indoor network controller 132.

[0062] Figure 4 illustrates an embodiment of a hybrid IAN architecture for GSM. The Kl interface 305 between the mobile station 102 and the indoor base station 128 and the K2 interface 310 between the indoor base station 128 and the indoor network controller 132 is illustrated. These interfaces and techniques for protocol conversion will be described below in more detail. [0063] Figure 5 provides an overview of a level 1, level 2, and level 3 GSM- related protocol architecture for one embodiment of mobile station 102. As illustrated, there are two logical radio resource (RR) management entities: the GSM RR entity 546 and the IAN RR entity 556. The protocol architecture includes a GSM baseband level 1 layer 542, GSM level 2 link layer 544, Bluetooth baseband level 1 layer 552, Bluetooth level 2 layers 554, access mode switch 560, and upper layer protocols 580. When the mobile station is operating in an IAN mode, the IAN RR entity 556 is the current "serving" RR entity providing service to the mobility management (MM) sublayer via the designated service access point (SAP) (RR-SAP) (shown in Figure 6). The GSM RR entity is detached from the MM sublayer in this mode. The IAN RR entity 556 is a new set of functions. IAN-RR entity 556 is responsible for several tasks. First the IAN-RR entity 556 is responsible for discovery of IAN coverage and IAN registration. Second, the IAN-RR entity 556 is responsible for emulation of the GSM RR layer to provide the expected services to the MM layer; i.e., create, maintain and tear down RR connections. In one embodiment, all existing GSM 04.07 primitives defined for the RR-SAP apply. The plug-in of the IAN RR entity 556 is made transparent to the upper layer protocols in this way. Third, the IAN-RR entity 556 module is responsible for coordination with the GSM RR entity to manage access mode switching and handover.

[0064] Figure 6 illustrates an embodiment of the mobile station 102 showing portions of the level 2 and level 3 layers. In this embodiment, there is provided IANGSM-SAP 592, GSMIAN-SAP 590 interface handlers for access mode switching and handover. The IAN RR entity 556 provides coordination with the GSM RR entity 546 through the IANGSM-SAP 592, specifically for access mode switching and "handout" (i.e., from indoor to outdoor) procedures. The GSM RR entity 546 provides coordination with the IAN RR entity 556 through the GSMIAN-SAP 590, specifically for access mode switching and "handing over" (i.e., from outdoor to indoor) procedures. The function of mobility management layer 565 and connection management layer 570 will be described below in more detail.

[0065] Figure 7A illustrates an embodiment in which an IAN protocol architecture supports GSM MM and CM signaling, as well as IAN-specific signaling for the unlicensed wireless service. The MSC sublayers are conventional, well known features known in the art in regards to the message transfer part ((MTP) interfaces 705, signaling connection control part, (SCCP) 707, base station system application part (BSSAP) 709, mobility management interface 711, and connection management interface 713. [0066] The IAN-RR protocol supports the IAN "layer 3" signaling functions. This includes the end-to-end GSM signaling between the indoor network controller 132 and mobile station 102, via IAN-RR message relay functions in the indoor base station 128. The indoor network controller 132 is responsible for the interworking between these messages and the analogous A-interface messages. The IAN-RR protocol also supports IAN-specific signaling between the mobile station 102, indoor base station 128 and indoor network controller 132; e.g., for mobile station-to-indoor base station bearer path control. [0067] The radio resource layers in the mobile station include an IAN-RR sub-layer 556 and an IEP sublayer 557. The IAN- radio resource (RR) protocol is conveyed in an IAN Encapsulation Protocol (IEP) over the Kl interface 305, with the IEP being administered by the IEP sublayer 555. The IEP packets are transferred over the Kl interface 305 using the services of an unlicensed wireless service layer 2 connection access procedure (L2CAP) link layer. [0068] The IAN-RR protocol is conveyed in an IAN Transfer Protocol (ITP) over the K2 interface 310 using an ITP module 702. The ITP messages are transferred using an IAN Secure Tunnel (1ST) connection between the indoor base station 128 and the indoor network controller 132. The 1ST may be provided using standard security protocols. The use of the standard Secure Socket Layer (SSL) protocol 704 running over TCP/IP 706 is shown in Figure 7A. Another option is to use IPSec. An intervening broadband access system 719 supports lower level IP connectivity.

[0069] The ITP module also supports non IAN-RR signaling between the indoor base station 128 and the indoor network controller 132. This includes the IBS-to-INC bearer path control signaling. This signaling may trigger, or be triggered by, IAN-RR signaling. We refer to this signaling as the indoor base station Management Application Protocol (EBSMAP) 708. [0070] Figure 7B illustrates an alternate embodiment in which the IAN- specific protocol functions of indoor base station 128 are moved to mobile station 102, allowing the use of unlicensed access points that do not support IAN- specific functionality but do support generic IP connectivity; for example, standard Bluetooth or IEEE 802.1 lb access points. As illustrated, in this embodiment, the SSL-based IAN Secure Tunnel and all upper layer protocols terminate on the mobile station. From the perspective of indoor network controller 132, there is no difference between the embodiment illustrated in Figure 7 A and that illustrated in Figure 7B.

[0071] Figure 8 illustrates one embodiment of an IAN protocol architecture in support of GSM voice transmission. Audio flows over the Kl interface in a format illustrated as the "Kl Audio Format." For example, the Kl audio format may be the 64 kbps continuous variable slope delta modulation (CVSD) format running over Synchronous Connection Oriented (SCO) channels, as specified in the Bluetooth VI.1 standards. It is also possible to use standard voice over IP techniques using Bluetooth, 802.11 or other unlicensed technology over the Kl interface. Audio flows over the K2 interface in a format illustrated as the "K2 Audio Format." For example, a number of RTP-based audio formats may be used; e.g., G.711 (A-law or mu-law) and G.729A. Audio flows over the indoor network controller 132 to MSC interface, A, in 64 kbps pulse code modulation (PCM) format (G.711 A-law or mu-law). If the K2 audio format is something other than G.711, then transcoding is required in the indoor network controller 132; likewise, if the Kl and K2 audio formats are not the same, then transcoding is required in the indoor base station 128.

[0072] Figures 9-11 illustrate a corresponding GPRS implementation. Figure 9 provides an overview of the GPRS-related protocol architecture for the IAN mobile station. Figure 10 shows details of one embodiment of an internal IAN/GPRS protocol architecture of the mobile station. Figure IIA shows the corresponding GPRS signaling mode when the mobile station is operating using the unlicensed wireless service. Figure 11B shows the corresponding GPRS data transmission mode when the mobile station is operating using the unlicensed wireless service. The IAN GPRS protocol architecture effectively enables the tunneling of GPRS signaling and data packets through the IAN utilizing the unlicensed spectrum; the IAN-GRR protocol serves the same tunneling function as the IAN-RR protocol, but for packet-switched traffic between the mobile station 102 and SGSN 118. [0073] Referring to Figure 10, the IAN/GPRS architecture includes two logical GPRS radio resource (RR) entities: the GPRS RLC 905 entity and the IAN GRR entity 955. In IAN mode, the IAN GRR entity is the current "serving" RR entity providing service to the logical link control 980 (LLC) layer via the designated service access point (GRR-SAP). The GPRS RLC entity is detached from the LLC layer in this mode.

[0074] The IAN-GRR RLC entity 955 is responsible for the following tasks. First, it emulates the GPRS RLC layer 905 to provide the expected services to the upper layer protocols. Second, it coordinates with the GPRS RLC 905 entity to manage access mode switching. In one embodiment, the IAN GRR layer includes IANGPRS-SAP and GPRSIAN-SAP interface handlers for access mode switching and modified PLMN/cell reselection behavior in IAN mode. [0075] The IAN GRR entity 955 provides coordination with the GPRS RLC entity 905 through an IAN GPRS-SAP, specifically for access mode switching procedures. The GPRS RLC entity 905 provides coordination with the IAN GRR entity through the GPRSIAN-SAP, specifically for access mode switching procedures.

[0076] Figure 11 A illustrates an embodiment in which an IAN protocol architecture supports GPRS signaling. The SGSN layers are conventional, well known features known in the art in regards to the GPRS network management (NM), packet flow management (PFM), base station system GPRS protocol (BSSGP), network service (NS), GPRS mobility management (GMM), logical link control (LLC), session management (SM) and short message service (SMS) interfaces. The IAN-GRR protocol supports message encapsulation or tunneling functions. The indoor network controller 132 is responsible for terminating the NM, PFM, GMM, BSSGP, and NS layers and for relaying LLC protocol data units (PDUs) conveying GPRS signaling between the IAN-GRR encapsulated form present on the K2 interface and the analogous Gb-interface messages. The indoor base station provides simple IAN-GRR message relay functions between the Kl and K2 interfaces. The IAN protocol architecture in support of GPRS signaling makes use of the ITP, SSL, TCP/IP, and IEP layers described in reference to Figure 7A. GPRS data transmission may also be supported via the architecture of Figure 1 IA, whereby LLC PDUs conveying GPRS data packets are relayed by the INC and IBS between the SGSN and the mobile station. Figure 1 IB illustrates an alternate embodiment in which the transport protocol on the K2 interface is not the connection-oriented TCP protocol, but is instead the connectionless UDP protocol. This approach has the advantage of improved support for application protocols that are best matched with connectionless transports (e.g., voice over IP). Data transfer security over the K2 provided by SSL in Figure 1 IA can be provided by IPSec as shown in Figure 1 IB. [0077] The basic operation of embodiments of the mobile station, base station, and indoor network controller 132 having been described above in regards to the operation of level 1, level 2, and level 3 layers and voice bearer operation, registration, mobility management, and call management procedures will now be discussed for several embodiments.

[0078] Conventional licensed wireless systems include procedures for handing off a communication session to different components of the licensed wireless system. These include, for example, handing off a session to different cells under control of the same base station controller, switching cells under control of different base station controllers but belonging to one MSC, and switching cells under control of different MSCs. In embodiments of the present invention, these protocols have been further adapted to initiate a handoff of a communication session to the unlicensed wireless system when the mobile station is within range of at least one indoor base station controller. [0079] Figure 12 illustrates the concept of registration used for mobility management in GSM/GPRS. A MSC 116 may have more than one BSC 112 and associated base station subsystems (BSSs) linked to it, such as BSS 112-A and BSS 112-B. The coverage area is split into a plurality of logical registration areas 1205, such as 1205-x, 1205-y, and 1205-z called Location Areas (LA) (for GSM) and Routing Areas (RA) (for GPRS).

[0080] A mobile station 102 is required to register with the base subsystem (BSS) of the network each time the serving location area (or routing area) changes. This provides the network with information regarding the location of the mobile station that may, for example, be used to determine which BTS 108 and BSC 112 will service the communication session. One or more location areas identifiers (LAIs) may be associated with each visitor location register (VLR) in a carrier's network. Likewise, one or more routing area identifiers (RAIs) may be controlled by a single SGSN. In actual implementations, the number of different registration areas controlled by each VLR/SGSN is decided based upon a tradeoff between minimizing network paging and location updating load. The fewer registration areas, the less location updates on the system but the higher the paging load. The higher the number of registration areas, the lower the system paging load but the higher the number of user registrations. A single location area/routing area 1205-y may be associated with multiple base station subsystems (BSS). If this is the case, a mobile-terminated call to a subscriber that is registered in a particular location area will result in paging requests to each BSS associated with that location area. Note that there is not necessarily a one- to-one relationship between LAI and RAI; there may be multiple GPRS routing areas within a single location area.

[0081] Referring to Figures 13 and 14, in embodiments of the present invention, the registration concept is adapted to describe services by one or more indoor base stations 128 to facilitate roaming and handoff between the licensed wireless system and the unlicensed wireless system, as described below in more detail. In the present invention, a set of IAN LAI RAI pairs defines a set of at least one indoor base stations 128 under the control of one indoor network controller 132. Thus, referring to Figure 13, a single indoor network controller 132 may have one or more indoor base stations defining location area/routing areas 1305 and 1310 serviced by the unlicensed wireless system. One or more licensed wireless service area local area/routing areas may overlap with the IAN LAI/RAI. In a first IAN configuration illustrated in Figure 13, Location Area and Routing Area identity or identities are shared between the IAN system and the umbrella GSM network.

[0082] As illustrated in Figure 13, the indoor network controller 132 may be connected to a different MSC/SGSN than those that provide the umbrella GSM/GPRS coverage. For this reason, the mobile set 102 is preferably provided with the IAN LAI/RAI pair that is associated with the serving indoor base station 128 by the indoor network controller 132 as part of the "IAN Registration" procedure. This information is used in the mobile set to determine Mobility Management actions while the mobile set is "switched-on" in the GSM/IAN domain; e.g., if a location update is required upon leaving the indoor coverage area.

[0083] In a second umbrella IAN configuration illustrated in Figure, 14, Location Area and Routing Area identity or identities are not shared between the IAN system and the umbrella GSM network. Consequently, the indoor LAI and RAI 1405 may be substantially different than the outdoor LAI and RAI zones 1410 and 1415. The IAN system is identified by one or a set of registration identifiers (LAI and RAI). The IAN mobile station arbitrates between the two networks and avoids presenting the GSM network with an overload of registration requests during transient conditions; i.e., temporary movement into and out of the IAN network.

[0084] In one embodiment, an IAN registration is performed by the mobile station 102 to manage signal load on the public land mobile network (PLMN) infrastructure. An IAN registration is preferably automatically performed by the mobile set on initial detection of IAN coverage or following a temporary interruption of IAN coverage under certain specific conditions. As described below in more detail, this proactive registration process facilitates seamless handoff for a variety of environments and situations that may be encountered. In one embodiment, an IAN registration does not involve any signaling to the PLMN infrastructure and is wholly contained within the IAN system (i.e., the mobile station, indoor base station and indoor network controller). The IAN registration message delivered to the indoor network controller 132 preferably includes (among other parameters): IMSI; GSM update status, and associated parameters (e.g., LAI and TMSI, if available); GPRS update status, and associated parameters (e.g., RAI and P-TMSI, if available). [0085] In one embodiment, the IAN registration procedure is also used by the indoor network controller 132 to provide the mobile station 102 with the operating parameters associated with the IAN service on the indoor base station 128. This is analogous to the use of the GSM broadcast control channel (BCCH) to transmit system parameters to mobile stations in GSM cells. In this embodiment, the information that is transmitted includes (among other parameters): LAN-LAI (Location Area Identification); IAN-RAI (Routing Area Identification); LAN-CI (Cell Identification); IAN-ARFCN value (for handover purposes); IAN-BSIC value (for handover purposes); Attach/Detach Allowed (ATT) flag setting; GPRS network operating mode;

CELL_RESELECT_OFFSET, used to "bias" GSM cell selection in favor of cells with the same registration area as the IAN system; BA (BCCH Allocation) List: and Timer values. These parameters are packaged in an IAN-System-Information wrapper. This package is included in the IAN registration response to the mobile station. The package may also be included in other messages to the mobile station in the event that a system parameter update is required. [0086] Figure 15 illustrates several different radio environments that may be encountered by an IAN mobile station 102. In the first environment, the GSM and LAN coverage are completely separate and non-overlapping. The second possibility shows partially overlapping GSM and IAN coverage. In the final scenario, and perhaps the most common, the IAN coverage is completely encapsulated within the GSM coverage. An IAN device may power on in any of these environments and may transition between coverage areas in a number of attached states.

[0087] Ln one embodiment the mobile station 102 scans for both GSM and IAN radio coverage at power on or anytime when the mobile station 102 is idle and there is no coverage of any type. If only GSM coverage is detected, then the normal GSM mobility management procedure is initiated. If only IAN coverage is detected, then the mobile station 102 establishes a link to the indoor base station 128 and waits for a IAN-LINK-ATTACH message from the indoor base station 128. On receipt of the LAN-LINK- ATTACH message (indicating that the received signal level at the indoor base station 128 has passed a predefined threshold), the mobile station 102 performs the IAN registration procedure. Based upon the information returned, the mobile station 102 then determines if a full network registration is required and if so what type (e.g., GSM or GPRS). If both GSM and IAN coverage are detected, then the mobile station 102 performs the normal GSM mobility management procedure, then performs the IAN registration procedure.

[0088] There is also the possibility that a mobile user may initially be outside of the IAN coverage zone but eventually move into the IAN coverage zone. Consequently, in one embodiment, at anytime when the mobile station 102 is idle, in GSM coverage and there is no IAN coverage, the mobile station 102 periodically scans for IAN coverage. If IAN coverage is detected, the mobile station 102 initiates the LAN registration procedure described above. [0089] In some environments, such as inside a building, there may be IAN coverage but no GSM coverage. For this case, it is desirable that GSM scanning and other procedures be performed to enable the mobile station 102 to handoff to GSM upon exiting the IAN coverage zone. In one embodiment, at anytime when the mobile station 102 is idle, in IAN coverage and there is no GSM coverage, the mobile station 102 continues to perform normal GSM PLMN search procedures. If GSM coverage is detected, the mobile station 102 records the identification of the preferred GSM cell for handover or loss of IAN coverage situations. At anytime when the mobile station is idle, in IAN coverage and there is GSM coverage, the mobile station 102 continues to perform normal GSM cell reselection procedures.

[0090] Ln one embodiment, the mobile station 102 records the identification of the preferred GSM cell for handover or loss of IAN coverage situations. At power off with IAN coverage, a detach indication (if required by the PLMN network or normally sent by the mobile station at power off) is sent by the mobile station 102 to the PLMN via the IAN. This indication is encoded per the current GSM mode of operation (e.g., GSM or GPRS). At anytime when the mobile station 102 is operating in IAN mode (i.e., after successful IAN registration on the IAN), the mobile station 102 takes the CELL_RESELECT_OFFSET value into account in it GSM PLMN search and cell reselection procedures; i.e., the offset value "encourages" the mobile station 102 to show preference for a GSM cell in the same registration area as the indoor base station 128. [0091] Figure 16 illustrates one embodiment of initial registration message flows between the mobile station 102, indoor base station 128, and indoor network controller 132 at power-on between a mobile station, indoor base station, and indoor network controller involved in the normal, successful case when a mobile station is powered on in an area with both GSM and IAN coverage. This scenario illustrates the case where the IAN cell is in the location area where the mobile station was already registered such that an LMSI ATTACH message is not required and a periodic location update is also not required. Ln step a, upon "switch on" the mobile station will search for GSM and IAN coverage. The mobile station may first find GSM coverage and perform a location update using the outdoor network. In step b, IAN coverage is detected; therefore, secure links are established between the mobile station 102 and indoor base station 128 and (if not already established) between the indoor base station 128 and indoor network controller 132. In step c, when the indoor base station 128 determines that the received signal from the mobile station is acceptable for IAN service, it sends a IAN-LINK- ATTACH message to the mobile station 102. Ln step d, the mobile station 102 sends a IAN-REGISTER message to the indoor base station 128. The indoor base station 128 relays the IAN-REGISTER message to the indoor network controller 132 using LBSAP. The indoor network controller 132 begins monitoring for page requests from the GSM network targeted at the mobile station in question. In step e, the indoor network controller 132 returns an IAN- REGISTER-ACK message to the indoor base station 128. An indication of the CI and LAI associated with the indoor base station 128 is included in this message, contained in the IAN-System-Information parameter. The indoor base station 128 transparently passes this information to the mobile station 102. The indoor base station 128 stores an indication that the mobile station 102 is registered for IAN service. In step f, the mobile station has selected a GSM cell based on normal GSM cell selection procedures. In step g, the mobile station 102 has the following information: 1) The GSM update status and associated parameters stored on the SLM; 2) the selected GSM cell information based on normal GSM cell selection procedures; 3) the indoor base station 128 cell information provided by the indoor network controller 132 (i.e., this and the GSM cell information allow the mobile station to determine whether the IAN configuration is type 1 or 2). Based on this information, the mobile station is required to determine if additional mobility management procedures are necessary. In this example, the mobile station determines that no further mobility management procedure is necessary (i.e., that the service state is for NORMAL SERVICE with the GSM cell selected). Ln step h, the IAN portion of the mobile station continues in IAN idle mode.

[0092] Figure 17 illustrates one embodiment of registration message flows and location update message flows at power-on involved in the normal, successful case when a mobile station is powered on in an area with both GSM and IAN coverage. This scenario illustrates the case (for example) where the IAN cell is in the location area where the mobile station was already registered, but an LMSI Attach or Location Update is required. Steps a-f are the same as those described with respect to Figure 16. In the example of Figure 17, in step g, the mobile station determines that a location update via the LAN is necessary. In step h, the mobile station 102 requests the establishment of a logical IAN-RR session from the indoor base stationl28 using the IAN-RR-REQUEST message. This message includes the resources that are required for the session (e.g., signaling channel only or signaling channel and voice channel). The indoor base station 128 verifies that it can provide the necessary resources to handle the request (i.e., air interface resources and indoor network controller connectivity). In step i, the indoor base station 128 signals its acceptance of the IAN-RR session request. In steps j-m, location update signaling takes place between the mobile station 102 and MSC 116. Ln step n, the MSC 116 sends the CLEAR- COMMAND message to the indoor network controller 132 to release the radio resource. Ln step o, the indoor network controller 132 acknowledges the release of the radio resources in the CLEAR-COMPLETE message. The SCCP connection associated with the session between the indoor network controller 132 and the MSC 116 is released (signaling not shown). In step p, the indoor network controller 132 signals the indoor base station 128 to release the IAN-RR session and associated resources via the IAN-RR-RELEASE message. The indoor base station 128 forwards the message to the mobile station. In step q, the mobile station acknowledges the release of the previously established IAN-RR session, using the IAN-RR-RELEASE-COMPLETE message. The indoor base station 128 forwards the acknowledgement to the indoor network controller 132. Ln step r, the mobile station 102 continues in IAN idle mode.

[0093] Figure 18 illustrates one embodiment of registration message flows involved in the normal, successful case when a powered up mobile station 102 enters IAN coverage from GSM coverage while in the idle mode. In step a, the mobile station 102 performs the appropriate GSM mobility management procedure (e.g., normal or periodic location update or LMSI attach) while in GSM coverage. This may involve communication between the MSC and the home location register (HLR) using standard protocols such as the Mobile Application Part (MAP) protocol. Ln step b, IAN coverage is detected. Steps c-f are the same as steps b-e in Figure 17. In step g, the mobile station 102 determines that no further mobility management procedure is necessary. In step h, the mobile station begins IAN idle mode operation.

[0094] Figure 19 illustrates embodiment of attachment/detachment message flows involved in the normal, successful case when a powered up, idle mobile station 102 re-enters LAN coverage following a temporary absence and prior to the expiration of a timer TI. In step a, the mobile station 102 is in IAN idle mode operation. In step b, the indoor base station 128 determines that the received signal from the mobile station is no longer acceptable for IAN service. The indoor base station 128 sends a IAN-LLNK-DETACH message to the mobile station 102. The mobile station 102 starts timer TI. If the link is lost before the indoor base station 128 can send IAN-LLNK-DETACH, the mobile station 102 and indoor base station 128 start timers TI and T2, respectively. If the link is lost after sending IAN-LLNK-DETACH, the indoor base station 128 starts timer T2. At some later point, the mobile station 102 and indoor base station 128 may reestablish the IAN link, in which case the indoor base station 128 stops timer T2. The secure link between the indoor base station 128 and indoor network controller 132 is still established. In step c, the indoor base station 128 determines that the received signal from the mobile station 102 is acceptable for IAN service and sends a IAN-LINK-ATTACH message to the mobile station, prior to the expiry of timer TI. The mobile station 102 stops timer TI. In step d, the mobile station 102 continues in IAN idle mode operation. [0095] Figure 20 illustrates an embodiment of detach, attach, and registration message flows involved in the normal, successful case when a powered up mobile station re-enters IAN coverage following a temporary absence and after the expiration of timer TI but prior to the expiration of timer T2. Steps a-b are the same as in the previous example of Figure 19. In step c, timer TI expires at the mobile station 102. In step d, the IAN application directs the mobile station 102 to resume normal GSM MM operation. The mobile station 102 selects the GSM cell, which has the same LAI as the IAN LBS; therefore, there is no need for a location update. In step e, the indoor base station 128 determines that the received signal from the mobile station 102 is now acceptable for IAN service. The indoor base station 128 sends an IAN-LINK-ATTACH message to the mobile station 102. Note that between step-b and step-e, the link between the mobile station and indoor base station 128 may be lost and then re-established. Ln step f, the mobile station 102 sends an IAN-REGISTER message to the indoor base station 128. In step g, since the indoor base station 128 considers the mobile station 102 to still be active, it returns an IAN-REGISTER-ACK message to the mobile station 102 without notifying the indoor network controller 132. The indoor base station 128 includes the previously stored IAN-System-Information parameter. Ln step h, the mobile station determines that no further mobility management procedure is necessary. Ln step I, the IAN application suspends GSM MM procedures and begins IAN idle mode operation. [0096] Figure 21 illustrates one embodiment of detachment and deregistration message flows involved in the normal, successful case when the indoor base station 128 and mobile station 132 detect the loss of the LAN connection and both timers TI and T2 expire for the idle mode. In step a, the mobile station 102 is in IAN idle mode operation. In step b, the indoor base station 128 determines that the received signal from the mobile station 102 is no longer acceptable for IAN service. The indoor base station 128 sends an IAN-LLNK-DETACH message to the mobile station 102. The mobile station starts timer TI. If the link is lost before the indoor base station 128 can send IAN-LLNK-DETACH, the mobile station 102 and indoor base station 128 may start timers TI and T2, respectively. In step c, the link between the mobile station 102 and indoor base station 128 is lost. The indoor base station 128 starts timer T2. Ln step d, timer TI expires at the mobile station 102. Ln step e, the IAN application directs the mobile station 102 to resume normal GSM MM operation. The mobile station 102 selects the GSM cell, which has the same LAI as the IAN LBS; therefore, there is no need for a location update. The mobile station 102 may also find that no GSM coverage is available, in which case it proceeds per normal GSM procedures. Ln step f, timer T2 expires at the indoor base station 128. Ln step g, the indoor base station 128 sends an IAN-DEREGISTER message to the indoor network controller 132 containing the reason for the deregistration (i.e., loss of IAN link). The indoor base station 128 releases any resources assigned to the mobile station 102. The indoor network controller 132 changes the mobile station state to "Inactive" or a similar state. Subsequent page requests for the mobile station 102 from the GSM network are ignored.

[0097] Figure 22 illustrates an embodiment of channel activation and assignment request message flows for Voice bearer establishment for the IAN broadband architecture. Figure 23 illustrates an embodiment of the analogous case for the IAN hybrid architecture. The indoor network controller 132 provides the signaling interworking functionality that allows the switched establishment of bearer paths between the MSC 116 and the indoor base station 128. [0098] In one embodiment, voice bearer establishment between the MSC 116 and the mobile station 102 takes place in three stages in the IAN broadband architecture solution: First, the indoor network controller 132 establishes a connection to the MSC-LNC circuit allocated by the MSC 116 during the A- interface circuit assignment process. In the broadband architecture, this is a TDM-to-VoLP connection, converting the TDM channel to the MSC 116 into a VoLP channel to the indoor base station 128. Second, the indoor network controller 132 sends a message to the indoor base station 128, directing it to establish VoLP connectivity to the VoLP channel established in step one. Finally, the indoor base station 128 directs the mobile station 102 to establish a voice link over the unlicensed air interface, and the indoor base station 128 connects this channel to the channel established in step two. Acknowledgements are returned from mobile station 102 to indoor base station 128 to indoor network controller 132 to MSC 116, completing the process.

[0099] In both cases illustrated in Figures 22-23, the GSM mobile originating and mobile terminating voice call signaling is exchanged between the mobile station 102 and the indoor network controller 132, flowing over the IAN Secure Tunnel between the indoor network controller 132 and the indoor base station 128. The indoor network controller 132 provides the necessary interworking between this signaling and the A-interface signaling to the MSC 116. During the call setup process the MSC 116 sends a BSSAP Assignment-Request message over the A-interface to the indoor network controller 132. A Circuit Identity Code (CIC) identifying a DS0 path between the MSC 116 and the indoor network controller 132 is provided in this message. The DS0 terminates on the media gateway element within the indoor network controller 132. In the broadband case, on reception of the BSSAP Assignment Request message: The indoor network controller 132 translates the Assignment-Request message into a voice over LP (VoLP) call setup request to the LP address associated with the indoor base station 128. The indoor network controller 132 sends a LBSMAP-ACTLVATE- CH message to the indoor base station 128. This message triggers VoLP channel establishment in the indoor base station 128. The indoor base station 128 sends a IAN-ACΗVATE-CH message to the mobile station 102, triggering voice link establishment over the air interface. The mobile station 102 sends acknowledgement (IAN-ACTLVATE-CH-ACK) to the indoor base station 128 and the indoor base station 128 sends acknowledgement (LBSMAP-ACTIVATE- CH-ACK) to the indoor network controller 132. The indoor network controller 132 translates the LBSMAP-ACΗVATE-CH-ACK message from the indoor base station 128 into a BSSAP Assignment Complete message, completing the process.

[00100] Referring to the hybrid case of Figure 23, the indoor network controller 132 translates the Assignment-Request message into a ISUP call setup request to the PSTN phone number associated with the indoor base station 128. The indoor base station 128 answers the call (i.e., goes off-hook) and the indoor network controller 132 translates the ISUP answer signal into a BSSAP Assignment-Complete message. Using ISUP signaling allows this connection to take place in sub-second timeframes. The indoor network controller 132 Application Server subsystem controls the Media Gateway subsystem via MGCP or Megaco (H.248) signaling to provide the switching between the TDM circuit from the MSC and the TDM circuit to the PSTN.

[00101] Referring to Figure 24, in one embodiment a further indoor network controller optimization is supported in a hybrid approach. The voice bearer is in the form of TDM DS0 circuits in the indoor network controller 132 from the MSC 116 and TDM DS0 circuits out of the indoor network controller 132 to the PSTN (or, potentially, a tandem switch in the PLMN), thus the media gateway function is not necessary, as shown in Figure 24. In this case, the indoor network controller 132 performs only signaling interworking between the A-interface BSSAP protocol and the ISUP protocol. This strategy assumes that the MSC 116 is configured to provide the circuit allocation function (i.e., the assignment of DSOs). This is the normal operating mode in GSM networks (non-remote -MSC- transcoder operation) as opposed to the alternative where the BSC provides this function. Circuits may be allocated in pools at the MSC 116. A pool of circuits will be required for the support of the indoor network controller 132. These bearer circuits will of course not be directly connected to the indoor network controller 132 but rather to a voice switch. The MSC 116 may need to allocate GSM descriptors (full rate, half rate etc.) to this trunk pool. For indoor network controller support, these channels may be described in the same manner as full rate channels; however, this description will bear no relevance to the IAN system. No transcoding and rate adaptation unit (TRAU) resources will be required for the origination or termination of IAN calls.

[00102] Figures 25-29 illustrate the message flows involved for various call management scenarios via the IAN network.

[00103] Figure 25 illustrates the message flows involved in the normal, successful case of a mobile originated call that includes registration with the indoor network controller 132, service request to the MSC 116, assignment requests, establishment of a voice channel, and connection. Ln step a, the mobile station 102 is registered for IAN service on the indoor network controller 132. In step b, the user enters or selects a called party number (B) and presses SEND. Ln step c, the mobile station requests the establishment of a logical IAN-RR session from the indoor base station 128 using the LAN-RR-REQUEST message. This message includes the resources that are required for the session (i.e., signaling channel and voice channel). The indoor base station 128 verifies that it can provide the necessary resources to handle the request (i.e., air interface resources and indoor network controller connectivity). Ln step c, the indoor base station 128 signals its acceptance of the IAN-RR session request. In step d, the mobile station 102 sends a CM-SERVICE-REQUEST message to the indoor base station 128. The indoor base station 128 relays the message to the indoor network controller 132 in an IBSAP message. The LBSAP header contains the mobile station identification, which is used to access the mobile station's 102 IAN record in the indoor network controller 132. The indoor network controller 132 constructs a DTAP CM-SERVICE-REQUEST message. The identifier included is the identifier provided by the mobile station. This message is encapsulated inside a BSSMAP COMPLETE-LA YER-3-LNFO message and sent to the MSC 116. Ln an optional step e, the MSC 116 may initiate the standard GSM authentication procedure.

[00104] Ln step f, if ciphering is not necessary, the MSC 116 signals service acceptance via the CM-SERVICE- ACCEPT message. The indoor network controller 132 relays this message to the mobile station 102. The procedure continues at step-g. Lf ciphering is necessary from the MSC's perspective (not shown in figure), the MSC 116 sends a BSSMAP CLPHER-MODE-COMMAND message to the indoor network controller 132, including the Encryption Information parameter. The indoor network controller 132 relays this to the mobile station 102 in the CLPHER-MODE-COMMAND message. The mobile station 102 responds with a CLPHER-MODE-COMPLETE message, which the indoor network controller 132 encapsulates in a BSSMAP CLPHER-MODE- COMPLETE message to the MSC 116. The mobile station 102 stores the Cipher Mode Setting. Note that this is only needed to enable ciphering if the call is subsequently handed over to GSM; the request for GSM ciphering does not result in the activation of GSM ciphering for the IAN call. If the BSSMAP CLPHER- MODE-COMMAND message includes an identity request (i.e., Cipher Response Mode parameter indicates LMEISV request), then the mobile station 102 includes the mobile station identity in the CLPHERLNG-MODE-COMPLETE message. [00105] Receipt of either the CM-SERVLCE- ACCEPT message or the CLPHER-MODE-COMMAND message indicates to the mobile station 102 that the MM connection is established. In step g, on receipt of a confirmation that the MM connection is established (i.e., receipt of the CM-SERVICE-ACCEPT), the mobile station 102 sends a SETUP message to the indoor network controller 132 and the indoor network controller 132 relays a DTAP SETUP message to the MSC 116. The Bearer Capability LE indicates "speech". Ln step h, a DTAP CALL-PROCEEDING message is returned to the indoor network controller 132 by the MSC 116. This message is delivered to the mobile station. Ln step i, a BSSMAP ASSLGNMENT-REQUEST message is sent by the MSC 116 to the indoor network controller 132. A circuit identity code (CIC) for the selected trunk is included in this message. In step j, The indoor network controller 132 establishes a media gateway connection to the endpoint identified by the CIC. In step k, the indoor network controller 132 sends a LBSMAP-ACTIVATE-CH message to the indoor base station 128; this message triggers VoLP channel establishment in the indoor base station 128. The indoor base station 128 relays an IAN-ACΗVATE-CH message to the mobile station 102, triggering voice link establishment between the mobile station 102 and indoor base station 128. In step 1, the mobile station-IBS and LBS-LNC voice channels are now established and a voice path exists between the indoor network controller 132 and mobile station 102.

[00106] In step m, the mobile station returns an LAN-ACTLVATE-CH-ACK message to the indoor base station 128 and the indoor base station 128 returns an LBSMAP-ACTLVATE-CH-ACK message to the indoor network controller 132. The indoor network controller 132 sends a BSSMAP ASSLGNMENT- COMPLETE message to the MSC 116. An end to end bearer path is now established between the MSC 116 and mobile station 102. In step n, the MSC 116 constructs an ISUP LAM using the B subscriber address, and sends it towards the called party's destination exchange PSTN 2505. In step o, the destination exchange responds with an ISUP ACM message. The MSC 116 sends a DTAP ALERTING or PROGRESS message to the indoor network controller 132. The message is propagated to the mobile station 102. ALERTLNG is used, for example, to direct the mobile station 102 to provide a ringback signal to the calling user; PROGRESS is used, for example, to notify the mobile station that the ringback signal is available inband from the network. Either way, the user hears the ringback tone. In step p, the called party answers and the destination exchange indicates this with an LSUP ACM message. The MSC 116 sends a DTAP CONNECT message to the indoor network controller 132. This in turn is delivered to the mobile station 102. In step q, a chain of acknowledgements are returned completing the two way path at each hop. Ln step r, the end-to-end two way path is now in place and voice communication begins. [00107] Figure 26 illustrates the message flows involved in the normal, successful case for a mobile terminated IAN-mode call. Step a shows the mobile station 102 is registered for LAN service on the indoor network controller 132. Ln step b, the GMSC receives a call from party A intended for the IAN subscriber from PSTN 2505.

[00108] In step c, the GMSC 2605 queries the home location register (HLR) 2610 for routing, sending the MAP Send-Routing-Information request message. The HLR 2610 queries the current serving MSC 116 using the MAP Provide- Roaming-Number request message. Ln step d, the MSC 116 returns a roaming number, MSRN, in the MAP Provide-Roaming-Number response message and the HLR 2610 relays this to the GMSC 2605 in the MAP Send-Routing- Information response message. In step e, the GMSC 2605 relays the call to the MSC 116. In step f, the MSC 116 sends a BSSMAP PAGING message to all BSCs in the location area, including the indoor network controller. The indoor network controller 132 retrieves the user IAN record corresponding to the LMSI in the PAGLNG message. If no record is found, or a record is found but the user is not in the active state, the indoor network controller 132 ignores the PAGING message. Otherwise, it sends an IAN-PAGLNG-REQUEST message to the mobile station. In step g, the mobile station requests the establishment of a logical IAN- RR session from the indoor base station 128 using the LAN-RR-REQUEST message. This message includes the resources that are required for the session (i.e., signaling channel and voice channel). The indoor base station 128 verifies that it can provide the necessary resources to handle the request (i.e., air interface resources and indoor network controller connectivity). In step h, the indoor base station 128 signals its acceptance of the IAN-RR session request. In step I, the mobile station sends an LAN-PAGLNG-RESPONSE message to the indoor network controller. Ln step j, optionally, the MSC 116 may initiate the standard GSM authentication procedure. Lf ciphering is necessary from the MSC's 116 perspective (not shown in figure), the MSC 116 sends a BSSMAP CLPHER- MODE-COMMAND message to the indoor network controller 132, including the Encryption Information parameter. The indoor network controller 132 relays this to the mobile station in the CLPHER-MODE-COMMAND message. The mobile station 102 responds with a CLPHER-MODE-COMPLETE message, which the indoor network controller 132 encapsulates in a BSSMAP CLPHER-MODE- COMPLETE message to the MSC 116. The mobile station stores the Cipher Mode Setting. Note that this is only needed to enable ciphering if the call is subsequently handed over to GSM; the request for GSM ciphering does not result in the activation of GSM ciphering for the IAN call. If the BSSMAP CIPHER- MODE-COMMAND message includes an identity request (i.e., Cipher Response Mode parameter indicates IMEISV request), then the mobile station 102 includes the mobile station identity in the CLPHERING-MODE-COMPLETE message. [00109] In step k, the MSC sends a DTAP SETUP message to the indoor network controller. The indoor network controller 132 relays the message to the mobile station 102. In step 1, on receipt of the SETUP message, the mobile station sends a CALL-CONFIRMED message to the indoor network controller 132. A DTAP CALL-CONFIRMED message is returned to the MSC 116 by the indoor network controller 132. Steps i-m are the same as those described above for Figure 24. Ln step r, the user is alerted. The mobile station 102 sends an ALERTING message to the indoor network controller 132 to indicate that the user is being alerted. The indoor network controller 132 translates this into a DTAP ALERTLNG message, and the MSC 116 returns an ISUP ACM message to the GMSC which forwards an ACM to the originating exchange. In step s, the user answers. The mobile station 102 sends a CONNECT message to the indoor network controller 132 to indicate that the user has answered. The indoor network controller 132 translates this into a DTAP CONNECT message, and the MSC 116 returns an ISUP ANM message to the GMSC which forwards an ANM to the originating exchange. Ln step t, a chain of acknowledgements are returned completing the two way path at each hop. In step u, the end-to-end two way path is now in place and voice communication begins. [00110] Figures 27-28 illustrate examples of call release by an IAN subscriber. Figure 27 illustrates the message flows involved in the normal, successful case when an IAN-mode call is released by the mobile station 102. In step a, the LAN subscriber ends the call (e.g., by pressing the END button). The mobile station 102 sends a DISCONNECT message to the indoor network controller 132 and the indoor network controller 132 relays a DTAP DISCONNECT message to the MSC 116. The MSC 116 sends an ISUP RELEASE message towards the other party. Ln step b, the MSC 116 sends a DTAP RELEASE message to the indoor network controller 132. The indoor network controller 132 relays this to the mobile station 102. Ln step c, the mobile station 102 sends a RELEASE- COMPLETE message to the indoor network controller 132 and the indoor network controller 132 relays a DTAP RELEASE-COMPLETE message to the . MSC. At this point, the MSC 116 considers the connection released. The MSC 116 should have received a ISUP RLC message from the other party's exchange. Ln step d, the MSC 116 sends BSSMAP CLEAR COMMAND to the indoor network controller 132 indicating a request to release the old resources. The SCCP Connection Identifier is used to determine the corresponding call. In step e, the indoor network controller 132 releases the LNC-to-MSC circuit associated with the call. Ln step f, the indoor network controller 132 acknowledges the release in a BSSMAP CLEAR-COMPLETE message to the MSC 116. The SCCP connection associated with the call between the indoor network controller 132 and the MSC 116 is released (signaling not shown). In step g, the indoor network controller 132 sends an IAN-RR-RELEASE message to the indoor base station 128. The indoor base station 128 relays the message to the mobile station 102. In step h, the mobile station 102 and the indoor base station 128 releases the voice channels and other resources allocated for the call. In step i, the mobile station 102 confirms the call release with the IAN-RR-RELEASE message to the indoor base station 128 and the indoor base station 128 relays this message to the indoor network controller 132.

[00111] Figure 28 illustrates the message flows involved in the normal, successful case when a IAN-mode call is released by the other, non-IAN party in the call. Referring to step a, the other party ends the call (e.g., by hanging up). The MSC 116 receives a ISUP RELEASE message from the other party's exchange. The MSC 116 sends a DTAP DISCONNECT message to the indoor network controller 132 and the indoor network controller 132 relays a DISCONNECT message to the mobile station 102. In step b, the mobile station 102 sends a RELEASE message to the indoor network controller 132. The indoor network controller 132 relays this to the MSC 116 in the DTAP RELEASE message. The MSC 116 sends a ISUP RLC message towards the other party. In step c, the MSC 116 sends a DTAP RELEASE-COMPLETE message to the indoor network controller 132 and the indoor network controller 132 relays a RELEASE-COMPLETE message to the mobile station 102. Steps d-i are similar to those described above in regards to Figure 27. [00112] Embodiments of the present invention also permit supplementary GSM services to be provided. GSM has standardized a large number of services. Beyond call origination and termination, the following services shall be supported by the IAN system: Service Standard (Stage 3); Short Message Services 04.11; Supplementary Service Control 04.80; Calling Line Identification Presentation (CLIP) 04.81; Calling Line Identification Restriction (CLLR) 04.81; Connected Line Identification Presentation (CoLP) 04.81; Connected Line Identification Restriction (CoLR) 04.81; Call Forwarding Unconditional 04.82; Call Forwarding Busy 04.82; Call Forwarding No Reply 04.82; Call Forwarding Not Reachable 04.82; Call Waiting (CW) 04.83; Call Hold (CH) 04.83; Multi Party (MPTY) 04.84; Closed User Group (CUG) 04.85; Advice of Charge (AoC) 04.86; User Signaling (UUS) 04.87; Call Barring (CB) 04.88; Explicit Call Transfer (ECT) 04.91; and Name Identification 04.96.

[00113] These supplementary services involve procedures that operate end-to- end between the mobile station 102 and the MSC 116. Beyond the basic GSM 04.08 direct transfer application part (DTAP) messages already described for MO and MT calls, the following 04.08 DTAP messages are used for these additional supplementary service purposes: CP-DATA; CP-ACK; CP-ERROR; REGISTER; FACLLITY; HOLD; HOLD-ACKNOWLEDGE; HOLD-REJECT; RETRIEVE; RETRIEVE-ACKNOWLEDGE; RETRIEVE-REJECT; RETRIEVE-REJECT; RETRIEVE-REJECT; RETRIEVE-REJECT; USER-INFORMATION; CONGESTION-CONTROL. These DTAP message are relayed between the mobile station 102 and MSC 116 by the indoor base station 128 and indoor network controller 132 in the same manner as in the other call control and mobility management embodiments.

[00114] Figure 29 illustrates one embodiment of message flows for providing supplementary GSM services. Referring to step a, an MM connection is established between the mobile station 102 and the MSC 116 for an ongoing call. In step b, a user requests a particular supplementary service operation (e.g., to put the call on hold). In step c, the mobile station 102 sends the HOLD message over the Kl interface to the indoor base station 128. The indoor base station 128 relays the HOLD message over the K2 interface to the indoor network controller 132. The indoor network controller 132 relays the DTAP HOLD message to the MSC 116 over the A-interface. Ln step d, the DTAP HOLD-ACK message is sent from MSC 116 to mobile station 102 in an analogous manner. In step e, later in the call, the user requests another supplementary service operation (e.g., to initiate a MultiParty call). Ln step f, the mobile station sends the FACILITY message over the Kl interface to the indoor base station 128. The indoor base station 128 relays the FACILITY message over the K2 interface to the indoor network controller 132. The indoor network controller 132 relays the DTAP FACLLΠΎ message to the MSC 116 over the A-interface. Ln step g, the DTAP FACILITY message containing the response is sent from MSC 116 to mobile station 102 in an analogous manner. ADDITIONAL ALTERNATE EMBODIMENTS [00115] As noted above, the mobile station may be, for example, a wireless phone, smart phone, personal digital assistant, or mobile computer. The mobile station may also be, for example, a fixed wireless device providing a set of terminal adapter functions for connecting Integrated Services Digital Network (ISDN) or Plain Old Telephone Service (POTS) terminals to the wireless system. Furthermore, Figure 7B illustrates an alternate embodiment in which the IAN- specific protocol functions of the indoor base station 128 are moved to the mobile station 102, allowing the use of unlicensed access points that do not support IAN- specific functionality but do support generic LP connectivity; for example, standard Bluetooth or LEEE 802.1 lb access points. In this embodiment, the SSL- based or LPSec-based LAN Secure Tunnel and all upper layer protocols terminate on the mobile station. From the perspective of the indoor network controller 132, there is no difference between the embodiment illustrated in Figure 7A and that illustrated in Figure 7B.

[00116] In one alternate embodiment, the mobile station-as-terminal adapter element is combined with the LBS element, creating a type of LBS that can serve both (a) LAN-equipped cell phones via the unlicensed interface (i.e., the normal LBS function described herein), and (b) POTS, ISDN or other fixed terminals (via the fixed wireless function described above). Note that these embodiments are transparent from the L C perspective.

[00117] Other terminal adapter types than those listed above may be employed with embodiments of the present invention. For example: (1) a terminal adapter that supports cordless telephones rather than POTS phones; (2) a terminal adapter that supports standard Session Initiation Protocol (SIP) telephones; and (3) a terminal adapter that also integrates a corded handset and user interface, such as one would find on a desk phone. Representative of the latter type of device is the Phonecell® SX5D Fixed Wireless Phone from Telular Corporation of Chicago, Illinois. In each case, the invention described herein describes how these terminal adapter functions can be connected to the wireless system via the unlicensed network.

[00118] The use of other standard Bluetooth capabilities together with embodiments of the present invention is possible. For example, there is a Bluetooth standard capability called "SLM Access Profile" that allows one Bluetooth device (e.g., an embedded cell phone subsystem in a car) to access the SLM that is in another Bluetooth device (e.g., the user's normal cell phone), allowing the first device to take on the "personality" associated with the SLM (i.e., that of the user's normal cell phone). The embodiments described above could make use of this standard capability to give the terminal adapter-attached devices (e.g., a POTS phone) the personality of the user's cell phone. MOBLLΠΎ MANAGEMENT [00119] In one embodiment, and as described in greater detail below, the indoor network controller (INC) 132 provides functions equivalent to that of a GSM BSC, and as such controls one or more (virtual) LAN cells, which may also be known as unlicensed mobile access (UMA) cells. In one embodiment, there may be a single UMA cell per LNC and, in an alternative embodiment, there may be one UMA cell per access point (AP) connected to an INC. The latter embodiment may be less desirable due to the large number of APs expected to be used, so the UMA architecture permits flexible groupings of APs into UMA cells. In one embodiment, each UMA cell may be identified by a cell global identifier (CGI), with an unused absolute radio frequency channel number (ARFCN) assigned to each UMA cell. Each UMA cell may be mapped to a physical boundary by associating it with specific GSM location areas served by the MSC. GSM cells within the location areas mapped to an UMA cell are configured with ARFCN-to-CGI mappings for that UMA cell. Further, this ARFCN may be advertised in the BA list by the GSM cells to permit handovers. Note that UMA cells may use the same location area identifiers (LAI) as existing GSM cells, or a new LAI may be used for UMA cells. The latter is useful in reducing paging in GSM cells when a mobile station is known to be registered via an LNC. The above discussion applies equally to GPRS routing areas and routing area identifiers (RALs). UMA CPE Addressing [00120] In one embodiment, customer premise equipment (CPE) includes the mobile station and the access point (AP) through which the mobile station may access the UMA network controller (UNC), which is also known as the indoor network controller (LNC) in this description, for UMA service. UMA CPE addressing parameters may include the parameters described below. [00121] Ln one embodiment, the UMA CPE addressing includes the international mobile subscriber identity (LMSL) associated with the SLM in the mobile equipment as a parameter. In one embodiment, the LMSI is provided by the UMA mobile station to the UNC when it requests UMA service via the K2 interface to the UNC. Unlike the GSM BSC, the UNC manages a context for each mobile station that is operating in UMA mode. Therefore, the UNC maintains a record for each served mobile station. For example, LMSL may be used by the UNC to find the appropriate mobile station record when the UNC receives a BSSMAP paging message.

[00122] Ln one embodiment, the UMA CPE addressing includes the address associated with the unlicensed interface in the mobile equipment (e.g., 802.11 MAC address) as a parameter. This identifier may be provided by the UMA mobile station to the UNC when it requests UMA service via the K2 interface. The UNC may use this address as an alternative to the LMSI to limit the transfer of the LMSI over the K2 interface and to assist in the routing of messages. [00123] Ln one embodiment, the UMA CPE addressing includes the temporary logical link identifier (TLLI) assigned to the mobile station by the serving GPRS support node (SGSN) as a parameter. This identifier may be provided via standard Gb-interface procedures. The UNC may track this address for each served mobile station to support GSM Gb-interface procedures (e.g., so that downlink GPRS packets may be routed to the correct mobile station). [00124] Ln one embodiment, the UMA CPE addressing includes the access point LD (AP-LD) as a parameter. The AP-ID may be the MAC address of the unlicensed mode access point through which the mobile station is accessing UMA service. This identifier may be provided by the UMA mobile station to the UNC when it requests UMA service via the K2 interface. In one embodiment, the AP-LD is be used by the UNC to support location services (e.g., enhanced 911 service) to the user based on the AP from which the service is being accessed. The AP-LD may also be used by the service provider to restrict UMA service access only to authorized APs.

[00125] Other CPE addressing parameters that may be used depend on the security requirements of the K2 interface (e.g., the need to manage UMA mobile station LP addresses for message routing via tunneled LPSec connections, or the need to manage local credentials assigned to the mobile station by the UNC). UMA Cell Identification [00126] Ln one embodiment, in order to facilitate the mobility management functions in GSM/GPRS, the coverage area is split into logical registration areas called location areas (for GSM) and routing areas (for GPRS). Mobile stations may be 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 visited location register (VLR) in a carrier's network. Likewise, one or more routing area identifiers (RALs) may be controlled by a single SGSN.

[00127] In one embodiment, a GSM cell is identified within the location or routing area by adding a cell identity (CI) to the location or routing area identification. The cell global identification (CGI) is the concatenation of the location area identification and the cell identity. In one embodiment, the cell identity is unique within a location area. An Exemplary UMA Approach to Cell Identification [00128] One embodiment of a UMA cell identification approach is described below. In this embodiment, a single UNC provides service for one or more UMA location areas and one or more UMA routing areas, and each UMA location area (or routing area) is distinct from, or the same as, the location area (or routing area) of the overlapping GSM cell. A UMA cell is identified within the UMA location or routing area by adding a cell identity (CI) to the location or routing area identification. The UMA cell global identification (UMA-CGI) is the concatenation of the location area identification and the cell identity. Ln one embodiment, a UMA cell may be a pre-defined partition of the overall UMA coverage area identified by a UMA-CGL value. Note that cell identification, like UMA information, may be transparent to the AP, such that the AP is not aware of its associated UMA-CGI value. The UMA components (e.g., mobile station and UNC) may support the ability to partition the overall UMA coverage area. [00129] In one embodiment, a partitioning method may include implementing a one-to-one or a many-to-one correspondence between GSM cell identity and UMA cell identity. Given the identification of a preferred GSM cell in a particular area, it may be possible to determine the coπesponding UMA cell identity based, for example, on UNC provisioning. An example of a one-to-one relationship is mapping a GSM cell to a UMA cell. An example of a many-to- one relationship is mapping a GSM location area (and associated GSM cells) to a UMA cell. This may be required for enhanced 911 emergency call routing purposes, as described under "Emergency Services" below. [00130] In one embodiment, when a UMA mobile station connects to the UNC for UMA service, it sends the CGI value and a path loss criterion parameter (CI) of the current GSM camping cell, as well as the neighbor cells, to the UNC. The UNC maps the GSM camping cell's CGI value to a corresponding UMA cell's CGI value based on mapping logic provisioned in the UNC. This may be a one- to-one mapping (e.g., if there is one UMA cell per GSM cell) or a many-to-one mapping (e.g., if there is one UMA cell per GSM location area). Lf no GSM coverage is available in the UMA service area, the UNC may assign the mobile station to a default "no GSM coverage" UMA cell. A single UNC may serve one MSC. This does not preclude UNC embodiments that combine multiple UNC "instances," as defined above, in a single device. Each UNC may also be assigned a unique "UMA-Handover-CGl" value used for GSM-to-UMA handover purposes. For example, this may be the value provisioned in the GSM RAN BSC's ARFCN-to-CGI tables and in the MSCs (e.g., to point to the UNC). UMA Operating Configurations [00131] In one embodiment, at least three UMA operating configurations may be identified. Ln a common core configuration, the UMA LAI and an umbrella GSM RAN LAI (e.g., that serves the subscriber's neighborhood) may be different, and the network may be engineered such that the same core network entities (e.g., MSC and SGSN) serve both the UMA cells and the umbrella GSM cells. One advantage of this configuration is that subscriber movement between the UMA coverage area and the GSM coverage area does not result in inter- system (e.g., MAP) signaling (e.g., location updates and handovers are intra- MSC).

[00132] Ln a separate core configuration, the UMA LAI and umbrella GSM RAN LAI are different, and the network may be engineered such that different core network entities serve the UMA cells and the umbrella GSM cells. One advantage of this configuration is that engineering of the UMA and GSM networks can be more independent than in the Common Core Configuration. This configuration is illustrated in Figure 14.

[00133] Ln a common LAL configuration, the UMA LAL and GSM RAN LAI are the same (e.g., different cells within the same LAI). Advantages of this configuration are that subscriber movement (while idle) between the UMA coverage area and the GSM coverage area may not result in any location update signaling, and that the mobile station can easily switch to GSM mode if UMA mode resources are temporarily unavailable (e.g., to respond to paging). This configuration is illustrated in Figure 13. UMA Registration and Deregistration [00134] Ln one embodiment, as described above, a UMA registration process does not employ signaling to the PLMN infrastructure and is contained within the UMA system (i.e., between the mobile station and UNC). The UMA registration process may serve at least two purposes. It may inform the UNC that a mobile station is connected through a particular AP and is available at a particular JP address. The UNC may keep track of this information, for example, for mobile- terminated calling. The registration process may also provide the mobile station with the operating parameters associated with the UMA service on the AP. This may be analogous to the use of the GSM broadcast control channel (BCCH) to transmit system parameters to mobile stations in GSM cells. GSM system information message content that is applicable in UMA mode may be delivered to the mobile station during the UMA registration process. [00135] Similarly, a UMA deregistration process may allow the mobile station to explicitly inform the UNC that it is leaving UMA mode, allowing the UNC to free resources that it may have assigned to the mobile station. The UNC may also support implicit UMA deregistration, wherein a secure channel to the mobile station is abruptly terminated. UMA Redirection [00136] In one embodiment, as described above, when a UMA mobile station connects to the UNC for UMA service, it may send a CGI value and a path loss criterion parameter (CI) of the current GSM camping cell, as well as the neighbor cells, to the UNC. Using this information, as well as internal database information, the UNC may be able to determine if it is the correct serving UNC for the mobile station, and if it is not the correct serving UNC, to redirect the mobile station to the correct UNC. The correct serving UNC may be the UNC whose UMA service area overlaps the mobile station's umbrella GSM coverage.

In one embodiment, the correct serving UNC might be attached to the same MSC as the GSM BSC to which the umbrella GSM cell belongs. In an alternative embodiment, the correct serving UNC might be attached to a different MSC that may hand-over to the MSC that provides umbrella GSM coverage to the mobile station, allowing the UNC to handover calls to and from GSM. It may also enable certain location-based services (e.g., E911 Phase 1, as described below) that can be tied to the location of the GSM cell. An internal database used by the

UNC may map GSM location areas to serving UNCs and conserve the amount of data that needs to be managed. This database may only need to change when a new UNC or a new GSM location area is added.

[00137] Lf no GSM coverage is available when a mobile station connects to the

UNC for UMA service, then the UNC may not reliably determine the location of the mobile station for the purposes of assigning the mobile station to the correct serving UNC (e.g., to enable handover and location-based services). The UNC may permit the operator to determine the service policy in this case (e.g., the operator may provide service to the user with certain limitations, possibly with a user interface indication on the mobile station). UMA Mobile Station Idle Mode Behavior [00138] In one embodiment, as described above, a UMA device may encounter different radio environments as illustrated in Figure 15. In a first environment, the GSM and UMA coverage areas are completely separate and non-overlapping.

In a second environment, the GSM and UMA coverage is partially overlapping.

Ln a third environment, which may be the most common, the UMA coverage is encapsulated within the GSM coverage. A UMA device may power on in any of these environments and further may transition in a number of attached states.

[00139] Ln one embodiment, at power on, and when the mobile station is idle and there is no coverage of any type, the mobile station may scan for both GSM and UMA radio coverage. If GSM coverage is detected, then the normal GSM mobility management procedure may be initiated. This condition may apply when no UMA coverage has been detected by the mobile station when GSM coverage is detected, or prior to the completion of the UMA registration process.

Lf UMA coverage is detected, then the UMA mobile station establishes a wireless

LAN (WLAN) link to the AP and monitor signal quality. When the received signal level at the mobile station passes a predefined threshold, the mobile station performs the UMA registration procedure. Based upon the information returned, the mobile station may determine if a full network registration is required, and if so, what type (e.g., GSM or combined GSM/GPRS). This procedure may apply when no GSM coverage exists or when UMA coverage is detected prior to detecting GSM coverage.

[00140] In one embodiment, when the mobile station is idle in GSM coverage, and there is no UMA coverage, the mobile station periodically scans for UMA coverage. If UMA coverage is detected, the mobile station may initiate the UMA registration procedure described above.

[00141] In one embodiment, when the mobile station is'idle in UMA coverage and there is no GSM coverage, the mobile station continues to perform normal

GSM PLMN search procedures. If GSM coverage is detected, the mobile station may send the GSM cell information to the UNC for possible UMA redirection purposes as described above. Alternatively, the mobile station may disable normal GSM PLMN search procedures to conserve power.

[00142] In one embodiment, when the mobile station is idle in UMA coverage, and there is GSM coverage, the mobile station may continue to perform normal

GSM cell reselection procedures and may store the identification of the selected

GSM cell to speed the transition to GSM mode, if required. Alternatively, the mobile station may disable normal GSM cell reselection procedures to conserve power.

[00143] Ln one embodiment, at power off in UMA coverage, a detach indication may be sent by the mobile station to the PLMN via the UMAN (e.g., if required by the PLMN network or normally sent by the mobile station at power off). This indication may be encoded per the current GSM mode of operation (e.g., GSM or GPRS).

[00144] In one embodiment, the UMA environment may be an LEEE 802.11 environment. In this case, the mobile station periodically performs an active scan for available 802.11 APs. When an AP is discovered, it may be matched against a stored profile of user preferences and security credentials, in which case the mobile station may automatically associate with the AP. The mobile station may enter low-power sleep mode, waking up periodically to measure signal quality for determining when to trigger UMA registration.

[00145] Ln one embodiment, the UMA environment may be a Bluetooth environment. In this case, the mobile station previously paired with the Bluetooth AP through which it will access UMA service. Periodically, the mobile station may enter a page scan receive mode, and respond to an AP transmit page to establish a link-level connection. Once a link-level control channel is established, and if the mobile station is not otherwise active, it may enter a low-power Bluetooth state (e.g., park mode) to conserve power. Periodically, the AP may poll the mobile station to allow it to re-enter active- power mode. This periodic traffic may also be used by the mobile station to measure signal quality to determine when to perform the UMA registration procedure. UMA Mobile Station Dedicated Mode Behavior [00146] A UMA device engaged in a voice call, a data transaction or a simultaneous voice/data transaction may encounter a transition from GSM coverage to UMA coverage or a transition from UMA coverage GSM coverage. In one embodiment, when the coverage transitions from GSM to UMA coverage, calls may be handed over transparently between the GSM RAN and the UMAN. Ln the case of voice, the handover may be accomplished by a handover function. Ln the case of data, session management controls may provide a common end- user experience to that provided in GPRS. Normal registration actions may occur upon a return to the idle state, if appropriate. Ln one embodiment, when the coverage transitions from UMA to GSM coverage, calls may be handed over transparently between the UMAN and the GSM RAN. In the case of voice, the handover may be accomplished by a handover function. In the case of data, session management controls may provide a common end-user experience to that provided in GPRS. Summary of. Key Mobility Management Concepts [00147] Figure 30 illustrates mobility management functions in one exemplary embodiment. In Figure 30, unlicensed network controller UNC-1 is the serving

UNC for the UMA cells associated with GSM location areas LA-11 to LA-23.

UNC-1 maps GSM location areas LA-lx to UMA cell UMA CGI-101 and GSM location areas LA-2x to UMA CGI-102. Unlicensed network controller UNC-3 is the serving UNC for the UMA cells associated with GSM location areas LA-31 to LA-33. UNC-3 maps GSM location areas LA-3x to UMA cell UMA CGL-301. Mobile station MS-1 will be in UMA cell UMA-CGI-101 (since GSM LA-lx is mapped to UMA-CGI-101). Mobile station MS-2 will be in UMA cell UMA- CGI- 102 (since GSM LA-2x mapped to UMA-CGI- 102). Mobile station MS-3 will be in UMA cell UMA-CGI-301 (since GSM LA-3x mapped to UMA-CGI- 301). If mobile station MS-4 connects to UNC-1, it will be in UMA cell UMA- CGL-199 (no GSM coverage). Lf MS-4 connects to UNC-3, it will be in UMA cell UMA-CGI-399 (no GSM coverage). Mobile stations MS-1 and MS-2 may connect to UNC-1 without redirection. If mobile station MS-3 attempts to connect to UNC-1, it may be redirected to UNC-3. EMERGENCY SERVICES [00148] As described in detail below, location area identification may be used to support UMA-based emergency services. When a wired caller dials 911 , the address and phone number of the caller are displayed on a screen at the 911 service center. Enhanced 911 (E911) provides dispatchers with the location of callers and their phone number. This is also known as automatic number information (ANI) and automatic location information (ALI). The FCC has ordered wireless service providers to address the issue in an effort to improve 911 calling from mobile phones.

[00149] Ln phase one of the E911 requirements, wireless service providers are required by the FCC to have the capability to send wireless 911 calls to an E911 public safety answering point (PSAP) containing the location of the cell tower through which the E911 call was processed and the mobile directory number (MDN) or "call back number" of the wireless phone placing the 911 call. In UMA, the emergency call is handled like a normal GSM emergency call origination. The MSC inserts the location identifier into the call signaling to the E911 tandem, the call and location identifier are delivered to the PSAP, and the PSAP uses the identifier to look up the cell site's location in the ALI database. The granularity of the UMA cell may be chosen to allow appropriate PSAP routing and comparable size as a GSM cell (for reasonable location resolution). [00150] In phase two of the E911 requirements, wireless service providers are required by the FCC to have the ability to send the caller's actual location to the E911 PSAP. The location accuracy requirements differ depending on whether a network-based or handset based approach is chosen. The network-based accuracy requirement is within 300 meters 95% of the time and within 100 meters 67% of the time. The handset based accuracy requirement is within 150 meters 95% of the time and within 50 meters. The UMA network provides latitude and longitude information for the AP that is routing the UMA mobile station emergency call. This may be done statically (e.g., by manually entering the location information for all the APs intended to be used for UMA service) or dynamically (e.g., using DHCP to obtain location information for a serving AP). GSM E911 Phase One Solution [00151] In one embodiment of a GSM E911 phase one solution, a BSC receives a GSM 04.08 CM service request message that indicates an emergency call establishment request from the mobile station. The BSC forwards the message to the MSC in a GSM 08.08 BSSMAP complete layer 3 information (CL3I) message. The BSC may include the cell global identifier (CGI) associated with the serving cell in the CL3I message. The MSC (or associated emergency services support system) may map the CGI value it receives from the BSC into the Emergency Services Routing Number (ESRN) that is statically associated with the cell. The ESRN may be represented as a 10-digit NANP number, and may also be referred to as the pseudo-ANI, or pANI. The MSC may send the call, with the ESRN, to an E911 tandem switch, which may use ESRN to query a selective routing database to come up with an emergency service number (ESN). The E911 tandem may use the ESN to route the call to the appropriate PSAP, including the calling user's MSISDN in the ISUP calling party number parameter and the ESRN in the ISUP generic digits parameter. The PSAP may use the ESRN to query an ALI database that may return the geographic address associated with the cell.

[00152] It will be appreciated by one of ordinary skill in the art that other specific embodiments are possible. In general, the information needed for phase one E911 support is the cell identifier that may be provided by the BSC to the MSC. By a series of transformations in the core network, the cell identifier may be mapped into an ESRN value, which the PSAP may use to query an ALI database to determine the geographic location information associated with the cell. GSM E911 Phase Two Requirements [00153] A GSM 1900 approach to E911 phase two support is defined in J- STD-036-A, "Enhanced Wireless 9-1-1, Phase 2." The condensed network reference model is illustrated in Figure 31 and described below. The Base Station Subsystem (BSS) receives the emergency call from the mobile station and notifies the visited MSC (VMSC). The BSS is also involved in the handling of certain positioning procedures. The emergency services message entity (ESME) routes and processes the out-of-band messages related to emergency calls. This may be incorporated into selective routers (also known as routing, bridging and transfer switches) and automatic location information (ALI) database engines. The emergency services network entity (ESNE) routes and processes the voice band portion of the emergency call. This is composed of selective routers (also known as routing, bridging and transfer switches). The gateway mobile location center (GMLC) contains functionality required to support delivery of a mobile's position to the ESME. The GMLC handles requests for a mobile's initial, updated (current) or last known position from the ESME. Ln one PLMN, there may be more than one GMLC. The GMLC sends positioning requests to and receives final position estimates from the visited MSC via the Lg interface. The GMLC stores the initial position estimate to support a non-call associated signaling (NCAS) pull operation (when the ESME requests the position from the GMLC). The serving mobile location center (SMLC) manages the overall coordination and scheduling of resources required to determine a mobile's position. For some position methods, it also calculates the final position estimate and accuracy. In one PLMN, there may be more than one SMLC. As described in 3GPP TS 03.71, two types of SMLC are possible; NSS based SMLC, which supports the Ls interface, and BSS based SMLC, which: supports the Lb interface. An NSS based SMLC supports positioning of a target mobile station via signaling on the Ls interface to the visited MSC. A BSS based SMLC supports positioning via signaling on the Lb interface to the BSC serving the target mobile station. Both types of SMLC may support the Lp interface to enable access to information and resources owned by another SMLC. A location measurement unit (LMU) makes radio measurements to support the determination of a mobile's position. All position and assistance measurements obtained by an LMU are supplied to a particular SMLC associated with the LMU.

The procedures associated with location determination for emergency service purposes are described in 3GPP TS 03.71. UMA Solution for E911 Phase One [00154] Ln one embodiment, UMA elements (e.g., mobile station and UNC) may be transparent for E911 calls that require phase one location. In one embodiment, the call may be handled like a normal emergency call origination.

The MSC inserts the UMA cell's location identifier (ESRN) into the call signaling to the E911 tandem, the call and location identifier may be delivered to the PSAP, and the PSAP may use the identifier to look up the cell site's location in the ALI database. In one embodiment, a UMA cell may be defined to encompass a set of GSM location areas belonging to the MSC to which a UNC is attached. However, the serving area of the resulting UMA cell may be too large to provide reasonable granularity for emergency services. For example, if the UMA cell is sufficiently large, it may map to more than one PSAP, which may complicate PSAP routing.

[00155] The partitioning of a physical UMA coverage area associated with a UNC, into multiple UMA cells, is described above under mobility management. As described therein, when a UMA mobile station connects to the UNC for UMA service, it may provide the GSM cell information to the UNC. The UNC may then map the GSM cell information to a corresponding UMA cell's CGI value. This may be a one-to-one mapping (e.g., if there is one UMA cell per GSM cell) or a many-to-one mapping (e.g., if there is one UMA cell per PSAP routing area or one UMA cell per GSM location area). If no GSM coverage is available in the UMA service area, the UNC assigns the mobile station to a default "no GSM coverage" UMA cell, subject to refinement based on AP location information, that may be provided for E911 phase two purposes, as described below. The UNC may provide the UMA CGI to the MSC during call establishment, including an emergency call. The MSC (or associated emergency services support system) may map the UMA CGI value into an ESRN value that may be statically associated with the cell, and that has an entry in the ALI database. For example, if there is one UMA cell per GSM cell, then the ESRN for the existing GSM cells is reused and no new ALI database records are needed. Ln one embodiment, partitioning of the UNC coverage area into UMA cells may be eliminated if the UNC supports E911 phase two and the core network emergency services support systems can map the provided latitude/longitude to a geographic address that can be looked up in the ALI database by a phase one PSAP UMA Solution for E911 Phase Two [00156] In one embodiment, the UNC determines the location information for the AP that the mobile station uses to access the UMA service. When the UMA mobile station performs the UMA registration procedure described above, one of the parameters that the UNC provides to the mobile station in the response may be a "location available" indicator. If the UNC does not have a location estimate

(i.e., latitude and longitude) for the AP, then the indicator is set to "no location is available." Otherwise, the indicator is set to "location is available". "No location is available" would typically be the case the first time the UMA mobile station connects to the UNC for service. Ln that case, the user may be informed of the setting of the "location available" indicator via a user interface icon on a display screen in the mobile station. The mobile station may provide a convenient way for the user to access an "enter UMA location" function. Invocation of this function may enable the user to enter street address information associated with the current location. Once entered, the mobile station may send this information to the UNC. The UNC may process the information (e.g., performs a geocoding operation) to attempt to derive a location estimate. If this procedure results in the creation of a location estimate for the AP, then the UNC may store this information in the AP record, which may also include the AP-LD. When a location estimate is added to an AP record, and the associated AP is serving one or more UMA mobile station, the UNC may send a message to each mobile station with the location available indicator set to the value "location is available." The user may be informed of the change in the setting of the "location available" indicator via a change to the user interface icon on the mobile station display screen. The description above is for an embodiment involving user- entered AP address information.

[00157] In another embodiment, the WLAN access network supports new location capabilities (e.g., those based on DHCP GEOPRLV extensions, as described in ETF Internet Draft: "draft-ietf-geopriv-dhcp-civil-01") that provide the street address or geographic location of the AP to the mobile station, and the mobile station may pass this information to the UNC when it connects for UMA service. In one embodiment, the mobile station contains GPS technology that may allow it to acquire a position estimate, which it may pass to the UNC when it connects for UMA service. Once the location information associated with the serving AP is stored in the UNC, E911 phase two location queries may be handled. In one embodiment, from the core network's perspective, the UNC may provide a BSS-based, serving mobile location center (SMLC) function. When there is a need for phase two location, the MSC may send a BSSMAP Perform Location-request message to the UNC. The UNC may retrieve the AP's location information and respond with a BSSMAP perform-location-response message containing the location estimate. In one embodiment, it may be an operator option to configure the UMA service such that emergency calls are made via GSM mode if "no location is available". This option may be configured in the UNC and the UNC may include this configuration setting in the UMA operating parameters sent to the mobile station during the UMA Registration process. [00158] It will be understood that an embodiment of the present invention relates to a computer storage product with a computer-readable medium having computer code thereon for performing various computer-implemented operations. The media and computer code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and 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") and ROM and RAM devices. Examples of computer code include machine code, such as produced by a compiler, and files containing higher-level code that are executed by a computer using an interpreter. For example, an embodiment of the invention may be implemented using Java, C++, or other object-oriented programming language and development tools. Another embodiment of the invention may be implemented in hardwired circuitry in place of, or in combination with, machine-executable software instructions. [00159] The 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. It is intended that the following claims and their equivalents define the scope of the invention.

APPENDIX I: Table Of Acronyms

Claims

What is claimed is: 1. A system comprising: a network controller operable to communicate with a telecommunications network and communicably coupled to one or more unlicensed wireless base stations comprising one or more unlicensed wireless access areas and wherein each unlicensed wireless access area is mapped to one or more licensed wireless access areas; a mobile station operable to communicate with the telecommunications network using a licensed wireless communication channel serviced by the telecommunications network in a licensed wireless access area and an unlicensed wireless communication channel in an unlicensed wireless access area, wherein the mobile station is associated with a licensed wireless network identifier and a licensed wireless location identifier for use when the mobile station is in the licensed wireless access area, wherein the mobile station is configured with an unlicensed wireless network identifier and an unlicensed wireless location identifier when the mobile station is in the unlicensed wireless access area.

2. The system defined in Claim 1 wherein the network controller provides the functions of a GSM base station controller, the unlicensed wireless access identifier comprises a GSM international mobile subscriber identity (IMSI) and the unlicensed wireless location identifier is a GSM cell location identifier.

3. The system defined in Claim 1 wherein the unlicensed wireless access area comprises an IEEE 802.11 wireless LAN (WLAN)

4. The system defined in Claim 1 wherein the base station comprises an IEEE 802.11 wireless access point, the unlicensed wireless access identifier comprises an IEEE 802.11 media access control (MAC) address and the unlicensed wireless location identifier is a register location of the wireless base station.

5. The system defined in Claim 1 wherein the wireless access area comprises a Bluetooth personal LAN (PLAN).

6. The system defined in Claim 1 wherein the network controller provides the functions of a serving GPRS (SGPRS) support node, the unlicensed wireless access identifier comprises a GPRS temporary logical link identifier (TLLI) and the unlicensed wireless location identifier is a GSM cell location identifier.

7. The system defined in Claim 1 wherein the base station is operable to provide a location identifier to a public safety access point via the network controller when the mobile station initiates an emergency services call over the unlicensed wireless communication channel.

8. The system defined in claim 7 wherein the location identifier is a GSM cell location obtained by the mobile station via the licensed wireless communication channel.

9. The system defined in claim 7 wherein the location identifier is a location programmed into the network controller.

10. The system defined in Claim 7 wherein the location identifier is programmed by a DCHP server from the telecommunications network.

11. A method comprising: communicating with a telecommunications network using an unlicensed wireless communication channel in one or more unlicensed wireless access areas serviced by one or more corresponding unlicensed wireless base stations; mapping the one or more unlicensed wireless access areas to one or more licensed wireless access areas communicably coupled with the telecommunications network; communicating with the telecommunications network using the licensed wireless communication channel in the one or more licensed wireless service areas, wherein each of the one or more licensed wireless service areas is associated with a licensed wireless network identifier and a licensed wireless location identifier for use when a mobile station uses the licensed wireless communication channel,and wherein each of the one or more unlicensed wireless service areas is associated with an ulicensed wireless network identifier and an ulicensed wireless location identifier for use when the mobile station uses the unlicensed wireless communication channel.

12. An apparatus comprising: a mobile station operable to communicate with a telecommunications network using a licensed wireless communication channel serviced by the telecommunications network in a licensed wireless access area and an unlicensed wireless communication channel in an unlicensed wireless access area, wherein the mobile station is associated with a licensed wireless network identifier and a licensed wireless location identifier for use when the mobile station is in the licensed wireless access area, wherein the mobile station is configured with an unlicensed wireless network identifier and an unlicensed wireless location identifier when the mobile station is in the unlicensed wireless access area.