HK1148156B - Self-configurable small base station - Google Patents

Description

Self-configuring small base station

Cross Reference to Related Applications

The priority of U.S. provisional patent application No.60/965,116 entitled "GSM FLATRAN PLUG & PLAY FORGUARD BAND MNOS", filed on 17.8.2007, and incorporated herein by reference; this application also claims priority from U.S. provisional patent application No.60/965,193 entitled "UMTS field lplug & PLAY SYSTEM lubricants," filed on 8, 17, 2007, and incorporated herein by reference.

Technical Field

The present invention relates to mobile communication technology, and more particularly, to a self-configuring small base station.

Background

In a conventional macro cellular mobile telecommunications network, access to mobile telecommunications services is provided within the coverage area served by a large base station by deploying the base station. A typical macrocell base station is a physical device that includes a transmission tower or other structure on which one or more antennas are provided, and other equipment for providing connectivity to a core mobile telecommunications network associated with the base station. Careful planning typically involves selecting the radio frequencies, channels, codes and other resources to be used by such macro cellular base stations, while experienced engineers and technicians typically spend a lot of time building base stations and deploying and configuring the associated equipment.

Femtocells and other small scale base stations are used to support mobile telecommunications subscriber access to and/or provide dedicated bandwidth for mobile telecommunications subscribers in remote or unserviceable areas or service areas. Femtocells and other small scale base stations can be deployed anywhere in contrast to macrocells, and many such base stations, each of which provides a small coverage area, are in many cases deployed simultaneously within an area served by one or more macrocells. Each femtocell must be configured to connect to and provide access to mobile telecommunications services via a mobile telecommunications network, and each femtocell will also allocate and use RF and other resources that do not interfere with other equipment or cause other problems.

Mobile telecommunications user equipment, such as cellular telephones, personal digital assistants, and the like, are typically sold through retail stores operated by mobile network operators and/or other institutions or partners. Sales personnel working at these retail stores are typically trained on how to expose user equipment functionality, how to configure the phone so that it can work with the mobile network operator's network, collect user information necessary to provide services and collect charges from the user, etc. Such sales personnel typically do not have the relevant level of knowledge or skill of engineers and technicians in the planning and configuration and deployment of the macrocell base station.

Drawings

Various embodiments of the invention are disclosed in detail in the following detailed description and the related figures.

FIG. 1 is a logical block diagram of an embodiment of the system of the present invention that provides access to a small base station of a universal mobile telecommunications system (UMST);

FIG. 2 is a logical block diagram of an embodiment of a Public Land Mobile Network (PLMN) of the present invention for providing access to a UMTS mobile telecommunications network through one or more small base stations (e.g., femtocell base stations);

FIG. 3 is a logical block diagram of an embodiment of the system of the present invention that provides access to a small base station of the Global System for Mobile communications (GSM);

FIG. 4 is a logical block diagram of an embodiment of a Public Land Mobile Network (PLMN) of the present invention for providing access to a GSM mobile telecommunications network through one or more small base stations (e.g., femtocell base stations);

FIG. 5 is a flow diagram of one embodiment of a small base station or other Customer Premise Equipment (CPE) implementing the self-configuration process of the present invention at initialization and/or connection time;

fig. 6 is a schematic diagram of an embodiment of a technique to deploy and provide femtocell base stations or other mobile telecommunications Customer Premise Equipment (CPE) self-configuration functionality;

fig. 7A is a schematic diagram of a CPE configuration table or other data storage space for storing configuration data on a UMTS femtocell;

fig. 7B is a schematic diagram of a CPE configuration table or other data storage space for storing configuration data on a GSM femtocell;

figure 8A is a schematic diagram of an embodiment of a high capacity configuration table applied to a UMTS femtocell;

figure 8B is a schematic diagram of an embodiment of a bulk configuration table applied to a GSM femtocell;

figure 9A is a schematic diagram of an embodiment of an access control database table applied to UMST femtocells;

FIG. 9B is a diagram of an embodiment of an access control database table applied to a GSM femtocell;

fig. 10A is a diagram of an embodiment of an access control table applied to a UMST femtocell;

figure 10B is a schematic diagram of an embodiment of an MSC server access control table as applied to a GSM femtocell;

FIG. 11A is a flowchart of an embodiment of a process for associating customer premises data (customer premise data) with a CPE point of sale;

FIG. 11B is a flow diagram of one embodiment of an implementation process for automatically mapping information collected at a CPE point-of-sale to CPE configuration data;

FIG. 12A is a schematic diagram of an embodiment of a UMTS access control database table that has been loaded with CPE data;

