Configuring an identifier for an access point of a femto cell

Note: Within nine months ofthe publication ofthe mention ofthe grant ofthe European patent in the European Patent Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the Implementing Regulations. Notice of opposition shall nőt be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).

Printed by Jouve, 75001 PARIS (FR) (Cont. next page)

ΕΡ 2 223 552 Β1 • HUAWEI: Detection of conflicting cell identities, 3GPP DRAFT; R2-074216, 3RD GENERATION PARTNERSHIP PROJECT(3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCÉ, vol. RAN WG2, no. Shanghai, China; 20071002, 2 October 2007 (2007-10-02), XP050136835, [retrieved on 2007-10-02]

ΕΡ 2 223 552 Β1

Description

BACKGROUND

Field [0001] This application relates generally to communication and more specifically, bút nőt exclusively, to configuring a communication node.

Introduction [0002] Wireless communication systems are widely deployed to provide various types of communication (e.g., voice, data, multimédia Services, etc.) to multiple users. As the demand fór high-rate and multimédia data Services rapidly grows, there lies a challenge to implement efficient and robust communication systems with enhanced performance.

[0003] To supplement conventional mobile phone network base stations (e.g., macro cells), small-coverage base stations may be deployed (e.g., installed in a user’s home) to provide more robust indoor wireless coverage to mobile units. Such small-coverage base stations are generally known as access point base stations, Home NodeBs, orfemto cells. Typically, such small-coverage base stations are connected to the Internet and the mobile operator’s network via a DSL router or a cable modem.

[0004] In practice, these small-coverage base stations may be deployed in an ad-hoc manner and in relatively large numbers. Consequently, there is a need fór improved techniques fór configuring such base stations. [0005] US 2005/0148368 describes a rádió base station that collects information about the network and exchanges data with a configuration device, the Internet System Manager (ÍSM).

[0006] US 2007/0254620 describes femto rádió base station node, including a reporting unit that provides scanned cell information fór one or more receivable cells ofthe rádió access network to the rádió network control node. The rádió network control node is arranged, upon receipt ofthe scanned cell information, to provide configuration information to the femto rádió base station node.

[0007] US 2007/0097939 describes configuration of a femto rádió base station. A macro receiver of the femto rádió base station is used to acquire detected coverage information of a rádió access network. The detected coverage information is transmitted to a control node ofthe rádió access network. The control node determines the operation paraméter and communicates the operation paraméter to the femto rádió base station. The femto rádió base station is accordingly configured using the operation paraméter.

SUMMARY [0008] The disclosure relates in somé aspects to configuring an access point. In various scenarios such an access point may take the form of a femto node, a relay node, a pico node, or somé other type of node.

[0009] In accordance with the invention, there is provided a method of communication according to claim 1, an apparátus according to claim 17 and a computer program product according to claim 18.

BRIEF DESCRIPTION OF THE DRAWINGS [0010] These and other sample aspects ofthe disclosure will be described in the detailed description and the appended claims that follow, and in the accompanying drawings, wherein:

FIG. 1 isasimplified block diagram of several sample aspects of a communication system where an access point is configured based on received information;

FIG. 2 is a simplified diagram illustrating sample coverage areas fór wireless communication;

FIG. 3 is a flowchart of several sample aspects of operations that may be performed to configure an access point;

FIG. 4 isasimplified block diagram of several sample aspects of components that may be employed in communication nodes;

FIG. 5 is a simplified diagram illustrating sample operations relating to neighbor discovery;

FIG. 6 is a simplified diagram illustrating sample operations relating to neighbor discovery;

FIG. 7 is a flowchart of several sample aspects of operations that may be performed to configure an access point based on the configuration of one or more neighboring nodes;

FIG. 8 isasimplified block diagram of several sample aspects of components that may be employed in communication nodes;

FIG. 9 is a flowchart of several sample aspects of operations that may be performed to configure an access point based on location;

FIG. 10 is a flowchart of several sample aspects of operations that may be performed to configure an access point based on received configuration information;

FIG. 11 is a flowchart of several sample aspects of operations that may be performed to direct an access point to a configuration server;

FIG. 12 is a simplified diagram of a wireless communication system;

FIG. 13 is asimplified diagram ofa wireless communication system including femto nodes;

FIG. 14 is a simplified block diagram of several sample aspects of communication components; and FIGS. 15-22 arcsimplified blockdiagramsof several

EP 2 223 552 Β1 sample aspects of apparatuses configured to perform configuration-related operations as taught herein.

[0011] In accordance with common practice the various features illustrated in the drawings may nőt be drawn to scale. Accordingly, the dimensions ofthe various features may be arbitrarily expanded or reduced for clarity. In addition, somé of the drawings may be simplified for clarity. Thus, the drawings may nőt depict all ofthe components of a given apparátus (e.g., device) or method. Finally, like reference numerals may be used to denote like features throughout the specification and figures.

DETAILED DESCRIPTION [0012] Various aspects ofthe disclosure arc described below. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative. Based on the teachings herein one skilled in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparátus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparátus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more ofthe aspects set forth herein. [0013] FIG. 1 illustrates several nodes in a sample communication system 100 (e.g., a portion of a communication network). For illustration purposes, various aspects ofthe disclosure will be described in the context of one or more access terminals, access points, and network nodes that communicate with one another. It should be appreciated, however, that the teachings herein may be applicable to other types of apparatuses or other similar apparatuses that are referenced using other terminology. For example, an access point as taught herein may be implemented or referred to as a base station, an eNodeB, a Home eNodeB, and so on. Alsó, an access terminál as taught herein may be implemented or referred to as a mobile, user equipment, and so on. In addition, a network node may be implemented or referred to as a configuration server; an operations, accounting, and management (OAM) entity; a mobility manager; and so on. Other sample terminology is set forth in the following discussion.

[0014] Access points in the system 100 provide one or more Services (e.g., network connectivity) for one or more wireless terminals (e.g., access terminál 102) that may be installed within or that may roam throughout an associated geographical area. Forexample, at various points in time the access terminál 102 may connect to an access point 104 or an access point 106. Each of the access points 104 and 106 may communicate with one or more network nodes (represented, for convenience, by network node 108) to facilitate wide area network connectivity. Such network nodes may take various forms such as, for example, one or more rádió and/or core network entities (e.g., implemented as discussed above or as somé other suitable network entity).

[0015] In somé aspects, configuration of an access point such as access point 104 may be advantageously achieved by providing configuration functionality at the access point. For example, in a network that has a relatively large number of access points, it may be more efficient for the overall operation ofthe network if each access point has the capability to configure itseif at least to somé extent. In this way, the operator of the network (e.g., centralized entities managed by the operator) may be relieved ofat least somé ofthe burden of determining the appropriate configurations and keeping track ofthe configurations for all of these access points.

[0016] In the example of FIG. 1, the access point 104 includes a configuration controller 110 that configures the access point 104. Here, the configuration controller 110 may provide one or more configuration parameters thatthe access point 104 uses for communication-related operations. Forexample, the configuration controller 110 may provide configuration parameters for a wireless transceiver 112 such as a pilot identifier, operating frequency, and transmit power.

[0017] In somé implementations the configuration controller 110 defines configuration parameters based on the configuration(s) of at least one other access point (e.g., a neighboring access point). To this end, the configuration controller 110 may récéivé configuration information from the other access point(s) and/or information that may be used to obtain configuration information from the other access point(s).

[0018] In somé cases the access point 104 may communicate with the access point 106 to determine the configuration ofthe access point 106. For example, the access point 104 may communicate with the access point 106 via a backhaul (e.g., through the network node 108). As a more specific example, an eNodeB may récéivé a report (e.g., via anX2 interface) of a PCI used by a neighboring eNodeB.

[0019] Alsó, the access point 104 may acquire configuration-related information directly from the access point 106 via wireless signals. For example, the access point 104 may include a downlink receiver (nőt shown in FIG. 1) that receives signals transmitted by the access point 106. As a more specific example, the PCI used by an eNodeB may be heard over-the-air at another eNodeB through the use of a downlink receiver.

[0020] The access point 104 alsó may acquire configuration-related information via an access terminál (e.g., when the access terminál 102 is being served by the access point 104). For example, the access terminál 102 may forward information it acquiresfrom the access point 106 (e.g., information derived from transmissions by the access point 106) to the access point 104. As a more

ΕΡ 2 223 552 Β1 specific example, user equipment may report the PCI used by an eNodeB to another eNodeB.

[0021] In somé cases the access point 104 may récéivé configuration-related information from the network node 108. Forexample, the network node 108 may identify any neighbors ofthe access point 104 and send this neighbor information to the access point 104. The configuration controller 110 then uses this neighbor information to determine the configuration ofthe indicated neighbor(s).

[0022] In somé cases the network node 108 sends a list of pilot identifiers to the access point 104. The access point 104 may then select its pilot identifier from the list. Fór example, the access point 104 may randomly select a pilot identifier from the list or select a pilot identifier based on a defined criterion or criteria. Here, the access point 104 may exclude any pilot identifiers used by other access points (e.g., neighboring access point) from its selection.

[0023] As a more specific example, an OAM entity may signal a list of PCI values to an eNodeB. This list may be cell specific. The eNodeB may then select a PCI value fór a cell from the list of PCIs. Fór example, the eNodeB may select a PCI value randomly from the list of PCIs. [0024] In somé cases the eNodeB may restrict the received list by removing a PCI that is reported by user equipment, reported by a neighboring eNodeB, heard over-the-air via a downlink, acquired in somé other way, or acquired through a combination of two or more of these ways. The eNodeB may then select a PCI value randomly from the restricted list of PCIs or select a PCI value from the restricted list in somé other way.

[0025] In somé cases the access point 104 may provide information to a configuration server (e.g., as represented by the network node 108) to assist the configuration server in providing configuration information fór the access point 104. Forexample, the access point 104 may determine its location and send corresponding location information tothe network node 108. The network node 108 may then determine appropriate configuration information based on the location and send this configuration information to the access point 104, where the configuration controller 110 uses the configuration information to configure the access point 104.

[0026] In somé cases, a configuration server (e.g., as represented by the network node 108) directs an access point to another configuration server fór configuration information. Fór example, upon receiving a request from the access point 104 fór configuration information, the network node 102 may redirect the access point 104 to another node (e.g., another configuration server). Such a redirection may be based on, fór example, the location ofthe access point 104 and/orthe load on one or more of the configuration servers.

[0027] Configuration operations such as those described above may be advantageously employed in a network 200 as shown in FIG. 2 where somé access points provide macro coverage and other access points provide smaller coverage. Here, macro coverage areas 204 may be provided by, fór example, macro access points ofa Iarge area cellular network such as a 3G network, typically referred to as a macro cell network or a wide area network (WAN). In addition, smaller coverage areas 206 may be provided by, fór example, access points of a residence-based or building-based network environment, typically referred to as a local area network (LAN). As an access terminál (AT) moves through such a network, the access terminál may be served in certain locations by access points that provide macro coverage while the access terminál may be served at other locations by access points that provide smaller coverage. In somé aspects, the smaller coverage access points may be used to provide incremental capacity growth, in-building coverage, and different Services, all leading to a more robust user experience.

[0028] In the description herein, a node (e.g., an access point) that provides coverage over a relatively Iarge area may be referred to as a macro node while a node that provides coverage over a relatively small area (e.g., aresidence) may be referred to as afemto node. It should be appreciated that the teachings herein may be applicable to nodes associated with other types of coverage areas. Fór example, a pico node may provide coverage over an area that is smaller than a macro area and larger than a femto area (e.g., coverage within a commercial building). Alsó, a relay node may provide wireless coverage that enables an access point to communicate with other nodes in a network. In other words, a relay node may provide a wireless backhaul thatfacilitates connectivity to, fór example, a network node or another relay node. In various applications, other terminology may be used to reference a macro node, a femto node, or other access point-type nodes. Fór example, a macro node may be configured or referred to as an access node, base station, access point, eNodeB (eNB), macro cell, and so on. Alsó, a femto node may be configured or referred to as a Home NodeB, Home eNodeB, access point, base station, access point base station, eNodeB, femto cell, and so on. In somé implementations, a node may be associated with (e.g., divided intő) one or more cells or sectors. A cell or sector associated with a macro node, a femto node, or a pico node may be referred to as a macro cell, a femto cell, or a pico cell, respectively. Fór convenience, the description herein may refer generally to operations and components of access points and femto nodes. It should be appreciated that these operations and components alsó may be applicable to other types of nodes (e.g., relay nodes and pico nodes).

[0029] In the example of FIG. 2, several tracking areas 202 (or routing areas or location areas) are defined, each of which includes several macro coverage areas 204. Here, areas of coverage associated with tracking areas 202A, 202B, and 202C are delineated by the wide lines and the macro coverage areas 204 are represented by the hexagons. As mentioned above, the tracking areas 202 alsó may include femto coverage areas 206. In this

ΕΡ 2 223 552 Β1 example, each of the femto coverage areas 206 (e.g., femto coverage area 206C) is depicted within one or more macro coverage areas 204 (e.g., macro coverage area 204B). It shouid be appreciated, however, that a femto coverage area 206 may nőt lie entirely within a macro coverage area 204. Alsó, one or more picoorfemto coverage areas (nőt shown) may be defined within a given tracking area 202 or macro coverage area 204. [0030] As indicated by the small cells in the macro coverage area 204A, a large number of access points such as femto nodes may deployed in a network. In such a case, the teachings herein may be advantageously employed to configure these access points. With the above overview in mind, various techniques that may be employed to configure access points in accordance with the teachings herein will be described with reference to FIGS. 3-11. FIGS. 3-6 reiate in somé aspect to operations and components that may be employed to determine a pilot identifierto be used by an access point. FIGS. 7-9 reiate in somé aspect to operations and components that may be employed to configure an access point based on the configuration of at least one other node. FIG. 10 relates in somé aspect to operations that may be employed to provide configuration information to an access point. FIG. 11 relates in somé aspect to operations that may be employed to direct an access point to a configuration server.

[0031] Fór illustration purposes, the operations of FIGS. 3,5-7, and 9-11 (or any other operations discussed or taught herein) may be described as being performed by specific components (e.g., components ofthe system 100, the components shown in FIG. 4, orthecomponentsshown in FIG. 8). Itshould be appreciated, however, that these operations may be performed by other types of components and may be performed using a different number of components. It alsó shouid be appreciated that one or more ofthe operations described herein may nőt be employed in a given implementation.

[0032] FIGS. 4 and 8 illustrate several sample components that may be incorporated intő nodes such as an access point, a network node, and an access terminál to perform configurations operations as taught herein. The described components alsó may be incorporated intő other nodes in a communication system. Fór example, other nodes (e.g., other access points) in a system may include components similar to those described fór the access point 402 and/or the access point 802 to provide similar functionality.

[0033] As shown in FIG. 4, an access point 402 and a network node 404 (e.g., a configuration server) may include transceivers 406 and 408, respectively, fór communicating with other nodes. The transceiver 406 includes a transmitter 410 fór sending signals (e.g., messages) and a receiver 412 fór receiving signals (e.g., including configuration-related information). The transceiver 408 includes a transmitter 414 fór sending signals and a receiver 416 fór receiving signals. Similarly, an access point 802 and a network node 804 (e.g., a configuration server) as shown in FIG. 8 may respectively include a transceiver 806 (including a transmitter 808 and a receiver 810) and a transceiver 812 (including a transmitter 814 and a receiver 816). Alsó, an access terminál 818 as shown in FIG. 8 may include a transceiver 820 (including a transmitter 822 and a receiver 824).

[0034] The nodes of FIGS. 4 and 8 alsó include other components that may be used in conjunction with configuration operations as taught herein. Fór example, as shown in FIG. 8, the access point 802, the network node 804, and the access terminál 818 may include communication controllers 826, 828, and 830, respectively, fór managing communication with other nodes (e.g., sending and receiving messages/indications) and fór providing other related functionality as taught herein. Alsó as shown in FIG. 8, one or more of the access point 802, the network node 804, and the access terminál 818 may include configuration controllers 832 (e.g., comprising an integration reference point agent, IRPAgent), 834 (e.g., comprising an integration reference point manager, IRPManager), and 836, respectively, fór performing configuration-related operations and fór providing other related functionality as taught herein. Sample operations ofthe other components of FIGS. 4 and 8 are described beiow. [0035] Fór convenience, the nodes of FIGS. 4 and 8 are depicted as including components that may be used in the various examples described beiow in conjunction with FIGS. 3 -11. In practice, one or more ofthe illustrated components may nőt be used in a given example. As an example, in somé implementations the access terminál 818 may nőt include a conflict detector 838 and/or the configuration controller 836. As another example, in somé implementations the network node 804 may nőt include one or more ofthe configuration controller 834, a neighbor determiner 840, or a configuration server selector 842. As yet another example, in somé implementations the access point 802 may nőt include a location determiner 844.

[0036] Alsó, a given node may contain one or more of the described components. Fór example, a node may contain multiple transceiver components that enable the node to concurrently operate on multiple frequencies and/or enable the node to communicate via different types of technology (e.g., wired and/or wireless technology).

[0037] Referring now to FIGS. 3 and 4, the teachings herein may be employed to configure an access point with a pilot identifier based on the pilot identifier(s) used by at least one other access point. Through the use of such a scheme, access points in a network may choose (e.g., autonomously choose) pilot identifiers in a distributed rnanner. In this way, the possibility of pilot identifier collisions in the network (e.g., when a node hears multiple access points broadcasting the same pilot identifier) may be reduced or eliminated. Moreover, this may be accomplished without the use of a centralized manager that assigns and keeps track of all ofthe pilot identifiers used by all ofthe access points in the network.

ΕΡ 2 223 552 Β1 [0038] A pilot identifier may take various forms and may be referred to using different terminology in different implementations. For example, a pilot identifier may be referred to as a cell identifier (cell ID), a physical cell identifier (PCI), or primary scrambling sequence (PSC). Alsó, a pilot identifier may be associated with a pseudorandom nőise sequence (PN sequence) that is present in a pilot signal.

[0039] As represented by block 302 of FIG. 3, in somé implementations a configuration server(e.g., the network node 404 of FIG. 4) determines a list of pilot identifiers that may be used by a given access point (e.g., the access point 402) and sends the list to the access point. In the example of FIG. 4, these opérations may be performed by a configuration controller418.

[0040] Here, the list of pilot identifiers may comprise a subset (e.g., 10 pilot identifiers) of a set of all the pilot identifiers (e.g., 512 pilot identifiers) defined for a given network. In somé implementations the list comprises a rangé of pilot identifiers.

[0041] The list of pilot identifiers may be operator configurable. In somé cases, a given list may be applicable throughout the operator’s network (e.g., multiple access points in a network may be assigned the same list). In somé cases, unique lists may be defined for different access points. For example, each access point in a network may be assigned its own list (all of these lists may nőt be unique, however).

[0042] In somé implementations the operator may divide the pilot identifier space intő different subsets. The pilot identifier space may be divided based on various criteria.

[0043] In somé implementations the pilot identifier space is divided intő different subsets for different types of access points. Forexampie, macro access points may be assigned a first subset of pilot identifiers (e.g., pilot identifiers 0 - 49), femto nodes may be assigned a second subset of pilot identifiers (e.g., pilot identifiers 50 - 499), and mobile access points may be assigned a third subset of pilot identifiers s (e.g., pilot identifiers 500 - 511). [0044] In somé implementations the pilot identifier space is divided intodifferentsubsets based on the transmit power of access points. For example, higher-power access points (e.g., macro access points) may be assigned a first subset of pilot identifiers and a lower-power access points (e.g., femto nodes, pico nodes, or relay nodes) may be assigned a second subset of pilot identifiers.

[0045] In somé implementations the pilot identifier space may be divided intő different subsets based on location. For example, different pilot identifier subsets may be defined for different geographic regions. Thus, the subset of pilot identifiers assigned to a given access point may be dependent on the location of the access point.

[0046] In view ofthe above, in somé implementations the opérations of the configuration server at block 302 may be based on information the configuration server receivesfrom the access point402. Forexampie, atsome point in time (e.g., once the access point 402 establishes an Internet connection), the access point 402 uses its network connectivity to contact the network node 404 and send this information.

[0047] The access point 402 (e.g., a location determiner 420) may determine information indicative ofthe location ofthe access point 402 and send this information to the network node404. Such information maytakevarious forms. For example, information indicative of location of an access point may indicate at least one of: a city within which the access point is located, a state within which the access point is located, a country within which the access point is located, a macro access point that serves the access point, a zone with which the access point is associated, a cell with which the access point is communicating, a network identity or operator that the cell is associated with, GPS coordinates, a geographic location, or a Street address.

[0048] In addition, or in the alternative, the access point 402 may send information indicative of the type of the access point 402 to the network node 404. As discussed above, this information may take various forms. For example, this type information may indicate one or more of a device eláss (e.g., femto, macro, mobile, etc.) of the access point 402, a power eláss (e.g., high power, low power, etc.) ofthe access point 402, whether the access point is restricted (e.g., as taught herein), whether the access point is stationary or mobile, or somé other characteristic(s) associated with the access point 402. [0049] The network node 404 (e.g., the configuration controller 418) may then determine the list of pilot identifiers for use by the access point 402 based on the information it receives from the access point 402. In somé aspects, the network node 404 may use pilot identifier ranges pre-provisioned by the operator to select a valid rangé of pilot identifiers for use by the indicated node type and/or for use at the indicated location.

[0050] As mentioned above, somé or all of the operations of block 302 may nőt be utilized in somé implementations. For example, in somé cases the pilot identifier lists (e.g., ranges) are standardized. In such a case, the network node 404 may simply send a standard pilot identifier list to the access point 402. Alternatively, the access point 402 may be configured with the pilot identifier list, whereby the access point 402 does nőt récéivé this information from the network node 404.

[0051] As represented by block 304 of FIG. 3, the access point 402 (e.g., a pilot identifier determiner 422) determines at least one pilot identifier that is used by at least one other access point. For example, the access point 402 may determine which pilot identifiers are being used by its neighbors.

[0052] In somé implementations the access point 402 (e.g., a neighbor discovery controller 424) may conduct neighbor discovery to identify its neighbors. As will be discussed in more detail below, the access point 402 may discoverone-hop neighbors ormulti-hop neighbors (e.g.,

ΕΡ 2 223 552 Β1 two-hop, three-hop, etc.). In the latter case, the access point 402 may elect to crawl two or three hops or more to obtain pilot identifier Information from more distant neighbors.

[0053] In somé implementations the access point 402 acquires configuration Information from its neighbors via neighbor discovery. Fór example, as a result of a neighbor discovery request issued by the neighbor discovery controller424, the access point 402 may récéivé a neighbor discovery response from a neighbor access point (e.g., a one-hop or multi-hop neighbor) that includes the pilot identifier used by that neighbor access point. Such a neighbor discovery operation may be performed, fór example, via a backhaul.

[0054] In somé implementations the access point 402 may acquire the pilot identifier Information of its neighbors from aserver(e.g., network node 404). Forexample, the network node 404 (e.g., a neighbor determiner 426) may maintain this information on its own or obtain this information upon request. The network node 404 may then send the pilot identifier information to the access point 402 in response to a request from the access point 402. In somé aspects, the network node 404 may identify the pilot identifier information to be provided based on the location ofthe access point 402. Fór example, in its request, the access point 402 may include information that is indicative of its location. The network node 404 may then identify the access points in that vicinity and determine which pilot identifiers they use. In addition, the network node 404 may take intő account the transmit power of these access points when determining whether pilot signals transmitted by these access points may be received by a node that alsó receives pilot signals from the access point 402. In this way, only those pilot identifiers that may potentially cause a pilot identifier collision may be sent to the access point 402.

[0055] In somé implementations the access point 402 may initially acquire a list of its neighbors and then conduct neighbor discovery on the access points identified by the list. Fór example, the network node 404 (e.g., the neighbor determiner 426) may send such a list to the access point 402 based on the location of the access point 402 (e.g., which may be provided to the network node 404 by the access point 402). Alsó, an access terminál that is associated with (e.g., served by) the access point 402 may send a report to the access point 402 that indicates which access points the access terminál currently hears (i.e., receives signals from) or has previously heard.

[0056] In somé implementations the access point 402 may determine the pilot identifiers used by its neighbors without conducting formai neighbordiscovery. Forexample, the access point 402 may include a downlink receiver (e.g., as represented by receiver 412) that is configured to detect pilot signals from neighboring access points. That is, the access point 402 may récéivé configuration information over-the-air. In this case, the access point 402 may determine the pilot identifiers used by these neighboring access points based on detected signals (e.g., based on the PN sequence derived from received pilot signals) and, optionally, determine the identify ofthe neighbors (e.g., by analyzing information in other downlink messages).

[0057] In somé implementations the access point 402 may récéivé pilot identifier or other neighbor information from an access terminál (e.g., access terminál 102 of FIG. 1). Fór example, an access terminál that is associated with the access point 402 may send a report to the access point 402 indicative of the pilot signals that the access terminál is receiving. Here, the access terminál may dérivé information (e.g., a pilot identifier, a PN sequence, or other access point identify information) from the signals it receives and forward this information to the access point 402.

[0058] As represented by block 306 of FIG. 3, the access point402 (e.g., a pilot identifierselector428) selects a pilot identifier to be used by the access point 402 based on the pilot identifiers determined by block 304 and a designated pilot identifier list, if applicable. Forexample, the access point 402 may select a pilot identifier from the designated list that does nőt conflict with (e.g., is nőt the same as) any pilot identifier used by the neighboring access points.

[0059] The access point 402 may attemptto avoid conflict with the pilot identifiers of its immediate neighbors (e.g., one-hop neighbors) and, optionally, multi-hop neighbors. Multi-hop neighbor discovery is discussed in more detail below in conjunction with FIGS. 5 and 6. [0060] The access point 402 may organize the pilot identifiers of its neighbors in several groups and use these groups in the pilot identifierselection process. Such groups may be organized in various ways. Fór example, a first group may include pilot identifiers heard by the access point 402 and/or the pilot identifiers reported by access terminals associated with the access point 402. A second group may include the second-hop neighbors identified during neighbor discovery, bút only those that were identified via neighbor lists provided by neighboring femto nodes (e.g. a low-power access points). A third group may include the second-hop neighbors identified during neighbordiscovery, bút only those that were identified via neighbor lists provided by neighboring macro access points (e.g. a high-power access points). Here, the differentiation between groups two and three may be employed because a neighboring macro access point may report a large numberoffemto node neighbors, most of which may be Iocated relatively far away from the access point 402 and are, therefore, less likely to cause a conflict with the pilot identifier used by the access point 402.

[0061] Continuing with the above example, intheevent one ofthe pilot identifiers in a designated list is nőt being used by any of the neighbors of the access point 402 (e.g., any ofthe identifiers of groups one, two, and three), the access point 402 may simply select this pilot identifier. Conversely, if all ofthe pilot identifiers in the designated

ΕΡ 2 223 552 Β1 set are being used by at least one ofthe neighbors, the access point 402 may determine whether any ofthe pilot identifiers ofthe designated set in only in conflict with an access point from group three (i.e., there is no conflict with group one or group two). If so, the access point 402 may select one of these pilot identifiers in an attempt to minimize the risk of a conflict. In the event all of the pilot identifiers ofthe designated list conflict with either group one or group two, the access point 402 may select a pilot identifier that only conflicts with group two (in the event such a pilot identifier exist). In somé implementations, the access point 402 is nőt allowed to select a pilot identifier from group one. In the event there are multiple pilot identifiers to choose from, the access point 402 may select one of the pilot identifiers randomly or in somé other designated manner.

[0062] As represented by block 308, the access point 402 is then configured to use the selected pilot identifier forwireless communication. Fór example, the transmitter 410 may use the selected pilot identifier to generate the pilot signals that it broadcasts.

[0063] As represented by block 310, the access point 402 may continue to monitor the pilot identifiers used by its neighbors (e.g., using the operations of block 304) so that the access point may continue to ensure that the pilot identifier it is using is nőt in conflict with the pilot identifier used by a neighbor. Fór example, such a conflict may be caused by a new access point that has been recently installed in the vicinity of the access point 402 or by a mobile access point that has entered the vicinity of the access point 402. Alsó, a pilot identifier conflict (e.g., collision) may occur if two access points that are nőt within hearing rangé of each other choose the same a pilot identifier. Such a conflict may eventually be detected, fór example, by an access terminál that receives signals from both of the access points. In such a case, one or both of the access points may be configured to change their pilot identifier. As described below in conjunction with FIG. 7, an access terminál that detects a conflict may inform one or all of the concerned access points. Fór example, the access terminál may connect to one of these access points to pass on this information, or may send this information to the concerned access points using a connection the access terminál has to another access point.

[0064] In the event a conflict is identified, the access point 402 may perform operations similar to those described above to select a new pilot identifier that does nőt conflict with any pilot identifier used by any neighboring access point. Thus, through the use of these techniques, the access point 402 may independently recover from pilot identifier conflicts (e.g., pilot identifier collisions). Fór example, upon receivíng a conflict notification or identify ing a conflict, the access point 402 may move its current pilot identifier intő a group of identifiers that are designated as forbidden (e.g., group one discussed above) and repeat the operations described above. [0065] In somé cases, when changing its pilot identifier, the access point 402 may drop all connections that it currently holds and force the associated access terminals to reconnect. As an optimization, the access point 402 may send a message ahead oftime to inform the access terminals ofthe new pilot identifier and the time at which the access point 402 will switch to using a new pilot identifier. In this way, the switch to the new pilot identifier may be achieved with minimál disruption of service.

[0066] Referring now to FIGS. 5 and 6, an access point may discover its neighbors through the use of access point-initiated neighbor discovery and/or access terminal-assisted neighbor discovery. FIG. 5 represents an example of access point-initiated neighbor discovery. FIG. 6 represents an example of access terminal-assisted neighbor discovery.

[0067] In FIG. 5, an access point A may initiate neighbor discovery upon learning about the existence of a neighboring access point B. Fór example, as discussed above the access point A may üstén to the broadeast information of its RF neighbors (e.g., through the use of adownlinkreceiverjorobtain information about its neighbors in somé other manner. As represented by block 502 in FIG. 5, the access point A may thus learn an identifier (e.g., the address) of one of its neighbors.

[0068] The access point A (e.g., by operation of a neighbor discovery controller component) may connect to that neighbor directly over the backhaul and perform an exchange of neighbor discovery messages. Fór example, the access point A sends a neighbor discovery request (ND Request) to the access point B. In response, the access point B (e.g., by operation ofa neighbor discovery controller component) sends a neighbor discovery report (ND Report) to the access point A. Similarly, the access point B sends a neighbor discovery request to the access point A and receives a neighbor discovery report in response.

[0069] Advantageously, the report from the access point B may include information about its neighbors (e.g., an access point C). Fór example, the information regarding the access point C may comprise sufficient information (e.g., an identifier, an address, etc.) to enable another node to access the access point C. Here, it should be appreciated that the access point C may be a secondhop (or higher-hop) neighbor to the access point A (e.g., the access point A cannot hear the access point C). In somé implementations the access point B may automatically include information about its neighbors in its report. Alternatively, the access point A may specifically request that the access point B include this information in the report.

[0070] The access point A may therefore use any information it receives from a first-hop neighbor (e.g., access point B) regarding any multi-hop neighbors to communicate with the multi-hop neighbors. Fór example, as indicated in FIG. 5, the access point A sends a neighbor discovery request to the access point C and receives a neighbor discovery report in response. Likewise, the access point C sends a neighbor discovery report to the

ΕΡ 2 223 552 Β1 access point A and receives a neighbor discovery report in response. In a simiiar manner as discussed above, the neighbor discovery report from the access point C may include information about neighbors (nőt shown in FIG. 5) of access point C. In this way, the access point A may obtain information about its third-hop neighbors.

[0071] In FIG. 6, an access point A learns information about its neighbors through access terminal-assisted neighbor discovery. Here, the access terminál sends a pilot report to its serving access point (access point A) that indicates all ofthe pilots that the access terminál is receiving (e.g., pilot ID2 and other pilot IDs). In the event a pilot ID in the pilot report is new to the access point A, the access point A may use the access terminál to resolve the address (e.g., the IP address) of the new access point. Fór example, the access point A may send a sector ID request or other suitable request (e.g., including the pilot ID ofthe new access point) to the access terminál. The access terminál may then send a sector response that includes the corresponding sector ID (or the access terminál sends somé other suitable response) to the access point A.

[0072] The access point A may then perform a neighbor discovery exchange with the new access point (e.g., access point B). As discussed above in conjunction with FIG. 5, the access point A may récéivé information about second-hop neighbors (e.g., access point C) from the access point B and then conduct a neighbor discovery exchange with the second-hop neighbor(s).

[0073] Referring nowto FIGS. 7-9, theteachings herein are applicable to the configuration of an access point in generál. Fór example, the techniques described above as well as other techniques described herein may be used to determine a variety of configuration parameters fór an access point. Examples of such configuration parameters include, without limitation, a frequency bánd, a carrier frequency, a pilot identifier, a maximum transmit power, and a transmit power profile.

[0074] As represented by block 702 of FIG. 7, the access point 802 (e.g., a neighbor discovery controller 846) may optionally determine the identity of its neighbors. Fór example, in a simiiar manner as discussed above the access point 802 may récéivé a list of its neighbors from a configuration server (e.g., network node 804). Here, an operator may provide one or more centralized configuration servers within its network to assist in the configuration of access points in the network. Once the access point 802 has initialized, it may initiate the configuration proeess.

[0075] In somé aspects, initialization of the access point 802 involves the access point 802 acquiring connectivity with the operator’s network. Here, the access point 802 may need to be authenticated before is allowed to access an operator’s network.

[0076] In addition, the access point 802 may locate a configuration server. Fór example, the access point 802 may be preconfigured with a well-known address (e.g., IP address) ofthe configuration server. Alternatively, the access point 802 may be aware of the operator of the network to which is connected (e.g., operator.com), such that the access point 802 may make a DNS query fór the FQDN config_server.operator.com and récéivé an IP address in return. In other implementations the access point 802 may use somé other technique to obtain the appropriate address information. The access point 802 may then establish communication with the configuration server. Fór example, communication may be established using standardized SNMP or other configuration protocols such as NetConf, OMA DM, CWMP (TR 069), or DOCSIS, or through the use of a proprietary CLI over SSH.

[0077] As discussed above, a configuration server may provide a neighbor list to an access point based on location information the configuration server receives from the access point. These operations will be described in more detail with reference to the flowchart of FIG. 9 and the nodes 802 and 804 of FIG. 8.

[0078] As represented by block 902 of FIG. 9, after initialization of the access point 802, the location determiner844 may determine the location ofthe access point 802. The location determiner844 maydetermine location in various ways. Fór example, location may be determined through the use of global positioning system (GPS) technology, assisted-GPS technology, a network-based location determining method, an RF-based method, or somé other suitable method.

[0079] As represented by block 904, the access point 802 sends its location-related information (e.g., an estimate of its location) to the network node 804. In somé implementations this operation may be initiated by the access point 802 (e.g., once the access point 802 connects to the configuration server). In somé implementations the configuration server may explicitly ask fór this location information as part of its connection setup protocol (e.g., via a request). The access point 802 alsó may send other information (e.g., power profile, node type) to the network node 804 that the network node 804 may use to provide an appropriate response.

[0080] As represented by block 906, once the network node 804 (e.g., neighbor determiner 840) receives the location information from the access point 802, the network node 804 identifies the neighbors of the access point 802 and generates a neighbor list. This neighbor list may include, fór example, any macro access points that are relatively close to the access point 802, as well as any other access points (e.g., femto nodes, etc.) in the geographical vicinity ofthe access point 802.

[0081] The neighbor list may be a function ofthe power classes (or power profiles) of the access point 802 and its neighbors. Fór example, a distant macro access point that transmits with high-power may be a neighbor of the access point 802. In contrast, a low-power access point (e.g., a femto node) that is relatively close to the access point 802 may nőt be included in the neighbor list if the coverage areas of the low-power access point and the access point 802 do nőt intersect. Consequently, in somé

ΕΡ 2 223 552 Β1 cases the access point 802 may send power class information to the network node 802 along with the location information. In addition, the network node 804 may obtain power-related information from other access points in the network. As represented by block 908, once the neighbor list has been generated, the network node 804 sends the neighbor list to the access point 802.

[0082] Referring again to FIG. 7, as represented by block 704, the access point 802 (e.g., the configuration controller 832) determines the configuration of its neighbors. As discussed above, the access point 802 may acquire the configuration information of its neighbors in various ways. Fór example, the access point 802 may connect directly with a neighbor via a backhaul and thereby read a select set of parameters. The access point 802 may üstén over-the-air to discover one or more parameters ofthe neighboring access point (e.g., a pilot identifier as discussed above). The access point 802 may use access terminal-assisted neighbor discovery, whereby an access terminál associated with the access point 802 may send configuration information to the access point 802. Fór example, the access terminál 818 (e.g., configuration controller 836) may inform the access point 802 of the neighbor access points that the access terminál 818 has heard. Alsó, the access point 802 may récéivé the configuration information of neighbor nodes from a configuration serversuch as the network node 804 (e.g., configuration controller 834) as discussed herein. It should be appreciated that the access point 102 may obtain configuration information through the use of one or more of the techniques deseribed herein or through the use of other techniques.

[0083] As represented by block 706, the access point 802 (e.g., a configuration determiner 848) may specify a configuration fór the access point 802 based on the configuration information obtained at block 704. In somé aspects, the access point 802 may autonomously choose itsown set of parameters (e.g., RF parameters) as afunction ofthe parameters (e.g., RF parameters) of its neighbors.

[0084] In somé cases the access point 802 may select its power profile based on the power profile or power profiles of its neighbors. Fór example, the access point 802 may select the same power profile that is used by its neighbors. Alternatively, the access point 802 may select a power profile that is complementary to the power profile(s) used by its neighbor(s). A power profile may define, fór example, a maximum transmit power, different transmit powers fór different conditions, or other power parameters.

[0085] As discussed above, in somé cases the access point 802 may select a pilot identifier (e.g., a pilotPN) based on the pilot identifiers used by its neighbors. Fór example, the access point 802 may select a different pilot identifier than its neighbors.

[0086] In somé cases the access point 802 may select a carrier (e.g., an RF frequency bánd) based on the carrier(s) used by its neighbors. Fór example, neighboring nodes in a network may select complementary sets of carrier priorities (e.g., as indicated by a carrier mask or somé other suitable indication) in order to implement an interference management scheme. Here, eaeh access point may radiate more energy on somé carriers and less energy (e.g., or nőne at all) on other carriers. If neighboring access points choose these carrier priorities in a complementary fashion, it may ensure that access terminals associated with eaeh of the access points may have more favorable interference environments, at least on somé ofthe carriers. To accomplish this in an autonomous manner, a new access point(e.g., an access point that has recently been initialized) may determine the carrier priorities used by its neighbors and choose its own carrier priorities to be as complementary to them as possible.

[0087] In somé aspects, the configuration ofthe access point 802 may be dependent on its location. Fór example, a configuration server (e.g., the configuration controller 834) may specify a list (e.g., subset) of parameters (e.g., an allowed paraméter rangé) that may be used by the access point. As discussed above in conjunction with FIG. 3, the specified list may be based on the location of the access point 802. Fór example, a particular list of power profiles that may be used by the access point 802 may be specified based on the location of the access point 802. Similarly, a particular list of frequency bands that may be used by the access point 802 may be specified based on the location ofthe access point 802. At a broad level, the city, state, or country in which the access point 802 currently resides may limit which frequency bánd the access point 802 may use. Fór example, the same operator may own different frequency bands in different countries or an operator may designate the use of different frequency bands in different cities.

[0088] In somé implementations configuration information may include certain optimization parameters (e.g., non-radio parameters). Such parameters may include, fór example, security keys that may be used to gain access to one or more Services (e.g., network connectivity). Such parameters alsó may include the addresses of other nodes to which the access point 802 may need to connect.

[0089] As represented by block 708 of FIG. 7, the access point 802 may then use the configuration specified at block 706 fór communication or other operations. Fór example, as discussed above transceiver 806 be configured with the determined RF parameters to determine which pilot identifier to advertise, which carriers to operate on, and the transmit power level to be used on these carriers.

[0090] As represented by block 710, the access point 802 may continue to monitor the configurations of its neighbors to detect a conflict (e.g., a collision). As mentioned above, in the event of a conflict, the access point 802 may perform configuration operations as deseribed above to resolve the conflict.

[0091] In somé implementations, the access point 802

ΕΡ 2 223 552 Β1 may récéivé an indication ofthe conflictfrom an access terminál (e.g., access terminál 818). For example, if the access terminál 818 detects a conflict (e.g., conflict detector 838 detects two access points using the same pilot identifier), the access terminál 818 may send a corresponding message to the access point 802. Based on this message, the configuration controller 802 may perform operations as discussed above to select a different configuration for the access point 802.

[0092] It should be appreciated that the operations and components described above conjunction with FIGS. 7 - 9 may be applicable to the configuration schemes described herein with reference to other figures. Forexample, these operations and components may be used in conjunction with configuring a pilot identifierforan access point (e.g., as described above in conjunction with FIGS. 3-6).

[0093] Referring now to FIGS. 10 and 11, in somé implementations an access point may obtain configuration information from another node (e.g., a configuration server), whereby the configuration information is dependent on the location ofthe access point. For convenience, the operations of FIGS. 10 and 11 will be described in the context of the access point 802 and the network node 804 of FIG. 8.

[0094] Asrepresented by blocks 1002 and 1004ofFIG. 10, the access point 802 (e.g., location determiner 844) determines its location and provides this information to the network node 804. This operation may thus be similar to the location determining operations described above (e.g., at blocks 902 and 904).

[0095] As represented by block 1006, the network node 804 (e.g., configuration controller 834) determines configuration information forthe access point 802 based on the received location information. For example, as discussed above, configuration information may comprise RF parameters, optimization parameters, other parameters, or a combination of two or more of these parameters. In somé cases this operation may result in an entirely new configuration being defined for the access point 802. Alternatively, the network node 804 may oniy define a portion of the parameters used by the access point 802.

[0096] As represented by block 1008, the network node 804 sends the configuration information to the access point 802. The access point 802 is then configured to use the received configuration information (block 1010).

[0097] Referring now to FIG. 11, in somé cases a configuration server may elect to redirect an access point to a different configuration server. Sueh a determination may be made, forexample, based on the location ofthe access point and/or the load on a configuration server. [0098] As represented by block 1102, the access point 802 sends a message to the network node 804 to obtain configuration information. As discussed above, sueh a message may include information indicative ofthe location ofthe access point 802.

[0099] As represented by block 1104, the network node 804 (e.g., the configuration server selector 842) may determine whether to provide the requested configuration information. Forexample, the network node 804 may determine, based on the location ofthe access point 802, that another configuration server (e.g., that is closer to the access point 802) should handle the request. Alsó, the network node 804 may elect to redirect a request based on the load atthe network node 804. Forexample, if the network node 804 is heavily loaded, the network node 804 may redirect the request to another configuration server that is nőt as heavily loaded.

[0100] As represented by blocks 1106 and 1108, in the event the network node 804 decides to handle the request, the network node 804 may provide the requested configuration information to the access point 802. For example, this operation may be similar to the operations described above in conjunction with FIG. 10.

[0101] As represented by block 1110, if the network node 804 decides it will nőt handle the request (e.g., based on its load or the proximity of the access point 802), the network node 804 (e.g., the configuration server selector 842) identifies another configuration server that may provide configuration information for the access point 802. To this end, the network node 804 may maintain a database that includes information about other configuration servers on the network. In addition or alternatively, the network node 804 may be configured, conduct discovery, or communicate with another node to obtain this information.

[0102] As represented by block 1112, the network node 804 sends an indication ofthe other configuration server to the access point 802 (e.g., in the form of a redirection message). In somé implementations the indication may comprise information that will enable the access point 802 to determine the address ofthe other configuration server. For example, the indication may comprise a location (e.g., a city) ofthe configuration server. Upon receipt of this information, the access point 802 may determine the address of the other configuration server (e.g., via DNS query).

[0103] In somé implementations the indication may comprise the address of the other configuration server. In somé implementations redirection may be achieved by the configuration server setting a paraméter that indicates the address of the different configuration server. Upon determining that there is then a change in this paraméter, the access point 802 will attempt to establish a connection with the new configuration server.

[0104] As represented by block 1114, the access point 802 may therefore send a message to the other configuration server to obtain configuration information. Once the access point 802 completes its configuration exchange with a configuration server, the access point 802 may commence user communication operations.

[0105] As mentioned above, the teaching herein may be implemented in network that employs macro access points, femto nodes, relay nodes, and so on. FIGS. 12

ΕΡ 2 223 552 Β1 and 13 illustrate examples how access points may be deployed in such a network. FIG. 12 illustrates, in a simplified manner, how the cells 1202 (e.g., macro cells 1202A - 1202G) of a wireless communication system 1200 may servicéd by corresponding access points 1204 (e.g., access points 1204A - 1204G). Here, the macro cells 1202 may correspond to the macro coverage areas 204 of FIG. 2. As shown in FIG. 12, access terminals 1206 (e.g., access terminals 1206A-1206L) may be dispersed at various locations throughout the system over time. Each access terminál 1206 may communicate with one or more access points 1204 on a forward link (FL) and/or a reverse link(RL) ata given moment, depending upon whether the access terminál 1206 is active and whether it is in soft handover, fór example. Through the use of this cellular scheme, the wireless communication system 1200 may provide service over a large geographic region. Fór example, each of the macro cells 1202A 1202G may cover a few blocks in a neighborhood or several square miles in rural environment.

[0106] FIG. 13 illustrates an example how one or more femto nodes may be deployed withín a network environment (e.g., the system 1200). In the system 1300 of FIG. 13, multiple femto nodes 1310 (e.g., femto nodes 1310A and 1310B) are installed in a relatively small area coverage network environment (e.g., in one or more user residences 1330). Each femto node 1310 may be coupled to a wide area network 1340 (e.g., the Internet) and a mobile operator core network 1350 (e.g., comprising network nodes as discussed herein) via a DSL router, a cáble modem, a wireless link, or other connectivity means (nőt shown).

[0107] The owner ofa femto node 1310 may subscribe to mobile service, such as, fór example, 3G mobile service offered through the mobile operator core network 1350. In addition, an access terminál 1320 may be capable of operating both in macro environments and in smaller area coverage (e.g., residential) network environments. In other words, depending on the current location ofthe access terminál 1320, the access terminál 1320 may be served by a macro cell access point 1360 associated with the mobile operator core network 1350 or by any one of a set of femto nodes 1310 (e.g., the femto nodes 1310A and 1310B that reside withín a corresponding user residence 1330). Fór example, when a subscriber is outside his home, the subscriber may be served by a standard macro access point (e.g., access point 1360) and when the subscriber is nearor inside his home, the subscriber may be served by a femto node (e.g., node 1310A). Here, a femto node 1310 may be backward compatible with legacy access terminals 1320. [0108] Afemto node 1310 may be deployed on a single frequency or, in the alternative, on multiple frequencies. Depending on the particular configuration, the single frequency or one or more of the multiple frequencies may overlap with one or more frequencies used by a macro access point (e.g., access point 1360).

[0109] In somé aspects, an access terminál 1320 may be configured to connect to a preferred femto node (e.g., the home femto node ofthe access terminál 1320) whenever such connectivity is possible. Fór example, whenever the access terminál 1320A is withín the user’s residence 1330, it may be desired that the access terminál 1320A communicate only with the home femto node 1310Aor 1310B.

[0110] In somé aspects, ifthe access terminál 1320 operates withín the macro cellular network 1350 bút is nőt residing on its most preferred network (e.g., as defined in a preferred roaming list), the access terminál 1320 may continue to search fór the most preferred network (e.g., the preferred femto node 1310) using a Better System Reselection (BSR), which may involve a periodic scanning of avaiiable systems to determine whether better systems are currently avaiiable, and subsequent efforts to associate with such preferred systems. With the acquisition entry, the access terminál 1320 may limit the search fór specific bánd and channel. Fór example, the search fór the most preferred system may be repeated periodically. Upon discovery ofa preferred femto node 1310, the access terminál 1320 selects the femto node 1310 fór camping withín its coverage area.

[0111] A femto node may be restricted in somé aspects. Fór example, a given femto node may only provide certain Services to certain access terminals. In deployments with so-called restricted (or closed) association, a given access terminál may only be served by the macro cell mobile network and a defined set of femto nodes (e.g., the femto nodes 1310 that reside withín the corresponding user residence 1330). In somé implementations, a node may be restricted to nőt provide, fór at least one node, at least one of: signaling, data access, registration, paging, or service.

[0112] In somé aspects, a restricted femto node (which may alsó be referred to as a Closed Subscriber Group Home NodeB) is one that provides service to a restricted provisioned set of access terminals. This set may be temporarily or permanently extended as necessary. In somé aspects, a Closed Subscriber Group (CSG) may be defined as the set of access points (e.g., femto nodes) that share a common access control list of access terminals. Achannelon which all femto nodes (orall restricted femto nodes) in a region operate may be referred to as a femto channel.

[0113] Various relationships may thus exist between a given femto node and a given access terminál. Fór example, from the perspective of an access terminál, an open femto node may refer to a femto node with no restricted association (e.g., the femto node ailows access to any access terminál). A restricted femto node may refer to a femto node that is restricted in somé manner (e.g., restricted fór association and/or registration). A home femto node may refer to a femto node on which the access terminál is authorized to access and operate on (e.g., permanent access is provided fór a defined set of one or more access terminals). A guest femto node may refer to a femto node on which an access terminál

EP 2 223 552 Β1 is temporarily authorized to access or operate on. An alien femto node may refer to a femto node on which the access terminál is nőt authorized to access or operate on, except fór perhaps emergency situations (e.g., 911 calls).

[0114] From a restricted femto node perspective, a home access terminál may refer to an access terminál that is authorized to access the restricted femto node (e.g., the access terminál has permanent access to the femto node). A guest access terminál may refer to an access terminál with temporary access to the restricted femto node (e.g., limited based on deadline, time of use, bytes, connection count, or somé other criterion or eriteria). An alien access terminál may refer to an access terminál that does nőt have permission to access the restricted femto node, exceptfor perhaps emergency situations, fór example, such as 911 calls (e.g., an access terminál that does nőt have the credentials or permission to register with the restricted femto node).

[0115] Fór convenience, the disclosure herein describes various functionality in the context of a femto node. Itshould be appreciated, however, thata pico node or relay node may provide the same or similar functionality fór a different (e.g., larger) coverage area. Fór example, a pico node or a relay node may be restricted, a home pico node or home relay node may be defined fór a given access terminál, and so on.

[0116] The teachings herein may be implemented in various types of communication devices. In somé aspects, the teachings herein may be implemented in wireless devices that may be deployed in a multiple access communication system that may simuítaneously support communication fór multiple wireless access terminals. Here, each terminál may communicate with one or more access points via transmissions on the forward and reverse links. Theforward link(also known as the downlink) refers to the communication link from the access points to the terminals, and the reverse link (alsó known as the uplink) refers to the communication link from the terminals to the access points. This communication link may be established via a single-in-single-out system, a multiple-in-multiple-out(MIMO) system, orsomeothertype of system.

[0117] Fór illustration purposes, FIG. 14 describes sample communication components that may be employed in a wireless device in the context of a MIMObased system 800. The system 1400 employs multiple (Nj-) transmit antennas and multiple (N_R) récéivé antennas fór data transmission. A ΜΙΜΟ channel formed by the Λ/τ-transmit and N_R récéivé antennas may be decomposed intő /\/_s índependent channels, which are alsó referred to as spatial channels, where /\/_s < min {N_T, N_R}. Each ofthe /\/_s índependent channels corresponds to a dimension. The ΜΙΜΟ system may provide improved performance (e.g., higher throughput and/or greater reliability) ifthe additional dimensionalities created by the multiple transmit and récéivé antennas are utilized. [0118] The system 1400 may support time division duplex (TDD) and frequency division duplex (FDD). In a TDD system, the forward and reverse link transmissions are on the same frequency region so that the reciprocity principle allows the estimation ofthe forward link channel from the reverse link channel. This enables the access point to extract transmit beam-forming gain on theforward link when multiple antennas are available at the access point.

[0119] The system 1400 includes a wireless device 1410 (e.g., an access point) and a wireless device 1450 (e.g., an access terminál). Atthe device 1410, traffic data fór a number of data streams is provided from a data source 1412 to a transmit (TX) data processor 1414. [0120] In somé aspects, each data stream is transmitted overa respectivetransmit antenna. TheTXdata processor 1414 formats, codes, and interleaves the traffic data fór each data stream based on a particular coding scheme selected fór that data stream to provide coded data.

[0121] The coded data fór each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used atthe receiver system to estimate the channel response. The multiplexed pilot and coded data fór each data stream is then modulated (i.e., Symbol mapped) based on a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or MQAM) selected forthat data stream to provide modulation symbols. The data rate, coding, and modulation fór each data stream may be determined by instructions performed by a processor 1430. A data memory 1432 may store program code, data, and other information used by the processor 1430 or other components of the device 1410.

[0122] The modulation symbols fór all data streams are then provided to a TX ΜΙΜΟ processor 1420, which may further process the modulation symbols (e.g., fór OFDM). The TX ΜΙΜΟ processor 1420 then provides N_Tmodulation Symbol streams to A/j-transceivers (XCVR) 1422A through 1422T. In somé aspects, the TX ΜΙΜΟ processor 1420 applies beam-forming weights to the symbols of the data streams and to the antenna from which the Symbol is being transmitted.

[0123] Each transceiver 1422 receíves and processes a respective Symbol stream to provide one or more analóg signals, and further conditions (e.g., amplifies, filters, and upconverts) the analóg signals to provide a modulated signal suitable fór transmission over the ΜΙΜΟ channel. N_T modulated signals from transceivers 1422A through 1422T are then transmitted from N_T antennas 1424A through 1424T, respectively.

[0124] At the device 1450, the transmitted modulated signals are received by N_R antennas 1452A through 1452R and the received signal from each antenna 1452 is provided to a respective transceiver (XCVR) 1454A through 1454R. Each transceiver 1454 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide

ΕΡ 2 223 552 Β1 samples, and further processes the samples to provide a corresponding received Symbol stream.

[0125] A récéivé (RX) data processor 1460 then receives and processes the N_R received Symbol streams from /V_R transceivers 1454 based on a particular receiver Processing technique to provide N_T detected Symbol streams. The RXdata processor 1460 then demodulates, deinterleaves, and decodes each detected Symbol stream to recover the traffic data fór the data stream. The Processing by the RX data processor 1460 is complementary to that performed by the TX ΜΙΜΟ processor 1420 and the TX data processor 1414 atthe device 1410. [0126] A processor 1470 periodically determines which pre-coding mátrix to use (discussed below). The processor 1470 formulates a reverse link message comprising a mátrix index portion and a ránk value portion. Adata memory 1472 may store program code, data, and other information used by the processor 1470 or other components ofthe device 1450.

[0127] The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by aTXdata processor 1438, which alsó receives traffic data fór a number of data streams from a data source 1436, modulated by a modulátor 1480, conditioned by the transceivers 1454A through 1454R, and transmitted backto the device 1410. [0128] At the device 1410, the modulated signals from the device 1450 are received by the antennas 1424, conditioned by the transceivers 1422, demodulated by a demodulator(DEMOD) 1440, and processed by a RXdata processor 1442 to extract the reverse link message transmitted by the device 1450. The processor 1430 then determines which pre-coding mátrix to use fór determining the beam-forming weights then processes the extracted message.

[0129] FIG. 14 alsó illustrates that the communication components may include one or more components that perform configuration (CONFIG.) control operations as taught herein. Fór example, a configuration control component 1490 may cooperate with the processor 1430 and/or other components ofthe device 1410 to send/receive signals to/from another device (e.g., device 1450) as taught herein. Similarly, a configuration control component 1492 may cooperate with the processor 1470 and/or other components ofthe device 1450 to send/receive signals to/from another device (e.g., device 1410). It should be appreciated that fór each device 1410 and 1450 the functionality of two or more of the described components may be províded by a single eornponent. Fór example, a single processíng eornponent may provide the functionality ofthe configuration control component 1490 and the processor 1430 and a single Processing eornponent may provide the functionality ofthe configuration control eornponent 1492 and the processor 1470.

[0130] The teachings herein may be incorporated intő various types of communication systems and/or system components. In somé aspects, the teachings herein may be employed in a multiple-access system capable of supporting communication with multiple users bysharing the available system resources (e.g., by specifying one or more of bandwidth, transmit power, coding, interleaving, and so on). Fór example, the teachings herein may be applied to any one or combinations ofthe following technologies: Code Division Multiple Access (CDMA) systems, Multiple-Carrier CDMA (MCCDMA), Wideband CDMA (W-CDMA), High-Speed Packet Access (HSPA, HSPA+) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Single-Carrier FDMA(SC-FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, or other multiple access techniques. A wireless communication system employing the teachings herein may be designed to implement one or more standards, such as IS-95, cdma2000, IS856, W-CDMA, TDSCDMA, and other standards. A CDMA network may implement a rádió technology such as Universal Terrestrial Rádió Access (ÚTRA), cdma2000, or somé other technology. ÚTRA includes W-CDMA and Low Chip Rate (LCR). The cdma2000 technology covers IS-2000, IS-95 and IS-856 standards. ATDMA network may implement a rádió technology such as Global System fór Mobile Communications (GSM). An OFDMA network may implement a rádió technology such as Evolved ÚTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM®, etc. ÚTRA, EUTRA, and GSM are part of Universal Mobile Telecommunication System (UMTS). The teachings herein may be implemented in a 3GPP Long Term Evolution (LTE) system, an Ultra-Mobile Broadband (UMB) system, and other types of systems. LTE is a release of UMTS that uses E-UTRA. Although certain aspects ofthe disclosure may be described using 3GPP terminology, it is to be understood that the teachings herein may be applied to 3GPP (Re199, Re15, Re16, Re17) technology, as well as 3GPP2 (IxRTT, 1xEV-DO RelO, RevA, RevB) technology and other technologies.

[0131] The teachings herein may be incorporated intő (e.g., implemented within or performed by) a variety of apparatuses (e.g., nodes). In somé aspects, anode(e.g., a wireless node) implemented in accordance with the teachings herein may comprise an access point or an access terminál.

[0132] Fór example, an access terminál may comprise, be implemented as, or known as user equipment, a subseriber station, a subseriber unit, a mobile station, a mobile, a mobile node, a remote station, a remote terminál, a user terminál, a user agent, a user device, or somé other terminology. In somé implementations an access terminál may comprise a cellular telephoné, a cordless telephoné, a session initiation protocol (SÍP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless connection capability, orsome other suitable processíng device connected to a wireless modem. Accordingly, one

ΕΡ 2 223 552 Β1 or more aspects taught herein may be incorporated into a phone (e.g., a cellular phone or smart phone), a computer (e.g., a laptop), a portable communication device, a portable computing device (e.g., a personal data assistant), an entertainment device (e.g., a music device, a videó device, or a satellite rádió), a global positioning system device, or any other suitable device that is configured to communicate via a wireless médium.

[0133] Anaccess point may comprise, be implemented as, or known as a NodeB, an eNodeB, a rádió network controller (RNC), a base station (BS), a rádió base station (RBS), a base station controller (BSC), a base transceiverstation (BTS), a transceiverfunction (TF), a rádió transceiver, a rádió router, a basic service set (BSS), an extended service set (ESS), orsome other similar terminology.

[0134] In somé aspects a node (e.g., an access point) may comprise an access node fór a communication system. Such an access node may provide, fór example, connectivity fororto a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link to the network. Accordingly, an access node may enable another node (e.g., an access terminál) to access a network orsome otherfunctionality. In addition, it should be appreciated that one or both of the nodes may be portable or, in somé cases, relatively non-portable.

[0135] Alsó, it should be appreciated that a wireless node may be capable of transmitting and/or receiving information in a non-wireless manner (e.g., via a wired connection). Thus, a receiver and a transmitter as discussed herein may include appropriate communication interface components (e.g., electrical oroptical interface components) to communicate via a non-wireless médium.

[0136] A wireless node may communicate via one or more wireless communication links that are based on or otherwise support any suitable wireless communication technology. Fór example, in somé aspects a wireless node may associate with a network. In somé aspects the network may comprise a local area network or a wide area network. A wireless device may support or otherwise use one or more of a variety of wireless communication technologies, protocols, or standards such as those discussed herein (e.g., CDMA, TDMA, OFDM, OFDMA, WiMAX, Wi-Fi, and so on). Similarly, a wireless node may support or otherwise use one or more of a variety of correspondlng modulation or multiplexing schemes. A wireless node may thus include appropriate components (e.g., air interfaces) to establish and communicate via one or more wireless communication links using the above or other wireless communication technologies. Fór example, a wireless node may comprise a wireless transceiver with associated transmitter and receiver components that may include various components (e.g., signal generators and signal processors) that facilitate communication over a wireless médium.

[0137] The components described herein may be implemented in a variety ofways. Referring to FIGS. 15 22, apparatuses 1500, 1600, 1700, 1800, 1900, 2000, 2100, and 2200 are represented as a series of interrelated functional blocks. In somé aspects the functionality of these blocks may be implemented as a Processing system including one or more processor components. In somé aspects the functionality of these blocks may be implemented using, fór example, at least a portion ofone or more integrated circuits (e.g., an ASIC). As discussed herein, an integrated Circuit may include a processor, software, other related components, or somé combination thereof. The functionality of these blocks alsó may be implemented in somé other manner as taught herein. In somé aspects one or more of the dashed blocks in FIGS. 15-22 are optional.

[0138] The apparatuses 1500, 1600, 1700, 1800, 1900, 2000, 2100, and 2200 may include one or more modules that may perform one or more ofthe funetions described above with regard to various figures. Fór example, an identifierdetermining means 1502óra conflict identifying means 1516 may correspond to, fór example, an identifierdeterminerasdiscussed herein. An identifier selecting means 1504 may correspond to, fór example, an identifier selectoras discussed herein. A type sending means 1506 óra location sending means 1510 may correspond to, fór example, a transmitter as discussed herein. A list receiving means 1508 may correspond to, fór example, a receiver as discussed herein. A neighbor receiving, generating and sending means 1512 and an access point identifying means 1514 may correspond to, fór example, a neighbor discovery controller as discussed herein. An identifier list determining means 1602 may correspond to, fór example, a configuration controller as discussed herein. A list sending means 1604 may correspond to, fór example, a transmitter as discussed herein. A receiving means 1606 may correspond to, fór example, a receiver as discussed herein. A neighbor determining and sending means 1608 may correspond to, fór example, a neighbordeterminerasdiscussed herein. An access point identifying means 1702 may correspond to, fór example, a neighbor discovery controller as discussed herein. A configuration determining means 1704 may correspond to, fór example, a configuration determiner as discussed herein. A configuration specifying means 1706 may correspond to, fór example, a configuration controller as discussed herein. A conflict identifying means 1708 may correspond to, fór example, a configuration determiner as discussed herein. A sending means 1710 may correspond to, fór example, a transmitter as discussed herein. A receiving means 1712 may correspond to, forexample, a receiver as discussed herein. A receiving means 1802 may correspond to, fór example, a receiver as discussed herein. An access point determining means 1804 may correspond to, fór example, a neighbor determiner as discussed herein. A sending means 1806 may correspond to, fór example, a transmitter as discussed herein. A configuration determining means 1808 may correspond to, fór example, a config16

ΕΡ 2 223 552 Β1 uration controller as discussed herein. A location information sending means 1902 may correspond to, forexample, a location determiner as discussed herein. A configuration information receiving means 1904 may correspond to, fór example, a configuration controller as discussed herein. A server locating means 1906 may correspond to, fór example, a communication controller as discussed herein. A location information receiving means 2002 may correspond to, fór example, a receiver as discussed herein. A configuration information determining means 2004 may correspond to, fór example, a configuration controller as discussed herein. A configuration information sending means 2006 may correspond to, fór example, a transmitter as discussed herein. A message sending means 2102 may correspond to, fór example, a transmitter as discussed herein. A configuration server indication receiving means 2104 may correspond to, fór example, a receiver as discussed herein. An address determining means 2106 may correspond to, fór example, a communication controller as discussed herein. A request receiving means 2202 may correspond to, fór example, a receiver as discussed herein. A configuration server identifying means 2204 may correspond to, fór example, a configuration server selector as discussed herein. An indication sending means 2206 may correspond to, fór example, a transmitter as discussed herein. [0139] It should be understood that any reference to an element herein using a designation such as first, second, and so forth does nőt generally limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does nőt mean that oniy two elements may be employed there or that the first element must precede the second element in somé manner. Alsó, unless stated otherwise a set of elements may comprise one or more elements. In addition, terminology of the form at Ieast one of: A, B, or C used in the description or the claims means A or B or C or any combination of these elements.

[0140] Those of skill in the art would understand that information and signals may be represented using any ofa variety of different technologies and techniques. Fór example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0141] Those of skill would further appreciate that any ofthe various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analóg implementation, óra combination ofthe two, which may be designed using source coding or somé other technique), various forms of program or design code incorporating instructions (which may be referred to herein, fór convenience, as software or a software modulé), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways fór each particular application, bút such implementation decisions should nőt be interpreted as causing a departure from the scope of the present disclosure.

[0142] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated Circuit (IC), an access terminál, or an access point. The IC may comprise a generál purpose processor, a digital signal processor (DSP), an application specific integrated Circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute codesor instructions that reside within the IC, outside ofthe IC, or both. A generál purpose processor may be a microprocessor, bút in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may alsó be implemented as a combination of computing devices, e.g., a combination ofa DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0143] It is understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope ofthe present disclosure.

[0144] The functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmítted over as one or more instructions or code on a computer-readable médium. Computerreadable média includes both computer storage média and communication média including any médium thatfacilitates transfer of a computer program from one piacé to another. A storage média may be any available média that can be accessed byacomputer. By way of example, and nőt limitation, such computer- readable média can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other médium that can be used to carry or store desired program code in the form of instructions or data structures and that can be ac17

EP 2 223 552 Β1 cessed by a computer. Alsó, any connection is properly termed a computer-readable médium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, rádió, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, rádió, and microwave are included in the definition of médium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations ofthe above should alsó be included within the scope of computer-readable média. In summary, it should be appreciated that a computer-readable médium may be implemented in any suitable computerprogram product.

[0145] The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope ofthe disclosure. Thus, the present disclosure is nőt intended to be limited to the aspects shown herein bút is to be accorded the widest scope consistent with the scope ofthe appended claims.