FIG. 12B is a schematic diagram of an embodiment of a GSM access control database table that has been loaded with CPE data;

FIG. 13 is a flow diagram of one embodiment of a UMTS CPE self-discovery and self-configuration process;

FIG. 14 is a flow diagram of an embodiment of a process for providing limited initialization data to a UMTS CPE;

fig. 15 is a flow diagram of one embodiment of a process for loading CPE configuration data at an access point;

FIG. 16A is an effect diagram of the EMS CPE configuration data table 802 of FIG. 8A populated with the Fcid field;

FIG. 16B is an effect diagram of the EMS CPE configuration data table 802 of FIG. 8A populated with both Fcid and scrambling code fields;

fig. 17 is a diagram of the local CPE configuration table 702 of fig. 7A during UMTS CPE (e.g., femtocell) self-configuration;

fig. 18 is a schematic diagram of the access point CPE configuration data table 1002 of fig. 10A loaded by the AN during CPE initialization process with reference to fig. 15;

FIG. 19 is a flow chart of a GSM CPE self-discovery and self-configuration process;

FIG. 20 is a flow chart for providing GSM CPE initialization data;

fig. 21 is a flow chart of loading CPE configuration data on the MSC server;

FIG. 22 is a schematic illustration of the high volume CPE configuration data 842 of FIG. 8B loaded by an EMS or other node;

fig. 23 is a schematic diagram of a local CPE configuration table 704 loaded by a GSM CPE during a self-configuration process;

fig. 24 is a schematic diagram of the MSC server CPE configuration data table 1042 of fig. 10B loaded by the MSC server during CPE initialization with reference to fig. 21.

Detailed Description

The invention can be implemented in numerous ways, including as a process, an apparatus, a system, a composition of matter, a computer program product written on a computer readable storage medium and/or a processor such as a processor for executing instructions stored in a memory or a processor of instructions provided by a memory coupled to a processor. These implementations, or any other form of implementation that the invention may take, are intended to be techniques in the present invention. In general, the order of the steps in the disclosed processes may be modified within the scope of the present invention. Unless otherwise specified, a component for performing a task, such as a processor or a memory, may be implemented using a general component that is temporarily configured to perform the task at a given time, or may be implemented using a specific component that is dedicated to performing the task. As used herein, the term "processor" refers to one or more devices, circuits, and/or processing cores that process data, such as computer program instructions.

One or more embodiments of the present invention are provided below in connection with the appended drawings for describing the subject matter of the present invention. The invention is described in connection with these embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous adaptations, modifications and equivalents. Numerous implementation details are provided below to provide a thorough understanding of the present invention. These details are provided for the purpose of describing the invention by way of example and the invention may be practiced according to the claims without some or all of these specific details. For clarity of description, technical material that is known in the art is not described in detail so as not to unnecessarily obscure the present invention.

The invention provides a self-configuring small base station. In some embodiments, such a small base station, when connected to an Internet Protocol (IP) or other network, such as the internet, will automatically discover a registration server or other device associated with the mobile telecommunications network. The small base station will automatically assign, without human intervention, one or more resources and/or other initialization data that the small base station uses to configure itself during operation. In some embodiments, the distribution process is based at least in part on user information collected at and/or associated with the point-of-sale (where the small base station is sold, provided, rented, etc.). The small base station uses the allocated resources and/or other initialization information to configure itself for operation so that it can be used to communicate over the mobile telecommunications network. Examples of allocated resources include Radio Frequency (RF) channels and/or scrambling codes. In some embodiments, the small scale base station scans the local RF environment to determine whether candidate, potential, and/or allocated resources are suitable for use at a particular location (i.e., e.g., the location where the small scale base station is installed) to determine whether using the resources may cause interference to one or more other small and/or macro cell base stations or other transmitters operating in the same environment.

Fig. 1 is a logical block diagram of an embodiment of the system of the present invention that provides access to a small base station of a universal mobile telecommunications system (UMST). In the illustrated embodiment, user equipment 102, such as a UMTS mobile phone, communicates over a Uu air interface with UMTS Access Points (UAPs) 104, which in some embodiments may each comprise a small base station. The access point 104 is in this embodiment connected via an IP network 106, e.g. the internet, to a UMTS Backend Server (UBS)108, which is arranged to provide a connection to a UMTS network device 110 via a corresponding interface as illustrated in fig. 1.

Fig. 2 is a logical block diagram of an embodiment of a Public Land Mobile Network (PLMN) of the present invention for providing access to a UMTS mobile telecommunications network through one or more small base stations, such as femtocell base stations. In the illustrated embodiment, each of the plurality of femtocells 202 provides coverage service within a relatively small coverage area. The femtocell base station 202 provides coverage service in an area also served by a macro cellular network represented in figure 2 by a coverage area 208 and an associated macro cellular network PLMN 210. Each of the femtocell base station network PLMN 206 and the macro network PLMN210 is connected to a backbone network 212 through a Gateway Mobile Service Center (GMSC) 214. The femtocell network PLMN 206 includes a Femtocell Gateway (FGW)216, a Registration Server (RS)218, and a device management server (EMS)220, which in some embodiments are disposed in one or more physical systems ("boxes"), such as the UMTS backend server 108 in fig. 1. As shown in fig. 2, femtocell base station 202 is connected to FGW 216 and RS 218 through internet 204. RS 218 is used in some embodiments to establish a connection to a femtocell (or other small base station) during an initialization process (e.g., after purchase by a user), which connects to an internet connection, and initializes, for authenticating the femtocell in some embodiments, and to provide or assist in providing femtocell configuration data used by the femtocell in performing a self-configuration process. EMS220 receives an identifier, e.g., MAC address, via RS 218, associated with the registering femtocell 202, and EMS220 queries Access Control Database (ACDB)222 for configuration data, e.g., RF channels, code groups, and/or candidate scrambling codes (which have not been assigned to other femtocells and are suitable for use at the geographic location where the femtocell is installed, e.g., the address of the purchasing user collected at the point of sale) to be applied to the femtocell. Once the femtocell completes self-configuration, the FGW 216 establishes a secure channel connection to a Mobile Switching Center (MSC)224, which in some embodiments becomes a femtocell aggregator or tandem node. The MSC 224 is used to provide access to mobile telecommunications services to the femtocell base station and associated user equipment through the secure tunnel established by the FGW 216 and the MSC's connection to the backbone network 212. The remaining devices in fig. 2 operate in a typical umts plmn mode.

Figure 3 is a logical block diagram of an embodiment of the system of the present invention that provides access to a small base station of the global system for mobile communications (GSM). In the illustrated embodiment, a Mobile Station (MS)302 communicates with a GSM Access Point (GAP)304 (e.g., a femtocell) over a Um air interface. Each GAP 304 is connected via an IP network 306, e.g. the internet, to a GSM/GPRS back end server (GBS)308 for providing access to a Mobile Network Operator (MNO) core network 310 via an a (voice) and Gb (packet data) interface.

Fig. 4 is a logical block diagram of an embodiment of a Public Land Mobile Network (PLMN) of the present invention for providing access to a GSM mobile telecommunications network through one or more small base stations, such as femtocell base stations. In the illustrated embodiment, each of a plurality of femtocells 402 is connected to a femtocell network PLMN 406 through the internet 404. The femtocell base station 402 provides coverage service in an area also served by the macro cellular network represented in figure 4 by the macro network PLMN 408 and coverage area 410. In the illustrated embodiment, the femtocell network PLMN 406 includes a Femtocell Gateway (FGW)412, a Registration Server (RS)414, and an Equipment Management Server (EMS) 416. In some embodiments, RS 414 and EMS 416 operate in the same manner as the corresponding devices in fig. 2, with corresponding modifications only to the GSM environment. The EMS 416 is connected to an Absolute Radio Frequency Channel Number (ARFCN) database 418, which in some embodiments is used to implement multiple MNOs to coordinate the allocation of RF channels to accommodate actual usage during femtocell operation, such as in the uk licensed GSM guard band. The EMS 416 is also connected to an Access Control (AC) database 420, which in some embodiments is used to ensure that only authorized users are able to access the mobile telecommunications network through the femtocell, such as users who are generally authorized to use the femtocell and/or authorized users of a particular femtocell that must be passed through in attempting to establish a communication. The FGW 412 is used to aggregate traffic from the mobile systems associated with the plurality of femtocell base stations 402 and provide connectivity to the macro network PLMN 408 through the MSC server 422 and Media Gateway (MGW) 424.

Although the embodiments shown in fig. 1-4 illustrate UMTS and GSM networks, the techniques described herein may also be applied in other mobile telecommunications networks where small base stations or similar access points are used to provide access to mobile telecommunications services.

Before sale

Fig. 5 is a flow diagram of an embodiment of a small base station or other Customer Premise Equipment (CPE) implementing the self-configuration process of the present invention at initialization and/or connection time. In the illustrated embodiment, prior to selling the CPE (e.g., femtocell or other small base station), it may be configured to automatically discover a registration server or other node, for example, upon first connecting to the internet and/or another public or private IP network, receive initialization data (e.g., a resource or pool of resources, such as a code group) over the IP network, and use the received initialization data to configure itself for mobile telecommunication base station operation (502). In various embodiments, the CPE is configured to operate by configuring itself with minimal resources or other initialization data received when first connected to an IP or other network, in conjunction with other information determined by the CPE itself as determined by scanning the surrounding RF environment. In some embodiments, the CPE is configured by the OEM, MNO, and/or other entity prior to distribution (e.g., sale, lease, offer, mortgage, or otherwise) to the retail location for distribution to the end user, e.g., by setting a femtocell id (fcid) or other identifier and/or logic used by the CPE in performing auto-discovery and self-configuration (502). The CPE configuration table or other data space will be configured in advance, in a large manner, with multiple sets (e.g., rows) of configuration data set, each set containing available resources (504) associated with the CPE at registration time. Examples of such resources include code sets, scrambling codes, and RF channels. In some embodiments, initialization data destined for a registered CPE during a registration process is selected at least in part by mapping an identifier (e.g., MAC address or other FCid) received from the CPE and associated therewith to a geographic location (e.g., a premise address collected at a point-of-sale), and selecting an available configuration data set from a large configuration table based at least in part on the geographic location (described in detail below).

Fig. 6 is a schematic diagram of an embodiment of a technique to deploy and provide femtocell base stations or other mobile telecommunications Customer Premise Equipment (CPE) self-configuration functionality. In the illustrated embodiment, the CPE's Original Equipment Manufacturer (OEM) and/or vendor and/or Mobile Network Operator (MNO) of the mobile telecommunications network with which the CPE is to be used (602) pre-configures the CPE to auto-discover a mobile network registry server or other device, as described above, and automatically self-configure using limited resources and/or other initialization information (provided by the mobile network). At the point-of-sale (604), the purchasing subscriber provides the address of the mobile subscriber premises (606) (where the CPE device is to be used) and/or other account information to a retail sales associate or other representative, which then provides a CPE device identifier (e.g., a MAC address, referred to in some embodiments as "FCid" to represent "femtocell id"), subscriber premises address and/or other information such as a phone number, IMSI, TMSI, and/or other identifiers of subscribers and/or other subscribers allowed to access the network via the CPE device, to the mobile network (608), for example, by providing the information to the point-of-sale, account, and/or access control and/or CPE device control database. In some embodiments, a Graphical User Interface (GUI) or other input interface is provided to retail personnel (604) at the point of sale so that the personnel can capture and submit the required information without requiring a higher level of skill and training. In some embodiments, the retail sales processing system prevents the purchase (or other) transaction from completing until an acknowledgement is received indicating that the CPE address and white list (authorized user) information has been obtained and successfully submitted to the mobile network (608). The CPE, upon first connecting to the mobile network via a network connection (610) to a connecting network of the non-mobile telecommunications network (e.g., the internet or other public or private IP network), automatically discovers the registered nodes, receives initialization data, and then automatically configures as described herein.

Fig. 7A is a schematic diagram of a CPE configuration table or other data storage space for storing configuration data on a UMTS femtocell. In the illustrated embodiment, the CPE configuration data table 702 includes locations for storing the following information: "FCid" or "femtocell id" (which is an identifier (e.g., MAC address) uniquely associated at least locally with the CPE, which in some embodiments is stored in the SIM or other security module with the security key); a Mobile Country Code (MCC) (CPE is authorized in that country and has been configured to be available); a Mobile Network Code (MNC) (which is associated with a mobile operator with which the CPE is used); a Location Area Code (LAC) (associated with a location area used by the CPE); a Cell Identifier (CI) that identifies the cell with which the CPE is associated using a Location Area (LA); UMTS Absolute Radio Frequency Channel Number (UARFCN) (which indicates the channel used by the CPE broadcast); a code set (which is associated with a scrambling code to be used by the CPE); a scrambling code assigned for use by the CPE; neighbor (NB) cell list (with which CPE needs to hand over active calls if needed).

Fig. 7B is a schematic diagram of a CPE configuration table or other data storage space for storing configuration data on a GSM femtocell. In the illustrated embodiment, the CPE configuration data table 742 includes locations for storing the following information: "FCid" or "femtocell id" (an identifier uniquely associated at least locally with the CPE, such as a MAC address, which is stored in the SIM or other security module of the CPE in some embodiments, along with a security key); a Mobile Country Code (MCC) (where the CPE is authorized and/or configured to be available) a Mobile Network Code (MNC) (which is associated with a mobile operator with which the CPE is used); a Location Area Code (LAC) (associated with a location area used by the CPE); a Cell Identifier (CI) that identifies the cell with which the CPE is associated using a Location Area (LA); a Base Station Identifier Code (BSIC) (the femtocell broadcasts the identifier on a synchronization channel); absolute radio frequency channel number (which indicates the channel broadcast by the CPE); neighbor (NB) cell list (with which CPE needs to hand over active calls if needed).

Fig. 8A is a diagram of an embodiment of a high capacity configuration table applied to a UMTS femtocell. Mass configuration table 802 is, in some embodiments, stored on or by an Equipment Management Server (EMS), such as EMS220 of FIG. 2, and/or on one or more other nodes that provide configuration to femtocells or other CPEs when they register to enable them to configure themselves to operate with the mobile telecommunications network The routing area of (a); a Mobile Country Code (MCC); a Mobile Network Code (MNC); a Location Area Code (LAC); a Cell Identifier (CI); UMTS absolute radio frequency channel number (UARFCD); code group; FCid or other unique identifier of a CPE (to which the above-mentioned resource and/or configuration data is assigned); scrambling codes (allocated for use by CPEs identified by FCid). The FCid and scrambling code columns are completed after each set of resource allocations, row by row, during CPE registration and self-configuration, as will be described in detail below.

Fig. 8B is a diagram of an embodiment of a bulk configuration table applied to a GSM femtocell. The mass configuration table 842, in some embodiments, is stored in or by a device management server (EMS), such as EMS 416 in fig. 4, and/or on one or more other nodes that are used to provide configurations to femtocells or other CPEs when they register so that they can configure themselves to operate with the mobile telecommunications network. In the illustrated embodiment, the bulk configuration table 842 appears in a state in which resources that may be allocated to registered CPEs have been identified, but no set (row) of resources has been allocated to any particular CPE, which in this embodiment has the effect that any value in the "FCid" column is empty. In this embodiment, the large capacity configuration table 842 includes columns for storing the following information for each set of resources and/or configuration data: a routing area where the resource is to be used and/or where the CPE to which the resource is allocated is located; a Mobile Country Code (MCC); a Mobile Network Code (MNC); a Location Area Code (LAC); a Cell Identifier (CI); base Station Identifier Code (BSIC) (which the femtocell will broadcast on the synchronization channel); code group; FCid or other unique identifier of a CPE (to which the above-mentioned resource and/or configuration data is assigned); absolute Radio Frequency Channel Number (ARFCN) (assigned for use by the CPE identified by the FCID).

Figure 9A is a schematic diagram of an embodiment of an access control database table applied to UMST femtocell. In some embodiments, access control database table 902 is stored in an access control database, such as ACDB 222 in fig. 2. In the illustrated embodiment, table 902 includes storage locations for storing: CPE identifier (FCid); a customer address indicating a customer premises where the CPE is to be installed and operated); a routing area (to which the CPE is associated); an Access Control White List (ACWL) identifying each user equipment that has been authorized to access the mobile telecommunications network through the CPE by an International Mobile Subscriber Identifier (IMSI).

Fig. 9B is a diagram of an embodiment of an access control database table applied to a GSM femtocell. In some embodiments, the access control database table 942 is stored in an access control database, such as the AC 420 in FIG. 4. In the illustrated embodiment, table 902 includes storage locations for storing: CPE identifier (FCid); a customer address indicating a customer premises where the CPE is to be installed and operated); a routing area (to which the CPE is associated); an Access Control White List (ACWL) identifying each user equipment that has been authorized to access the mobile telecommunications network through the CPE by an International Mobile Subscriber Identifier (IMSI) and a Temporary Mobile Subscriber Identity (TMSI).

Fig. 10A is a diagram of an embodiment of an access control table applied to a UMST femtocell. In some embodiments, a network node configured to control access to a mobile telecommunications network (e.g., MSC 224 in fig. 2) maintains a table 1002 shown in fig. 10A. In the illustrated embodiment, for each CPE (e.g., each row), access control table 1002 includes: FCid; a routing area; MCC; MNC; LAC; CI; and ACWL (IMSI). In various embodiments of the present invention, an MSC configured to provide access control to a mobile network to femtocell users uses the data in table 1002 to ensure that only authorized users are allowed to use the femtocell.

Figure 10B is a diagram of an embodiment of an MSC server access control table as applied to a GSM femtocell. In some embodiments, an MSC server, such as MSCs 422 in fig. 4, maintains table 1042 in fig. 10B. In the illustrated embodiment, for each CPE (e.g., each row), the access point table 1002 includes: FCid; a routing area; MCC; MNC; LAC; CI and ACWL (IMSI and TMSI).

Point of sale

Fig. 11A is a flow diagram of an embodiment of an operational procedure for associating customer premises data with a CPE point of sale. In the illustrated embodiment, the customer premises address where the CPE device is to be used is obtained and entered via a graphical user interface or other interface (1102). For example, a retail representative asks the user for his customer premises address, then enters it into a computer or other terminal, reports the address over the telephone, copies the address to a postcard or other paper record, and so on. In some embodiments, information from which a customer premises address may be determined and/or inferred (e.g., a customer telephone number from which an account address may be determined) is collected and entered. The unique identifier (FCid) associated with the CPE may be determined by reading a document, package, tag, bookmark or other record, and/or by accessing electronically stored information or information of the CPE itself (e.g., in a SIM card or other device and entered through a user interface) and/or other reporting mechanisms (1104), such as by associating a customer premises address with the unique identifier of the CPE. Optionally, an identifier associated with an authorized user of the CPE, such as a mobile phone number, IMSI, etc., is determined and entered via the same interface in a manner that associates such authorized user with a unique identifier of the CPE (1106). The collected and entered customer premises address, CPE unique identifier and authorized user data will be submitted, which in various embodiments may be accomplished by, for example, the retail representative selecting an "enter" button or key.

Fig. 11B is a flow diagram of an embodiment of an implementation process for automatically mapping information collected at a CPE point-of-sale to CPE configuration data. In some embodiments, the flow in FIG. 11B may be performed by a local or remote node (which receives the collected and input data described in FIG. 11A). In the illustrated embodiment, the CPE unique identifier, customer premises address and authorized user information collected at the point of sale (e.g., collected when the CPE was sold) will be received (1142). The customer premises address is automatically mapped to a routing area (1144). The CPE device's access control database record is loaded (1146) with, for example, the received CPE device unique identifier, customer premises address and authorized user information, and the determined routing area. In some embodiments, the routing area may be determined at the point of sale, which is included in the information received at step 1142, while step 1144 is omitted.

Figure 12A is a schematic diagram of an embodiment of a UMTS access control database table that has been loaded with CPE data. In the illustrated embodiment, the access control database table 902 is shown as a state in which the CPE device unique identifier, user address, routing area and authorized user data have been loaded corresponding to the CPE device with an FCid of "123456789", as shown in fig. 11A and 11B.

Figure 12B is a schematic diagram of an embodiment of a GSM access control database table that has been loaded with CPE data. In the illustrated embodiment, the access control database table 942 is shown in a state where the CPE device unique identifier, user address, routing area and authorized user data corresponding to the CPE device with an FCid of "123456789" have been loaded, as shown in fig. 11A and 11B.

After sale

UMTS femtocell auto-discovery and self-configuration

Fig. 13 is a flow diagram of one embodiment of a UMTS CPE self-discovery and self-configuration process. In some embodiments, the flow in fig. 13 is implemented by a UMTS femtocell or other small base station. In the illustrated embodiment, in an initial step (1302), the CPE automatically discovers the Registration Server (RS) associated with the UMTS mobile telecommunications network with which the CPE is to operate, performs an authentication operation, and sends its FCid (or other unique identifier) to the RS (1304). In some embodiments, the CPE is pre-configured to automatically discover the RS, for example using a URL (e.g., http:// register. [ mno or other domain name ]. Com) or other identifier associated with the RS on the network through which the CPE will connect to a mobile network, such as the Internet or another IP network. In response, the CPE receives resources and/or other initialization data from the RS, either directly or indirectly from the relevant node (e.g., EMS) (1306). In some embodiments, the initialization data includes one or more RF or other resources available to the CPE, such as resources determined by the EMS or other node using the large capacity configured CPE configuration data set. Examples of initialization data include UARFCN, code group and/or one or more assigned and/or candidate scrambling codes. The CPE selects a scrambling code, e.g., based at least in part on the scanning for the RF environment, and reports the selected scrambling code to the mobile network (1308). In some embodiments, the UMTS CPE receives the UARFCN and code group in step 1306, which is implemented by the mobile network (e.g., the EMS) at least in part by mapping the provisioned FCid to a routing area (e.g., using an access control database as described above) and selecting a row (or other set) from the high capacity configured CPE configuration data that matches the routing area and is not allocated. In some embodiments, the CPE tests one or more scrambling codes in the candidate code group and reports back to the mobile network the scrambling code selected by the CPE as being suitable or most suitable for use based on the test, step 1308. In some embodiments, the CPE tests one or more scrambling codes, reports the raw results, and the mobile network node makes the selection. Once it is known that a scrambling code selection has been received by the CPE from the mobile network (1310), the CPE configures itself to operate using the allocated and/or self-selected resources, establishes a connection to the MSC, and reports its configuration parameters to the MSC (1312). Upon receiving notification (1314) that its configuration data has been received by the MSC, the CPE enters an active state and may provide the user equipment with access to at least part of the services provided over the mobile telecommunications network (1316).

Fig. 14 is a flow diagram of an embodiment of a process for providing limited initialization data to a UMTS CPE. In some embodiments, the process in fig. 14 is implemented by one or more mobile network devices, EMS220 in fig. 2. In the illustrated embodiment, an FCid or other unique CPE device identifier is received (1402) and used to look up the customer premises address and routing area in an access control database (1404). In some embodiments, the user address and/or routing area is collected at the point of sale, and/or is subsequently determined based on information collected at the point of sale, as described above. The determined routing area is used to select the operating UARFCN and code group (1406). In addition, unused LACs and CIs belonging to a routing area will be selected and associated with the received FCid or other unique CPE identifier (1408), for example, by selecting an unoccupied row from a large capacity configured CPE configuration data table whose routing area matches the routing area with which the CPE is associated as determined at step 1404, and then populating the received FCid in the table at the corresponding location of that row. Fig. 16A is an effect diagram of the EMS CPE configuration data table 802 of fig. 8A populated with the Fcid field. The initialization data determined in steps 1406 and 1408 is sent to the CPE (1410). The scrambling code selected by the CPE based on the configuration data sent in step 1410 will be received, validated, acknowledged, and used to update the CPE configuration data table in the EMS (or other mobile network node) (1412). Fig. 16B is a diagram of the effect of the EMS CPE configuration data table 802 of fig. 8A populated with both the Fcid field and the scrambling code field.

In some embodiments, the CPE uses initialization data obtained from the EMS (fig. 14) to configure itself and connect to the mobile network through the MSC or other node (used to provide access control to the mobile telecommunications network), as shown in step 1312 of fig. 13. Fig. 17 is a diagram of the local CPE configuration table 702 of fig. 7A during a UMTS CPE (e.g., femtocell) self-configuration process. In some embodiments, the neighbor table will be loaded in one, two, or a mixture of the following cases: the CPE senses a local RF environment, and/or the mobile network identifies neighboring cells (e.g., macro cellular network base stations) based at least in part on a customer premises address associated with the CPE unique identifier.

Fig. 15 is a flow diagram of one embodiment of a process for loading CPE configuration data at an access point. In the example shown, CPE configuration data will be received (1502) and used to obtain an Access Control White List (ACWL) with CPE authorized users listed (1504). Examples include ACWL information collected at the CPE point of sale described above. In some embodiments, the FCid or other unique CPE identifier will be used to obtain the ACWL. The ACWL and received configuration data will be used to load a CPE configuration table (1506) at the AN, after which AN acknowledgement (1508) will be sent to the CPE indicating to the CPE that the AN is now available to provide access to the mobile telecommunications network through the CPE to authorized users of the UE's CPE (i.e., users on the ACWL).

Fig. 18 is a schematic diagram of the access point CPE configuration data table 1002 of fig. 10A loaded by the AN during CPE initialization process with reference to fig. 15.

b.GSM femtocell auto-discovery and self-configuration

Fig. 19 is a flow chart of a GSM CPE self-discovery and self-configuration process. In some embodiments, the flow in fig. 19 may be implemented by a GSM femtocell or other small base station. In the illustrated embodiment, at an initial step (1902), the CPE scans the RF environment to select candidate channels and/or to probe neighboring cells (1904). The CPE auto-discovers and connects to a mobile network registration node (e.g., RS) over an IP or other access network, performs authentication, and sends its FCid (or other unique identifier) and candidate RF channels (1906). The CPE receives CPE resources and/or other initialization data from the mobile network, such as the assigned ARFCN (1908), which the CPE uses to self-configure (fig. 23 is an illustration of the local CPE configuration table 704 loaded by the GSM CPE in the self-configuration process), and establishes a secure connection to the serving MSC server and reports its configuration data to the server (1912). Upon receiving an acknowledgement from the MSC server (1914), the CPE enters the active state and begins providing service to authorized users.

Fig. 20 is a flow chart for providing GSM CPE initialization data. In some embodiments, the flow in fig. 20 may be implemented by one or more mobile network devices, such as EMS 416 in fig. 4. In the illustrated embodiment, an FCid or other unique CPE identifier and 0 or more candidate ARFCNs will be received (2002). The FCid is used to look up the customer premises address and routing area in the access control database (2004). The ARFCNs to be used by the CPE are selected based on the ARFCNs available in the area and the candidate list received from the CPE (if present) (2006). The high capacity configured CPE configuration data table is used by the CPE to select unused LACs, CIs and BSICs (2008), e.g., to select the next unused row with the same routing area as the CPE. The high capacity configured CPE configuration data table is updated to associate the CPE's FCid and the allocated ARFCN with the allocated LAC, CI, and BSIC (2010). The allocated configuration data is sent to the CPE (2012). Fig. 22 is a schematic diagram of the bulk configured CPE configuration data 842 of fig. 8B loaded by an EMS or other node.

Fig. 21 is a flow chart of loading CPE configuration data on the MSC server. In the example shown, CPE configuration data will be received (2102) and used to obtain an Access Control White List (ACWL) in which CPE authorized users are listed (2104). The ACWL and received configuration data are used to load a CPE configuration table (2106) in the MSCS, after which an acknowledgement (2108) will be sent to the CPE indicating to the CPE that the MSC server is now configured to provide access to the mobile telecommunications network via the CE to the CPE authorized user of the MS (i.e., the user on the ACWL).

Fig. 24 is a schematic diagram of the MSC server CPE configuration data table 1042 of fig. 10B loaded by the MSC server during CPE initialization with reference to fig. 21.

Although the examples detailed above are all with respect to UMTS and/or GSM femtocell base stations and/or networks, the techniques described herein may also be applied to any environment in which a mobile telecommunications CPE, such as a femtocell or other small base station, needs to be installed relative to a primary end user (e.g. a mobile user), and which requires the mobile telecommunications network to allocate one or more radio frequencies (e.g. channel numbers, scrambling codes) or other resources to the CPE so that the CPE can configure itself appropriately to operate with the mobile telecommunications network.

Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details described. There are many other ways in which the invention may be practiced. The embodiments disclosed herein are merely illustrative and are not intended to be limiting.

Claims (6)

1. A mobile telecommunications base station, comprising:

a communication interface for connecting to an access network other than a mobile telecommunications network associated with the mobile telecommunications base station; and

a processor coupled to the communication interface for:

establishing a connection, at least in part, via an access network, to a registration server associated with the mobile telecommunications network, wherein the registration server authenticates the mobile telecommunications base station and provides configuration data for use by the mobile telecommunications base station in performing a self-configuration procedure, wherein a device management server receives an identifier associated with the mobile telecommunications base station via the registration server and accesses a control database for application to the configuration data of the mobile telecommunications base station,

receiving initialization data over an access network, the initialization data received when first connected to an IP or other network;

determining other information by scanning the surrounding RF environment;

configuring the mobile telecommunications base station to provide access to mobile telecommunications services using initialisation data and the further information by using resources determined at least in part on the basis of the initialisation data; and

sending traffic of a mobile system associated with the mobile telecommunications base station to a base station gateway device associated with the mobile telecommunications network for aggregation, wherein the base station gateway device provides connectivity to a macro network through a mobile switching center server and a media gateway.

2. The mobile telecommunication base station of claim 1, wherein the resources comprise one or more of the following resources: radio frequency; a wireless channel; code group; scrambling codes are added; a location area code; a cell identifier and a base station identifier code.

3. The mobile telecommunication base station of claim 1, wherein the processor is further configured to transmit a unique identifier uniquely associated with the mobile telecommunication base station to the device.

4. A mobile telecommunications base station as claimed in claim 3, wherein the mobile telecommunications network device or another node associated with the device is arranged to select the initialisation data at least partly on the basis of the unique identifier.

5. The mobile telecommunication base station of claim 1, wherein the processor is further configured to automatically discover the device associated with the mobile telecommunication network.

6. A method of configuring a mobile telecommunications base station, comprising:

establishing a connection to a registration server associated with the mobile telecommunications network via, at least in part, an access network other than the mobile telecommunications network associated with the mobile telecommunications base station, and providing configuration data for use by the mobile telecommunications base station in conducting a self-configuration procedure, wherein the registration server authenticates the mobile telecommunications base station by using a MAC address associated with the mobile telecommunications base station, a device server receives an identifier associated with the mobile telecommunications base station being registered with the registration server and queries an access control database for application to the configuration data;

receiving initialization data via the access network, the initialization data received when first connected to an IP or other network;

determining other information by scanning the surrounding RF environment;

configuring the mobile telecommunications base station to provide access to mobile telecommunications services using the initialization data and the other information by using resources determined based at least in part on the initialization data; and

sending traffic of a mobile system associated with the mobile telecommunications base station to a base station gateway device associated with the mobile telecommunications network for aggregation, wherein the base station gateway device provides connectivity to a macro network through a mobile switching center server and a media gateway.