Configuring identifier for access point of femto cells

Claiming priority under 35 USC 119

This application is filed November 19, 2007, with each disclosure incorporated herein by reference, and has been given agent reference number 072359P1, US Patent Provisional Application No. 60 / owned by the same applicant. U.S. Patent Application No. 989,054, filed November 19, 2007 and granted agent reference number 072360P1, US Patent Provisional Application No. 60 / 989,057, filed February 1, 2008 and granted agent reference number 080744P1 Claims the interests and priority of US Patent Provisional Application No. 61 / 025,683.

The present application relates generally to communications and, in more detail, to the construction of communication nodes, without limitation.

Introduction Wireless communication systems are widely deployed to provide various types of communications (eg, voice, data, multimedia services, etc.) to multiple users. As the demand for high-speed multimedia data services grows rapidly, the challenge is to implement an efficient and robust communication system with improved performance.

To supplement traditional mobile phone network base stations (eg, macrocells), small coverage base stations can be deployed (eg, installed in the user's home) to provide more robust indoor wireless coverage to the mobile unit. Such small coverage base stations are commonly known as access point base stations, Home Node Bs or femtocells. Generally, such small coverage base stations are connected to the Internet and the network of Bile operators via DSL routers or cable modems.

As a practical matter, these small coverage base stations can be deployed in relatively large numbers in an ad hoc manner. Therefore, improved techniques are needed to construct such base stations.

An overview of exemplary embodiments of the present disclosure will be described below. It should be understood that reference to the term aspect herein may refer to one or more aspects of the present disclosure.

The present disclosure relates to, in some embodiments, configuring an access point. In various scenarios, such access points can take the form of femto nodes, relay nodes, pico nodes, or some other type of node.

The present disclosure relates to, in some embodiments, configuring an access point based on the configuration (s) of at least one other access point. For example, an access point may acquire configuration information indicating the (s) configuration of at least one adjacent access point and select one or more configuration parameters based on the acquired configuration information. it can.

The present disclosure relates to, in some embodiments, determining the identifier used (ie, transmitted) by the access point. For example, an access point may choose an identifier based on the (s) identifier used (ie, transmitted) by at least one other access point. These identifiers can include, for example, pilot identifiers (eg, physical cell identifiers). For convenience, in the description herein, such an identifier will be referred to as a pilot identifier.

The present disclosure relates to an autonomous configuration of an access point in some embodiments. For example, when an access point is initialized (for example, during deployment, power-on, or reset), the access point can determine its location and then (for example, its configuration based on that location). Can be configured by itself. Here, the access point can determine radio frequency (RF) parameters, optimization parameters, or other parameters. For example, the access point can determine the pilot identifier, carrier frequency, power profile, some other parameter, or a combination of two or more of these parameters.

The present disclosure relates to, in some embodiments, an access point that constitutes itself with the assistance of a configuration server. For example, an access point can send information such as the location of the access point to the configuration server, which can respond to the access point with a list of any adjacent access points. The access point then acquires configuration information indicating the (s) configuration of the identified adjacent (s) access points and one or more based on the acquired configuration information. Configuration parameters can be selected.

The present disclosure relates to providing configuration information to an access point in some aspects. For example, the configuration server can provide configuration information to an access point based on the location of the access point.

The present disclosure relates to directing an access point to a configuration server in some aspects. For example, a configuration server can direct an access point to another configuration server for configuration information.

These and other exemplary embodiments of the present disclosure will be described in detail below and the appended claims, as well as in the accompanying drawings.

<figref num="1">A simplified block diagram of some exemplary embodiments of a communication system in which an access point is configured based on received information.</figref><figref num="2">Schematic showing an exemplary coverage area for wireless communication.</figref><figref num="3">A flowchart of some exemplary aspects of the actions performed to configure an access point.</figref><figref num="4">A simplified block diagram of some exemplary aspects of the components employed in a communication node.</figref><figref num="5">A simplified diagram showing exemplary behavior related to neighbor discovery.</figref><figref num="6">A simplified diagram showing exemplary behavior related to neighbor discovery.</figref><figref num="7">A flowchart of some exemplary aspects of the actions performed to configure an access point based on the configuration of one or more adjacent nodes.</figref><figref num="8">A simplified block diagram of some exemplary aspects of the components employed in a communication node.</figref><figref num="9">A flowchart of some exemplary aspects of the actions performed to configure an access point based on location.</figref><figref num="10">A flowchart of some exemplary embodiment of the actions performed to configure the access point based on the received configuration information.</figref><figref num="11">A flowchart of some exemplary embodiments of the actions performed to direct the access point to the configuration server.</figref><figref num="12">A simplified diagram of a wireless communication system.</figref><figref num="13">A simplified diagram of a wireless communication system including a femto node.</figref><figref num="14">A simplified block diagram of some exemplary embodiments of communication components.</figref><figref num="15">A simplified block diagram of some exemplary embodiments of a device configured to perform the configuration-related operations taught herein.</figref><figref num="16">A simplified block diagram of some exemplary embodiments of a device configured to perform the configuration-related operations taught herein.</figref><figref num="17">A simplified block diagram of some exemplary embodiments of a device configured to perform the configuration-related operations taught herein.</figref><figref num="18">A simplified block diagram of some exemplary embodiments of a device configured to perform the configuration-related operations taught herein.</figref><figref num="19">A simplified block diagram of some exemplary embodiments of a device configured to perform the configuration-related operations taught herein.</figref><figref num="20">A simplified block diagram of some exemplary embodiments of a device configured to perform the configuration-related operations taught herein.</figref><figref num="21">A simplified block diagram of some exemplary embodiments of a device configured to perform the configuration-related operations taught herein.</figref><figref num="22">A simplified block diagram of some exemplary embodiments of a device configured to perform the configuration-related operations taught herein.</figref>

By convention, the various features shown in the drawings may not be drawn to a certain scale. Therefore, the dimensions of various features may be optionally scaled up or down for clarity. In addition, some of the drawings may be simplified for clarity. Therefore, the drawings do not show all the components of a given device (eg, device) or method. Finally, the same reference numbers may be used to indicate the same features throughout the specification and figures.

Various aspects of the disclosure will be described below. It will be apparent that the teachings herein can be practiced in a wide variety of forms and that the particular structures, functions, or both disclosed herein are only representative. Based on the teachings herein, it is noted that the embodiments disclosed herein can be implemented independently of the other embodiments, and that two or more of these embodiments can be combined in various ways. If you are a trader, please understand. For example, any number of aspects described herein can be used to implement the device or implement the method. Further, in addition to or using one or more of the embodiments described herein, or by using other structures, functions, or structures and functions, such devices are realized, or such methods. Can be carried out. Further, the embodiment can comprise at least one element of the claim.

Figure 1 shows some nodes in an exemplary communication system 100 (eg, part of a communication network). For purposes of illustration, various aspects of the disclosure are described in the context of one or more access terminals, access points, and network nodes communicating with each other. However, it should be understood that the teachings herein are applicable to other types of devices, or other similar devices referenced using other terms. For example, the access points taught herein can be implemented or referred to as base stations, eNodeBs, Home eNodeBs, and the like. Further, the access terminal taught in this specification can be implemented or called as a mobile device, a user device, or the like. In addition, network nodes can be implemented or called as configuration servers, operational billing management (OAM) entities, mobility managers, and so on. Other exemplary terms are described in the description below.

An access point in System 100 has one or more services (eg, network connectivity) that are located within the relevant geographic area or roaming across the relevant geographic area. Provide to a wireless terminal (for example, access terminal 102). For example, at various times, the access terminal 102 can connect to the access point 104 or the access point 106. Each of the access points 104 and 106 can communicate with one or more network nodes (represented by network node 108 for convenience) to enable wide area network connectivity. Such network nodes take various forms, such as one or more radio and / or core network entities (eg, implemented as described above or as some other suitable network entity). be able to.

In some embodiments, the configuration of an access point, such as the access point 104, can be advantageously achieved by performing configuration functions on the access point. For example, in a network with a relatively large number of access points, it becomes more efficient for the overall operation of the network if each access point has the ability to configure itself, at least to some extent. In this way, operators of networks (eg, centralized entities managed by operators) are relieved of at least some of the burden of determining the appropriate configuration for all of these access points and tracking the configuration. Sometimes.

In the example of FIG. 1, the access point 104 includes a configuration controller 110 that constitutes the access point 104. Here, the configuration controller 110 can provide one or more configuration parameters used by the access point 104 to communication-related operations. For example, the configuration controller 110 can provide configuration parameters such as pilot identifier, operating frequency and transmit power to the wireless transceiver 112.

In some implementations, the configuration controller 110 defines configuration parameters based on the configuration (s) of at least one other access point (eg, adjacent access points). For this purpose, the configuration controller 110 is used to receive configuration information from other (s) access points and / or to retrieve configuration information from other (s) access points. You can receive the information you can.

In some cases, the access point 104 may communicate with the access point 106 to determine the configuration of the access point 106. For example, the access point 104 can communicate with the access point 106 via a backhaul (eg, by network node 108). As a more specific example, the eNodeB can receive reports (eg, via the X2 interface) about PCI used by adjacent eNodeBs.

In addition, the access point 104 can directly acquire configuration-related information from the access point 106 via a wireless signal. For example, the access point 104 can include a downlink receiver (not shown in FIG. 1) that receives the signal transmitted by the access point 106. As a more specific example, the PCI used by the eNodeB can be heard wirelessly on another eNodeB using a downlink receiver.

The access point 104 can also acquire configuration-related information through the access terminal (eg, when the access terminal 102 is serviced by the access point 104). For example, the access terminal 102 can transfer the information acquired from the access point 106 (for example, the information derived from the transmission by the access point 106) to the access point 104. As a more specific example, the user equipment can report the PCI used by one eNodeB to another eNodeB.

In some cases, the access point 104 can receive configuration-related information from the network node 108. For example, network node 108 can identify any neighbor on access point 104 and send this neighbor information to access point 104. The configuration controller 110 then uses this neighbor information to determine the configuration of the indicated neighbor (s).

In some cases, network node 108 sends a list of pilot identifiers to access point 104. The access point 104 can then select its pilot identifier from the list. For example, access point 104 can randomly select a pilot identifier from the list, or select a pilot identifier based on defined criteria (s). Here, the access point 104 can exclude any pilot identifier used by another access point (eg, an adjacent access point) from its selection.

As a more specific example, an OAM entity can signal a list of PCI values to eNodeB. This list can be cell-specific. The eNodeB can then select the PCI value of the cell from the list of PCIs. For example, eNodeB can randomly select a PCI value from the list of PCIs.

In some cases, the eNodeB is reported by the user device, reported by the adjacent eNodeB, listened wirelessly over the downlink, acquired in some other way, or acquired by a combination of two or more of these methods. The received list can be restricted by deleting the PCI. The eNodeB can then randomly select a PCI value from the restricted list of PCIs, or select a PCI value from the restricted list in some other way.

In some cases, the access point 104 may provide information to the configuration server (eg, represented by network node 108) to assist the configuration server in providing the configuration information to the access point 104. For example, the access point 104 can determine its location and send the corresponding location information to network node 108. The network node 108 can then determine the appropriate configuration information based on the location and send this configuration information to the access point 104, and the configuration controller 110 uses the configuration information to configure the access point 104. ..

In some cases, the configuration server (represented by network node 108, for example) directs the access point to another configuration server for configuration information. For example, upon receiving a configuration information request from access point 104, network node 102 can redirect access point 104 to another node (eg, another configuration server). Such redirection can be based, for example, on the location of access point 104 and / or the load on one or more of the configuration servers.

Configuration actions such as the above actions can be advantageously adopted in the network 200 shown in FIG. 2, where one access point provides macro coverage and another access point provides smaller coverage. Here, the macro coverage area 204 can be provided by a macro access point in a wide area cellular network, such as a 3G network, commonly referred to as a macro cell network or wide area network (WAN), for example. In addition, the smaller coverage area 206 can be provided, for example, by access points in a residential or building-based network environment, commonly referred to as a local area network (LAN). When an access terminal (AT) travels through such a network, the access terminal is serviced by an access point that provides macro coverage at one location and by an access point that provides less coverage at another location. May be done. In some embodiments, smaller coverage access points can be used to provide increasing capacity, indoor coverage, and a variety of services, all of which result in a more robust user experience.

In the description of the present specification, a node that provides coverage over a relatively large area (for example, an access point) is called a macro node, and a node that provides coverage over a relatively small area (for example, a residence) is called a femto node. is there. It should be appreciated that the teachings herein may be applicable to nodes associated with other types of coverage areas. For example, a piconode can provide coverage over an area smaller than a macro area and larger than a femto area (eg, coverage within a commercial building). Relay nodes can also provide wireless coverage that allows access points to communicate with other nodes in the network. In other words, a relay node can provide, for example, a wireless backhaul that allows connectivity to a network node or another relay node. In various applications, other terms may be used to refer to macro nodes, femto nodes, or nodes of other access point types. For example, macronodes can be configured or called as access nodes, base stations, access points, eNodeBs (eNBs), macrocells, and so on. In addition, the femto node, Home NodeB, Home It may be configured or referred to as an eNodeB, access point, base station, access point base station, eNodeB, femtocell, etc. In some implementations, nodes can be associated (eg, split) with one or more cells or sectors. A cell or sector associated with a macro node, femto node, or pico node may be referred to as a macro cell, femto cell, or pico cell, respectively. For convenience, the description herein generally refers to the operation and components of access points and femtonodes. It should be appreciated that these behaviors and components are also applicable to other types of nodes (eg relay nodes and pico nodes).

In the example of FIG. 2, several tracking areas 202 (or routing areas or location areas) are defined, each of which contains several macro coverage areas 204. Here, the coverage areas associated with the tracking areas 202A, 202B and 202C are indicated by thick lines and the macro coverage area 204 is represented by a hexagon. As mentioned above, the tracking area 202 can also include the femto coverage area 206. In this example, each of the femto coverage areas 206 (eg, femto coverage area 206C) is shown within one or more macro coverage areas 204 (eg, macro coverage area 204B). However, it should be understood that the femto coverage area 206 is not completely within the macro coverage area 204. Also, one or more pico-coverage areas or femto-coverage areas (not shown) can be defined within a given tracking area 202 or macro-coverage area 204.

Many access points, such as femtonodes, can be deployed in the network, as indicated by the small cells in macrocoverage area 204A. In such cases, it is advantageous to adopt the teachings herein to configure these access points. With the above overview in mind, the various techniques adopted to construct the access point according to the teachings herein will be described with reference to FIGS. 3-11. 3-6 relate, in some embodiments, to the behavior and components employed to determine the pilot identifier used by the access point. 7-9 relate, in some embodiments, to the behaviors and components employed to configure the access point based on the configuration of at least one other node. FIG. 10 relates to an operation adopted to give configuration information to an access point in some embodiments. FIG. 11 relates to an operation adopted to direct the access point to the configuration server in some embodiments.

For illustration purposes, for the operations of FIGS. 3, 5-7 and 9-11 (or other operations discussed or taught herein), certain components (eg, the configuration of system 100) It may be described as being performed by an element, a component shown in FIG. 4, or a component shown in FIG. However, it should be understood that these actions can be performed by other types of components and can be performed using a different number of components. It should also be appreciated that one or more of the actions described herein may not be adopted in a given implementation.

4 and 8 show some exemplary components that are incorporated into nodes such as access points, network nodes, and access terminals to perform the configuration operations taught herein. The described components can also be incorporated into other nodes in the communication system. For example, other nodes in the system (eg, other access points) have components similar to those described for access points 402 and / or access points 802 that provide similar functionality.

As shown in FIG. 4, the access point 402 and the network node 404 (eg, the configuration server) can include transceivers 406 and 408 for communicating with other nodes, respectively. The transceiver 406 includes a transmitter 410 for transmitting a signal (eg, a message) and a receiver 412 for receiving the signal (including, for example, configuration-related information). The transceiver 408 includes a transmitter 414 for transmitting a signal and a receiver 416 for receiving the signal. Similarly, the access point 802 and network node 804 (eg, the configuration server) shown in FIG. 8 include transceiver 806 (including transmitter 808 and receiver 810) and transceiver 806 (including transmitter 814 and receiver 816), respectively. ) Can include transceiver 812. Also, the access terminal 818 shown in FIG. 8 can include a transceiver 820 (including a transmitter 822 and a receiver 824).

The nodes of FIGS. 4 and 8 also include other components that can be used in conjunction with the configuration operations taught herein. For example, as shown in FIG. 8, the access point 802, network node 804, and access terminal 818, respectively, for managing communication with other nodes (eg, sending and receiving messages / instructions), and herein. Communication controllers 826, 828 and 830 can be included to perform other related functions taught in. Also, as shown in FIG. 8, one or more of the access point 802, network node 804, and access terminal 818, respectively, for performing configuration-related operations and other associations taught herein. It can include configuration controllers 832 (eg, with integrated reference point agent IRPAgent), 834 and 836 (with, for example, integrated reference point manager IRPManager) to perform the function. Illustrative behavior of the other components of FIGS. 4 and 8 will be described below.

For convenience, the nodes of FIGS. 4 and 8 are shown as including the components used in the various examples described below in relation to FIGS. 3-11. As a practical matter, one or more of the components shown may not be used in a given example. As an example, in some implementations, the access terminal 818 may not include the conflict detector 838 and / or the configuration controller 836. As another example, in some implementations, network node 804 may not include one or more of configuration controller 834, neighbor determiner 840, or configuration server selector 842. As yet another example, in some implementations, access point 802 may not include location determiner 844.

Also, a given node can include one or more of the components described. For example, a node allows multiple transceivers to allow the node to operate simultaneously on multiple frequencies and / or communicate over different types of technologies (eg, wired and / or wireless technologies). Can include components.

Then, with reference to FIGS. 3 and 4, access by pilot identifier is based on the pilot identifier (s) used by at least one other access point, adopting the teachings herein. Points can be constructed. Using such a method, access points in the network can select pilot identifiers (eg, autonomously) in a decentralized manner. In this way, the possibility of pilot identifier collisions in the network (for example, when a node hears multiple access points broadcasting the same pilot identifier) can be reduced or eliminated. Moreover, this can be achieved without the need for a centralized manager to assign and track all of the pilot identifiers used by all of the access points in the network.

Pilot identifiers can take many forms and are referred to using different terms in different implementations. For example, a pilot identifier may be referred to as a cell identifier (cell ID), a physical cell identifier (PCI), or a primary scramble sequence (PSC). In addition, the pilot identifier can be associated with the pseudo-random noise sequence (PN sequence) present in the pilot signal.

In some implementations, as represented by block 302 in FIG. 3, the configuration server (eg, network node 404 in FIG. 4) has a pilot identifier that can be used by a given access point (eg, access point 402). Determine the list of and send the list to the access point. In the example of FIG. 4, these operations can be performed by the configuration controller 418.

Here, the list of pilot identifiers can include a subset (eg, 10 pilot identifiers) of a set of all pilot identifiers (eg, 512 pilot identifiers) defined for a given network. .. In some implementations, the list has various pilot identifiers.

The list of pilot identifiers can be configurable operators. In some cases, a given list is applicable across the network of operators (for example, multiple access points in the network are assigned the same list). In some cases, a unique list can be defined for different access points. For example, you can assign each access point in your network its own list (although not all of these lists are unique).

In some implementations, the operator can divide the pilot identifier space into different subsets. The pilot identifier space can be divided based on various criteria.

In some implementations, the pilot identifier space is divided into different subsets for different types of access points. For example, assigning a first subset of pilot identifiers (eg, pilot identifiers 0-49) to macro access points, assigning a second subset of pilot identifiers (eg, pilot identifiers 50-499) to femtonodes, and assigning pilot identifiers A third subset (eg, pilot identifiers 500-511) can be assigned to mobile access points.

In some implementations, the pilot identifier space is divided into different subsets based on the access point's transmit power. For example, assign a first subset of pilot identifiers to higher power access points (for example, macro access points) and a second subset of pilot identifiers for lower power access points (for example, femtonodes, piconodes, or relay nodes). Can be assigned.

In some implementations, the pilot identifier space can be divided into different subsets based on location. For example, different pilot identifier subsets can be defined for different geographic areas. Therefore, the subset of pilot identifiers assigned to a given access point may depend on the location of the access point.

In view of the above, in some implementations, the behavior of the configuration server in block 302 can be based on the information that the configuration server receives from access point 402. For example, at some point (for example, when access point 402 establishes an internet connection), access point 402 uses its network connectivity to communicate with network node 404 and send this information.

The access point 402 (eg, location determiner 420) can determine information indicating the location of the access point 402 and send this information to the network node 404. Such information can take various forms. For example, information indicating the location of an access point includes the city in which the access point is located, the state in which the access point is located, the country in which the access point is located, the macro access point that serves the access point, the zone with which the access point is associated, and access. It can indicate the cell with which the point is communicating, the network identification or operator with which the cell is associated, GPS coordinates, geographic location, or at least one of the location addresses.

Further, or as an alternative, the access point 402 can send information indicating the type of the access point 402 to the network node 404. As mentioned above, this information can take various forms. For example, this type information includes the device type of the access point 402 (eg, femto, macro, mobile, etc.), the power type of the access point 402 (eg, high power, low power, etc.), and the access point (eg, herein). Whether restricted (as taught in), whether the access point is fixed or mobile, or one of any other characteristics (s) associated with access point 402 or Multiple can be shown.

The network node 404 (eg, configuration controller 418) can then determine the list of pilot identifiers used by the access point 402 based on the information it receives from the access point 402. In some embodiments, the network node 404 uses a range of pilot identifiers pre-supplied by the operator for use by the indicated node type and / or for use at the indicated location. You can select a valid range of pilot identifiers.

As mentioned above, some or all of the behavior of block 302 is not utilized in some implementations. For example, in some cases the pilot identifier list (eg range) is standardized. In such a case, network node 404 only sends a list of standard pilot identifiers to access point 402. Alternatively, the access point 402 can be configured with a pilot identifier list, so that the access point 402 does not receive this information from the network node 404.

As represented by block 304 in FIG. 3, the access point 402 (eg, pilot identifier determiner 422) determines at least one pilot identifier used by at least one other access point. For example, access point 402 can determine which pilot identifier is being used by its neighbor.

In some implementations, access point 402 (eg, neighbor discovery controller 424) can perform neighbor discovery to identify its neighbor. As discussed in more detail below, access point 402 can discover 1-hop neighbors or multi-hop neighbors (eg, 2-hop, 3-hop, etc.). In the latter case, access point 402 may choose to crawl two or three or more hops to obtain pilot identifier information from farther neighbors.

In some implementations, the access point 402 acquires configuration information from a neighbor through neighbor discovery. For example, as a result of a neighbor discovery request issued by neighbor discovery controller 424, access point 402 from a neighbor access point (for example, a one-hop or multi-hop neighbor) contains a neighbor that contains the pilot identifier used by that neighbor access point. You can receive the discovery response. Such a neighbor discovery operation can be performed, for example, through a backhaul.

In some implementations, access point 402 can obtain pilot identifier information for its neighbors from a server (eg, network node 404). For example, a network node 404 (eg, Neighbor Judge 426) can maintain this information on its own or retrieve it on request. The network node 404 can then send pilot identifier information to the access point 402 in response to a request from the access point 402. In some embodiments, the network node 404 can identify the pilot identifier information as being given based on the location of the access point 402. For example, in the request, the access point 402 can include information indicating its location. The network node 404 can then identify access points in its vicinity and determine which pilot identifier they use. In addition, network node 404 takes into account the transmit power of these access points when determining whether the pilot signals transmitted by these access points can be received by the node that also receives the pilot signals from access points 402. You can put it in. In this way, only those pilot identifiers that can potentially cause pilot identifier conflicts can be transmitted to the access point 402.

In some implementations, access point 402 can first acquire a list of its neighbors and then make neighbor discoveries on the access points identified by the list. For example, a network node 404 (for example, Neighbor Judge 426) may send such a list to access point 402 based on the location of access point 402 (for example, given to network node 404 by access point 402). Can be done. Also, the access terminal associated with the access point 402 (eg, serviced by the access point 402) either listens to which access point the access point currently listens to (ie, receives the signal from which access point), or A report indicating previously heard can be sent to access point 402.

In some implementations, access point 402 can determine the pilot identifier used by a neighbor without formal neighbor discovery. For example, access point 402 may include a downlink receiver (eg, represented by receiver 412) configured to detect a pilot signal from adjacent access points. That is, the access point 402 can receive the configuration information wirelessly. In this case, access point 402 determines the pilot identifier used by these adjacent access points (eg, based on the PN sequence derived from the received pilot signal) based on the detected signal (eg, based on the received pilot signal). , Neighbor identification information can be determined at will (by analyzing the information in other downlink messages).

In some implementations, access point 402 can receive pilot identifiers or other neighbor information from access terminals (eg, access terminal 102 in FIG. 1). For example, the access terminal associated with the access point 402 can send a report to the access point 402 indicating the pilot signal being received by the access terminal. Here, the access terminal can derive information (for example, a pilot identifier, a PN sequence, or other access point identification information) from a signal received by the access terminal and transfer this information to the access point 402.

As represented by block 306 in FIG. 3, access point 402 (eg, pilot identifier selector 428) is based on the pilot identifier determined by block 304 and, where applicable, the specified pilot identifier list. Select the pilot identifier used by access point 402 based on. For example, access point 402 may select from a specified list a pilot identifier that does not conflict with (eg, is not the same) any pilot identifier used by adjacent access points.

The access point 402 can attempt to avoid conflicts with its immediate neighbor (eg, one-hop neighbor) and, optionally, the pilot identifier of the multi-hop neighbor. The discovery of multi-hop neighbors is discussed in more detail below in relation to Figures 5 and 6.

The access point 402 organizes its neighbor's pilot identifiers into groups that can be used in the pilot identifier selection process. Such groups can be organized in various ways. For example, the first group can include a pilot identifier heard by access point 402 and / or a pilot identifier reported by an access terminal associated with access point 402. The second group may contain a second hop neighbor identified during neighbor discovery, but only those identified by a neighbor list given by an adjacent femto node (eg, low power access point). it can. The third group contains the second hop neighbor identified during neighbor discovery, but only those identified by the neighbor list given by the adjacent macro access point (eg, high power access point). Can be done. Here, adjacent macro access points may report a large number of femtonode neighbors, most of which are located relatively far from access point 402 and are therefore used by access point 402. Differentiation can be adopted between Group 2 and Group 3 as it is less likely to cause conflict with the pilot identifier.

Continuing with the above example, one of the pilot identifiers in the specified list is not used by any of the access point 402 neighbors (for example, by any of the identifiers in groups 1, 2 and 3). If the access point 402 can simply select this pilot identifier. Conversely, if all of the pilot identifiers in the specified set are used by at least one of the neighbors, access point 402 is one of the access points from group 3 with any of the pilot identifiers in the specified set. It is possible to determine if there is a conflict with only (ie, no conflict with group 1 or group 2). If so, the access point 402 can choose one of these pilot identifiers in an attempt to minimize the risk of contention. If all of the pilot identifiers in the specified list conflict with either Group 1 or Group 2, access point 402 selects a pilot identifier that conflicts only with Group 2 (if such a pilot identifier exists). be able to. In some implementations, access point 402 is unable to select a pilot identifier from group 1. If there are a plurality of pilot identifiers to be selected from among them, the access point 402 can select one of the pilot identifiers at random or in some other specified way.

As represented by block 308, access point 402 is then configured to use the pilot identifier chosen for wireless communication. For example, transmitter 410 can use the selected pilot identifier to generate a pilot signal that transmitter 410 broadcasts.

As represented by block 310, the access point 402 can continue to monitor the pilot identifier used by its neighbors (eg, using the behavior of block 304), so the access point uses it. You can continue to ensure that your pilot identifier does not conflict with the pilot identifier used by your neighbors. For example, such contention may be caused by a new access point recently installed near the access point 402, or by a mobile access point that has entered the vicinity of the access point 402. Also, if two access points that are not within listening to each other choose the same pilot identifier, pilot identifier conflicts (eg, collisions) can occur. Such conflicts can ultimately be detected, for example, by access terminals that receive signals from both access points. In such cases, one or both of the access points can be configured to change their pilot identifier. As described below in connection with FIG. 7, the access terminal that detects the conflict can notify one or all of the related access points. For example, an access terminal connects to one of these access points to pass this information, or uses a connection to another access point that the access terminal has to access this information. Can be sent to points.

If a conflict is identified, the access point 402 can perform an operation similar to that described above in order to select a new pilot identifier that does not conflict with any pilot identifier used by any adjacent access point. Therefore, using these techniques, the access point 402 can independently recover from pilot identifier conflicts (eg, pilot identifier conflicts). For example, upon receiving a conflict notification or identifying a conflict, the access point 402 moves its current pilot identifier to a group of identifiers pointed out as banned (eg, Group 1 above), described above. You can repeat the actions you have taken.

In some cases, when changing its pilot identifier, the access point 402 can suspend all currently held connections and reconnect the associated access terminal. As an optimization, the access point 402 can send a message before the time when it notifies the access terminal of the new pilot identifier and before the time when the access point 402 switches using the new pilot identifier. In this way, switching to the new pilot identifier can be achieved by minimizing service disruption.

Then, referring to FIGS. 5 and 6, the access point can discover its neighbors using access point start neighbor discovery and / or access terminal assisted neighbor discovery. Figure 5 shows an example of finding an access point start neighbor. Figure 6 shows an example of finding an access terminal support neighbor.

In FIG. 5, access point A can initiate neighbor discovery by learning about the existence of adjacent access point B. For example, as mentioned above, access point A may listen to the broadcast information of its RF neighbor (eg, using a downlink receiver) or obtain information about that neighbor in some other way. it can. Thus, access point A can learn an identifier (eg, an address) of one of its neighbors, as represented by block 502 in FIG.

Access point A can connect directly to its neighbor through a backhaul (for example, by the action of a neighbor discovery controller component) and perform a neighbor discovery message exchange. For example, access point A sends a neighbor discovery request (ND request) to access point B. In response, access point B sends a neighbor discovery report (ND report) to access point A (for example, by the action of a neighbor discovery controller component). Similarly, access point B sends a neighbor discovery request to access point A and receives a neighbor discovery report in response.

Advantageously, the report from access point B can include information about its neighbor (eg, access point C). For example, information about access point C can be provided with sufficient information (eg, identifier, address, etc.) to allow another node to access access point C. Here, it is understood that access point C can be a second hop (or higher hop) neighbor to access point A (for example, access point A cannot hear access point C). I want to be. In some implementations, access point B can automatically include information about its neighbors in its reporting. Alternatively, access point A may specifically require access point B to include this information in its reporting.

Therefore, access point A can communicate with the multi-hop neighbor using information about the multi-hop neighbor received from the first hop neighbor (eg, access point B). For example, as shown in FIG. 5, access point A sends a neighbor discovery request to access point C and receives a neighbor discovery report in response. Similarly, access point C sends a neighbor discovery report to access point A and receives the neighbor discovery report in response. In a similar manner, as described above, the neighbor discovery report from access point C can include information about access point C neighbors (not shown in FIG. 5). In this way, access point A can obtain information about its third hop neighbor.

In FIG. 6, access point A learns information about an access terminal assisted neighbor through discovery. Here, the access terminal sends a pilot report indicating all of the pilots received by the access terminal (for example, pilot ID 2 and other pilot IDs) to its serving access point (access point A). If the pilot ID in the pilot report is new to access point A, access point A can use the access terminal to resolve the address of the new access point (for example, the IP address). For example, access point A can send a sector ID request, or other suitable request (including, for example, the pilot ID of a new access point), to the access terminal. The access terminal can then send a sector response containing the corresponding sector ID to the access point A (or the access terminal sends some other suitable response to the access point A).

Access point A can then perform a neighbor discovery exchange with a new access point (eg, access point B). As mentioned above, in connection with FIG. 5, access point A receives information about the second hop neighbor (eg, access point C) from access point B, and then the second (one or more) second. You can discover and exchange neighbors with your hop neighbors.

Next, with reference to FIGS. 7-9, the teachings herein are generally applicable to the configuration of access points. For example, the techniques described above, as well as other techniques described herein, can be used to determine various configuration parameters for the access point. Examples of such configuration parameters include, but are not limited to, frequency band, carrier frequency, pilot identifier, maximum transmit power, and transmit power profile.

As represented by block 702 in FIG. 7, access point 802 (eg, neighbor discovery controller 846) can optionally determine its neighbor's identity. For example, access point 802 can receive a list of its neighbors from a configuration server (eg, network node 804) in a similar manner as described above. Here, the operator can provide one or more centralized configuration servers in the network to assist in the configuration of access points in the network. Once the access point 802 is initialized, it can begin the configuration process.

In some embodiments, the initialization of the access point 802 involves the access point 802 gaining connectivity with the operator's network. Here, the access point 802 needs to be authenticated before it can access the operator's network.

In addition, access point 802 can be populated with configuration servers . For example, access point 802 can be preconfigured with a well-known address (eg, IP address) of the configuration server. Alternatively, the access point 802 can recognize the operator of the network to which it is connected (for example, operator.com), so the access point 802 makes a DNS query for the FQDN "config_server.operator.com". , Can receive the IP address instead. In other implementations, the access point 802 can use some other technique to obtain the appropriate address information. The access point 802 can then establish communication with the configuration server. For example, communication can be established using standardized SNMP or other configuration protocols such as NetConf, OMA DM, CWMP (TR 069) or DOCSIS, or using proprietary CLI over SSH.

As described above, the configuration server can give the access point a neighbor list based on the location information received 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.

After initialization of the access point 802, the location determiner 844 can determine the location of the access point 802, as represented by block 902 in FIG. The location determiner 844 can determine the location in various ways. For example, the location can be determined using Global Positioning System (GPS) technology, assisted GPS technology, network-based location determination methods, RF-based methods, or any other suitable method.

As represented by block 904, access point 802 sends its location-related information (eg, estimates of its location) to network node 804. In some implementations, this behavior is initiated by the access point 802 (for example, when the access point 802 connects to the configuration server). In some implementations, the configuration server can explicitly request this location information as part of its connection setup protocol (eg, via request). The access point 802 can also send other information (eg, power profile, node type) that network node 804 can use to give an appropriate response to network node 804.

When network node 804 (for example, neighbor determiner 840) receives location information from access point 802, as represented by block 906, network node 804 identifies the neighbors of access point 802 and generates a neighbor list. .. This neighbor list can include, for example, any macro access point that is relatively close to access point 802, as well as any other access point that is geographically close to access point 802 (for example, a femtonode).

The neighbor list can be a function of the power type (or power profile) of the access point 802 and its neighbors. For example, a distant macro access point that transmits with high power may be a neighbor of access point 802. In contrast, if the coverage area of an access point 802 does not intersect with a low power access point (eg, a femtonode) that is relatively close to the access point 802, then the low power access point is not included in the neighbor list. As a result, in some cases, the access point 802 can transmit the power type information together with the location information to the network node 802. In addition, network node 804 can obtain power-related information from other access points in the network. When the neighbor list is generated, as represented by block 908, network node 804 sends the neighbor list to access point 802.

Seeing FIG. 7 again, the access point 802 (eg, configuration controller 832) determines the configuration of its neighbors, as represented by block 704. As described above, the access point 802 can acquire the configuration information of its neighbor in various ways. For example, access point 802 can connect directly to a neighbor through a backhaul, thereby reading a selected set of parameters. Access point 802 can be heard wirelessly to discover one or more parameters of an adjacent access point (eg, the pilot identifier described above). The access point 802 can use access terminal assisted neighbor discovery, which allows the access terminal associated with the access point 802 to send configuration information to the access point 802. For example, the access terminal 818 (for example, the configuration controller 836) can notify the access point 802 of the neighbor access points heard by the access terminal 818. The access point 802 can also receive neighbor node configuration information from a configuration server such as the network node 804 (eg, configuration controller 834) discussed herein. It should be appreciated that the access point 102 may obtain configuration information using one or more of the techniques described herein, or by using other techniques.

As represented by block 706, the access point 802 (eg, configuration determiner 848) can specify the configuration for access point 802 based on the configuration information obtained in block 704. In some embodiments, the access point 802 can autonomously select its own set of parameters (eg, RF parameters), depending on its neighbor's parameters (eg, RF parameters).

In some cases, the access point 802 can select its power profile based on one or more power profiles of its neighbors. For example, access point 802 can choose the same power profile used by its neighbors. Alternatively, the access point 802 can select a power profile that complements the power profile (s) used by its (s) neighbors. The power profile can define, for example, maximum transmit power, different transmit power for different conditions, or other power parameters.

As mentioned above, in some cases, the access point 802 can choose a pilot identifier (eg, pilot PN) based on the pilot identifier used by its neighbors. For example, access point 802 can choose a pilot identifier that is different from its neighbors.

In some cases, the access point 802 can select a carrier wave (eg, RF frequency band) based on the carrier wave (s) used by its neighbors. For example, adjacent nodes in the network can choose a complementary set of carrier priorities (eg, indicated by a carrier mask or some other suitable indication) to implement an interference management scheme. Here, each access point radiates more energy on one carrier and less energy (for example, or not at all) on another carrier. If adjacent access points choose these carrier priorities in a complementary manner, it allows the access terminal associated with each of the access points to have a more favorable interference environment on at least some of the carriers. To do so. To achieve this in an autonomous way, new access points (eg, recently initialized access points) determine the carrier priorities used by their neighbors and themselves to supplement them as much as possible. Carrier priority can be selected.

In some embodiments, the configuration of access point 802 may depend on its location. For example, a configuration server (eg, configuration controller 834) can specify a list (eg, a subset) of parameters (eg, allowed parameter ranges) that can be used by the access point. As mentioned above, in connection with FIG. 3, the specified list can be based on the location of access point 802. For example, a specific list of power profiles available to access point 802 can be specified based on the location of access point 802. Similarly, a particular list of frequency bands available to access point 802 can be specified based on the location of access point 802. At a broader level, the city, state, or country in which the access point 802 currently resides can limit which frequency bands the access point 802 can use. For example, the same operator can own different frequency bands in different countries, or the operator can specify the use of different frequency bands in different cities.

In some implementations, the configuration information can include some optimization parameters (eg, non-radio parameters). Such parameters can include, for example, a security key that can be used to access one or more services (eg, network connectivity). Such parameters can also include the addresses of other nodes that the access point 802 needs to connect to.

As represented by block 708 in FIG. 7, access point 802 can then use the configuration specified in block 706 for communication or other operation. For example, as mentioned above, transceiver 806 uses the determined RF parameters to determine which pilot identifier should be advertised, on which carrier it should operate, and the transmission power level to use on these carriers. Can be configured to.

As represented by block 710, access point 802 can continue to monitor its neighbor's configuration to detect conflicts (eg, conflicts). As mentioned above, in the case of a conflict, the access point 802 can perform the configuration operation described above to resolve the conflict.

In some implementations, the access point 802 can receive contention instructions from an access terminal (eg, access terminal 818). For example, if access terminal 818 detects a conflict (for example, conflict detector 838 detects two access points that use the same pilot identifier), access terminal 818 sends a corresponding message to access point 802. be able to. Based on this message, the configuration controller 802 can perform the above actions to select a different configuration for the access point 802.

It should be appreciated that the above-mentioned behaviors and components related to FIGS. 7-9 are applicable to the configuration scheme described herein with reference to other figures. For example, these behaviors and components can be used in connection with configuring pilot identifiers for access points (eg, described above in connection with FIGS. 3-6).

Then, referring to FIGS. 10 and 11, in some implementations, the access point can obtain configuration information from another node (eg, configuration server), which allows the configuration information to be on the access point. Depends on location. For convenience, the operation of FIGS. 10 and 11 will be described in the context of access point 802 and network node 804 of FIG.

The access point 802 (eg, location determiner 844) determines its location and provides this information to network node 804, as represented by blocks 1002 and 1004 in FIG. Therefore, this operation can be similar to the location determination operation described above (eg, in blocks 902 and 904).

As represented by block 1006, network node 804 (eg, configuration controller 834) determines configuration information for access point 802 based on received location information. For example, as described above, the configuration information can include RF parameters, optimization parameters, other parameters, or a combination of two or more of these parameters. In some cases, this behavior may result in an entirely new configuration defined for access point 802. Alternatively, network node 804 may define only some parameters used by access point 802.

Network node 804 sends configuration information to access point 802, as represented by block 1008. The access point 802 is then configured to use the received configuration information (block 1010).

Then, referring to FIG. 11, in some cases, the configuration server may choose to redirect the access point to a different configuration server. For example, such decisions can be made based on the location of the access point and / or the load on the configuration server.

As represented by block 1102, access point 802 sends a message to network node 804 to obtain configuration information. As mentioned above, such a message can include information indicating the location of access point 802.

As represented by block 1104, network node 804 (eg, configuration server selector 842) can determine whether to give the requested configuration information. For example, network node 804 can determine that another configuration server (for example, closer to access point 802) should process the request based on the location of access point 802. Network node 804 can also choose to redirect requests based on the load on network node 804. For example, if network node 804 is heavily loaded, network node 804 can redirect requests to another unloaded configuration server.

If network node 804 decides to process the request, as represented by blocks 1106 and 1108, network node 804 can provide the requested configuration information to access point 802. For example, this behavior can be similar to the behavior described above in connection with FIG.

If network node 804 decides not to process the request (for example, based on its load or proximity of access point 802), as represented by block 1110, then network node 804 (for example, configuration server selector) 842) identifies another configuration server that can provide configuration information to access point 802. For this purpose, network node 804 can maintain a database containing information about other configuration servers on the network. Further, or alternative, network node 804 can be configured, made discoveries, or communicate with another node to obtain this information.

As represented by block 1112, network node 804 sends instructions from other configuration servers (eg, in the form of redirection messages) to access point 802. In some implementations, the instructions can include information that allows the access point 802 to determine the addresses of other configuration servers. For example, the instructions can include the location of the configuration server (eg, city). Upon receiving this information, the access point 802 can determine the addresses of other configuration servers (eg, via DNS queries).

In some implementations, the instructions can include the addresses of other configuration servers. In some implementations, redirection can be achieved by configuration servers that set parameters that indicate the addresses of different configuration servers. The access point 802 then attempts to establish a connection with the new configuration server if it determines that this parameter has changed.

As represented by block 1114, access point 802 can therefore send a message to get configuration information to other configuration servers. The access point 802 can start the user communication operation when the configuration exchange with the configuration server is completed.

As described above, the teachings herein can be implemented in networks that employ macro access points, femto nodes, relay nodes, and the like. Figures 12 and 13 show examples of how access points are deployed in such networks. Figure 12 shows in a simplified form how cells 1202 (eg, macrocells 1202A to 1202G) of a wireless communication system 1200 are serviced by the corresponding access points 1204 (eg, access points 1204A to 1204G). Shown. Here, the macro cell 1202 can correspond to the macro coverage area 204 of FIG. As shown in FIG. 12, access terminals 1206 (eg, access terminals 1206A-1206L) can be distributed to various locations throughout the system over time. Each access terminal 1206 has a forward link (FL) and / or a reverse link (FL) and / or reverse link (FL) at a given moment, depending on, for example, whether the access terminal 1206 is active and whether the access terminal 1206 is in soft handover. It can communicate with one or more access points 1204 on "RL"). Using this cellular scheme, the wireless communication system 1200 can serve over a large geographic area. For example, each of the macrocells 1202A to 1202G can cover several blocks within the neighborhood or several square miles of the local environment.

Figure 13 shows an example of how one or more femtonodes are deployed in a network environment (for example, System 1200). In system 1300 of FIG. 13, multiple femtonodes 1310 (eg, femtonodes 1310A and 1310B) are installed in a relatively small area coverage network environment (eg, in one or more user residences 1330). Each fem node 1310 is a wide area network 1340 (eg, the Internet) and (eg, the network nodes discussed herein) via a DSL router, cable modem, wireless link, or other means of connection (not shown). Can be coupled to the mobile operator core network 1350.

Owners of Femtonode 1310 can subscribe to mobile services, such as 3G mobile services offered via the Mobile Operator Core Network 1350. In addition, the access terminal 1320 can operate in both macro environments and smaller area coverage (eg, residential) network environments. In other words, depending on the current location of the access terminal 1320, the access terminal 1320 is either by the macrocell access point 1360 associated with the mobile operator core network 1350 or by one of a set of femtonodes 1310 (eg, corresponding). It may be serviced by femtonodes 1310A and 1310B) residing in the user's residence 1330. For example, when the subscriber is outside the home, serviced by a standard macro access point (eg, access point 1360), and when the subscriber is near or inside the home, a femto node (eg, node 1310A). ) Served by. Here, the femto node 1310 is backward compatible with the legacy access terminal 1320.

The femtonode 1310 can be deployed on a single frequency, or, as an alternative, on multiple frequencies. Depending on the particular configuration, a single frequency, or one or more of the frequencies, may overlap one or more frequencies used by the macro access point (eg, access point 1360). ..

In some embodiments, the access terminal 1320 can be configured to connect to a preferred femto node (eg, the home femto node of the access terminal 1320) whenever such connectivity is possible. For example, whenever the access terminal 1320A is in the user's residence 1330, it is desirable that the access terminal 1320A communicate only with the home femto node 1310A or 1310B.

In some embodiments, the access terminal 1320 operates within the macrocellular network 1350, but if it is not resident on its most preferred network (eg, defined in the preferred roaming list), the access terminal 1320 , Better system selection (BSR) can be used to continue exploring the most preferred network (eg, preferred femtonode 1310), with better system selection currently available for better systems. Periodic scans of available systems can be performed to determine if and then efforts can be made to associate with such preferred systems. The acquisition entry can be used by the access terminal 1320 to limit the search for a particular band and channel. For example, the search for the most preferred system can be repeated periodically. Upon discovery of the preferred femtonode 1310, the access terminal 1320 selects the femtonode 1310 to camp within its coverage area.

Femtonodes may be restricted in some embodiments. For example, a given femtonode can provide some services to only some access terminals. In deployments with so-called restricted (or restricted) associations, a given access terminal is provided by a macrocell mobile network and a defined set of femtonodes (eg, femtonodes 1310 residing within the corresponding user residence 1330). Only serviced. In some implementations, a node is restricted so that it does not give at least one of signaling, data access, registration, paging, or service to at least one node.

In some embodiments, a restricted femto node (sometimes referred to as a limited subscriber group Home Node B) is a node that provides services to a restricted set of prepared access terminals. This set can be expanded temporarily or permanently as needed. In some embodiments, a limited subscriber group (CSG) can be defined as a set of access points (eg, femtonodes) that share a common access control list of access terminals. The channel on which all femtonodes in the region (or all restricted femtonodes) operate is sometimes referred to as a femto channel.

Therefore, there are various relationships between a given femto node and a given access terminal. For example, from the point of view of an access terminal, an open femto node refers to a femto node that has no restricted association (for example, the femto node allows access to any access terminal). A restricted femtonode refers to a femtonode that is somehow restricted (eg, restricted for association and / or registration). A home femtonode refers to a femtonode that an access terminal is allowed to access and operate on (for example, persistent access is given to a defined set of one or more access terminals). .. A guest femtonode refers to a femtonode that is temporarily allowed to be accessed or run on it by an access terminal. Foreign femtonodes are femtonodes that access terminals are not allowed to access or operate on, except in an emergency (eg, 911).

From the point of view of a restricted femto node, a home access terminal refers to an access terminal that is allowed access to the restricted femto node (for example, the access terminal has persistent access to the femto node). A guest access terminal is an access terminal that has temporary access to a restricted femtonode (for example, limited based on expiration date, time of use, bytes, connection count, or some other criterion). Point to. Foreign access terminals do not have permission to access restricted femtonodes, except in emergencies, such as perhaps 911 (for example, a certificate or permission to register with a restricted femtonode). Access terminal that does not have).

For convenience, the disclosure herein describes various functions in the context of femtonodes. However, it should be noted that piconodes or relay nodes can provide different (larger) coverage areas with the same or similar functionality. For example, it is possible to limit a pico node or relay node to a given access terminal, define a home pico node or home relay node, and so on.

The teachings herein can be implemented in various types of communication devices. In some embodiments, the teachings herein can be implemented in a wireless device that can be deployed in a multiple access communication system that can simultaneously support communication for multiple wireless access terminals. Here, each terminal communicates with one or more access points via transmission over forward and reverse links. A forward link (also known as a downlink) refers to a communication link from an access point to a terminal, and a reverse link (also known as an uplink) refers to a communication link from a terminal to an access point. Point to. This communication link can be established via a one-input, one-output system, a multi-input multi-output (MIMO) system, or some other type of system.

For illustration purposes, FIG. 14 illustrates exemplary communication components that can be used in wireless devices in the context of MIMO-based system 800. System 1400 has multiple (N) for data transmission_T) Transmitting antennas and multiple (N)_R) Use one receiving antenna. N_TTransmitting antennas and N_RThe MIMO channel formed by the receiving antennas is sometimes called the spatial channel N_SCan be decomposed into independent channels, where N_S min {N_T, N_R}. N_SEach of the independent channels corresponds to one dimension. MIMO systems can provide improved performance (eg, higher throughput and / or greater reliability) when the additional dimensions generated by multiple transmit and receive antennas are utilized.

System 1400 supports Time Division Duplex (TDD) and Frequency Division Duplex (FDD). In the TDD system, forward and reverse link transmissions are performed on the same frequency domain, so it is possible to estimate the forward link channel from the reverse link channel by the reciprocity theorem. This allows the access point to extract the transmit beam forming gain on the forward link when multiple antennas are available at the access point.

System 1400 includes a wireless device 1410 (eg, an access point) and a wireless device 1450 (eg, an access terminal). On device 1410, traffic data from several data streams is fed from the data source 1412 to the transmit (TX) data processor 1414.

In some embodiments, each data stream is transmitted through its own transmitting antenna. To supply the encoded data, the TX data processor 1414 formats, encodes, and interleaves the traffic data for each data stream based on the particular encoding scheme selected for that data stream.

The encoded data in each data stream can be multiplexed with pilot data using OFDM techniques. Pilot data is typically a known data pattern that is processed in a known manner and can be used in the receiver system to estimate the channel response. The multiplexed pilot and encoded data of each data stream is then subjected to a particular modulation scheme (eg, BPSK, QSPK, M-PSK, or, for example, BPSK, QSPK, M-PSK, or) selected for that data stream to supply the modulation symbols. Modulated (ie, symbol mapping) based on M-QAM). The data transfer rate, coding, and modulation of each data stream is determined by the instructions executed by processor 1430. Data memory 1432 stores program code, data, and other information used by processor 1430 or other components of device 1410.

Modulation symbols for all data streams are then fed to the TX MIMO processor 1420, which further processes the modulation symbols (for example, in the case of OFDM). The TX MIMO processor 1420 then_TN modulation symbol streams_TSupply to 1422A ~ 1422T transceivers ("XCVR"). In some embodiments, the TX MIMO processor 1420 adds beam forming weights to the symbols of the data stream and to the antenna on which the symbols are transmitted.

Each transceiver 1422 receives and processes its own symbol stream to supply one or more analog signals, and further tunes (eg, amplifies, filters, and upconverts) those analog signals. Provides a modulated signal suitable for transmission over a MIMO channel. Then N from transceivers 1422A ~ 1422T_TEach of the modulated signals is N_TIt is transmitted from the antennas 1424A to 1424T.

On device 1450, the transmitted modulated signal is N_RIt is received by the antennas 1452A to 1452R, and the received signal from each antenna 1452 is supplied to the respective transceiver (XCVR) 1454A to 1454R. Each transceiver 1454 tunes (eg, filters, amplifies, and downconverts) its received signal, digitizes the tuned signal, supplies samples, and processes those samples to accommodate the corresponding " Supply the "receive" symbol stream.

The receive (RX) data processor 1460 is then N based on a particular receiver processing technique._RTransceivers 1454 to N_RReceives, processes, and N_TSupply a "detection" symbol stream. The RX data processor 1460 then demodulates, deinterleaves, and decodes each detected symbol stream to recover traffic data to the data stream. The processing by the RX data processor 1460 complements the processing performed by the TX MIMO processor 1420 and the TX data processor 1414 on device 1410.

Processor 1470 periodically determines which precoding matrix (discussed below) should be used. Processor 1470 creates a reverse link message with a matrix index section and a rank value section. Data memory 1472 stores program code, data, and other information used by other components of the processor 1470 or device 1450.

The reverse link message can include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 1438, which also receives traffic data from some data streams from the data source 1436, modulated by the modulator 1480, tuned by transceivers 1454A-1454R, and to device 1410. Be returned.

At device 1410, the modulated signal from device 1450 is received by antenna 1424, tuned by transceiver 1422, demodulated by demodulator (DEMOD) 1440, processed by RX data processor 1442, and transmitted by device 1450. The reverse link message is extracted. Processor 1430 then determines which precoding matrix should be used to determine the beam formation weights, and then processes the extracted messages.

FIG. 14 also shows that a communication component can include one or more components that perform the configuration (CONFIG) control operation taught herein. For example, the configuration control component 1490 works with processor 1430 and / or other components of device 1410 to transmit / send signals to and from another device (eg, device 1450) as taught herein. Can be received. Similarly, the configuration control component 1492 can work with the processor 1470 and / or other components of device 1450 to send / receive signals to and from another device (eg, device 1410). .. Please understand that for each device 1410 and 1450, more than one function of the described components can be provided by a single component. For example, a single processing component can provide the functionality of component control component 1490 and processor 1430, and a single processing component can provide the functionality of component control component 1492 and processor 1470.

The teachings herein can be incorporated into various types of communication systems and / or system components. In some embodiments, the teachings herein are by sharing available system resources (eg, by specifying one or more of bandwidth, transmit power, encoding, interleaving, etc.). , Can be used in multiple access systems that can support communication with multiple users. For example, the teachings herein are Code Division Multiple Access (CDMA) systems, Multiple Carrier CDMA (MCCDMA), Wideband. CDMA ("W-CDMA"), high-speed packet access ("HSPA", "HSPA +") system, time-division multiple access ("TDMA") system, frequency-division multiple access ("FDMA") system, single carrier FDMA ( Applies to any one or combination of techniques of "SC-FDMA") systems, orthogonal frequency division multiple access ("OFDMA") systems, or other multiple access techniques. Wireless communication systems that use the teachings herein are designed to implement one or more standards, including IS-95, cdma2000, IS-856, W-CDMA, TDSCDMA, and other standards. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, or some other technology. UTRA includes W-CDMA and low chip rates (LCR). cdma2000 technology covers IS-2000, IS-95, and IS-856 standards. TDMA network is Global System for Mobile Wireless technologies such as Communications (GSM®) can be implemented. OFDMA networks can implement wireless technologies such as evolutionary UTRA (E-UTRA), IEEE802.11, IEEE802.16, IEEE802.20, and Flash-OFDM®. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunication System (UMTS). The teachings herein can be implemented in 3GPP Long Term Evolution (LTE) systems, Ultra Mobile Broadband (UMB) systems, and other types of systems. LTE is a release of UMTS that uses E-UTRA. Although some aspects of the disclosure are described using 3GPP terminology, the teachings herein are 3GPP (Rel99, Rel5, Rel6, Rel7) techniques, as well as 3GPP2 (IxRTT, 1xEV-DO Rel0, RevA). , RevB) Please understand that it can be applied to technology and other technologies.

The teachings herein can be incorporated into various devices (eg, nodes) (eg, implemented within the device or performed by the device). In some embodiments, a node implemented according to the teachings herein (eg, a wireless node) may include an access point or access terminal.

For example, an access terminal comprises a user device, a subscriber station, a subscriber unit, a mobile station, a mobile, a mobile node, a remote station, a remote terminal, a user terminal, a user agent, a user device, or some other term. May be implemented as, or known as either. In some embodiments, the access terminal is a cellular phone, a cordless phone, a session initiation protocol ("SIP") phone, a wireless local loop ("WLL") station, a personal digital assistant ("PDA"), and wireless connectivity. It can include a handheld device that it has, or any other suitable processing device that is connected to a wireless modem. Accordingly, one or more aspects taught herein are telephones (eg, cellular phones or smartphones), computers (eg, laptops), portable communication devices, portable computing devices (eg, personal digital assistants). ), Entertainment devices (eg, music or video devices, or satellite radios), global positioning system devices, or other suitable devices configured to communicate via wireless media.

Access points include node B, eNodeB, wireless network controller ("RNC"), base station ("BS"), wireless base station ("RBS"), base station controller ("BSC"), transmission / reception base station ("BSC"). "BTS"), Transceiver Function ("TF"), Wireless Transceiver, Wireless Router, Basic Service Set ("BSS"), Extended Service Set ("ESS"), or any other similar term. May be implemented or known as either.

In some embodiments, the node (eg, an access point) can include an access node for the communication system. Such access nodes can provide connectivity for or to a network, for example, over a wired or wireless communication link to the network, for a network (eg, a wide area network such as the Internet or a cellular network). Thus, an access node can allow another node (eg, an access terminal) to access the network or some other function. Furthermore, please understand that one or both nodes can be portable or, in some cases, relatively non-portable.

Also, please understand that wireless nodes can send and / or receive information in a wired manner (eg, over a wired connection). Thus, the receivers and transmitters discussed herein can include suitable communication interface components (eg, electronic or optical interface components) for communicating over wired media.

Wireless nodes can communicate over one or more wireless communication links based on or support suitable wireless communication techniques. For example, in some embodiments, a wireless node can be associated with a network. In some embodiments, the network can comprise a local area network or a wide area network. The wireless device may support or support one or more of the various wireless communication technologies, protocols, or standards as described herein (eg, CDMA, TDMA, OFDM, OFDMA, WiMAX, Wi-Fi, etc.). Can be used. Similarly, a wireless node can support or use one or more of a variety of corresponding modulation or multiplexing schemes. Therefore, the wireless node shall include the appropriate components (eg, air interface) to establish one or more wireless communication links using the above or other wireless communication technologies and communicate through them. Can be done. For example, a wireless node is a wireless transceiver with associated transmitter and receiver components that can include various components that enable communication over wireless media (eg, signal generators and signal processors). Can be provided.

The components described herein can be implemented in a variety of ways. With reference to FIGS. 15-22, the devices 1500, 1600, 1700, 1800, 1900, 2000, 2100 and 2200 are represented as a series of interrelated functional blocks. In some embodiments, the functionality of these blocks can be implemented as a processing system that includes one or more processor components. In some embodiments, the functionality of these blocks can be implemented, for example, using at least a portion of one or more integrated circuits (eg, ASICs). As discussed herein, integrated circuits can include processors, software, other related components, or any combination thereof. The functionality of these blocks can also be implemented in some other way than the methods taught herein. In some embodiments, one or more dashed block blocks in FIGS. 15-22 are optional.

Devices 1500, 1600, 1700, 1800, 1900, 2000, 2100, and 2200 can include one or more modules capable of performing the one or more functions described above with respect to various figures. For example, identifier determination means 1502 or competition identification means 1516 may correspond, for example, to the identifier determination devices discussed herein. The identifier selection means 1504 may correspond, for example, to the identifier selectors discussed herein. The type transmitter 1506 or location transmitter 1510 may correspond, for example, to the transmitters discussed herein. The list receiving means 1508 may correspond, for example, to the receivers discussed herein. Neighbor reception generation transmission means 1512 and access point identification means 1514 may correspond to the neighbor discovery controller discussed herein. The identifier list determination means 1602 may correspond, for example, to the configuration controller discussed herein. The list transmitting means 1604 may correspond, for example, to the transmitters discussed herein. The receiving means 1606 may correspond, for example, to the receivers discussed herein. Neighbor determination transmitting means 1608 may correspond to, for example, the neighbor determination device discussed herein. The access point identification means 1702 may correspond, for example, to the neighbor discovery controller discussed herein. The configuration determination means 1704 may correspond, for example, to the configuration determination devices discussed herein. Configuration designation means 1706 may correspond, for example, to the configuration controllers discussed herein. Competitive identification means 1708 may correspond, for example, to the configuration decision makers discussed herein. Transmission means 1710 may correspond, for example, to the transmitters discussed herein. The receiving means 1712 may correspond, for example, to the receivers discussed herein. Receiving means 1802 may correspond, for example, to the receivers discussed herein. The access point determination means 1804 is, for example, a book. It may correspond to the neighbor judge discussed in the specification. Transmission means 1806 may correspond, for example, to the transmitters discussed herein. Configuration determination means 1808 may correspond, for example, to the configuration controllers discussed herein. The location information transmitting means 1902 may correspond to, for example, the location determiner discussed herein. The configuration information receiving means 1904 may correspond, for example, to the configuration controller discussed herein. The server placement means 1906 may correspond, for example, to the communication controller discussed herein. The location information receiving means 2002 may correspond, for example, to the receivers discussed herein. The configuration information determination means 2004 may correspond, for example, to the configuration controller discussed herein. The configuration information transmitting means 2006 may correspond, for example, to the transmitters discussed herein. The message transmitting means 2102 may correspond, for example, to the transmitters discussed herein. The configuration server instruction receiving means 2104 may correspond, for example, to the receivers discussed herein. The address determination means 2106 may correspond, for example, to the communication controller discussed herein. The request receiving means 2202 may correspond, for example, to the receivers discussed herein. The configuration server identification means 2204 may correspond, for example, to the configuration server selectors discussed herein. The instruction transmitting means 2206 may correspond, for example, to the transmitters discussed herein. It may correspond to the communication controller discussed in the detailed document. The location information receiving means 2002 may correspond, for example, to the receivers discussed herein. The configuration information determination means 2004 may correspond, for example, to the configuration controller discussed herein. The configuration information transmitting means 2006 may correspond, for example, to the transmitters discussed herein. The message transmitting means 2102 may correspond, for example, to the transmitters discussed herein. The configuration server instruction receiving means 2104 may correspond, for example, to the receivers discussed herein. The address determination means 2106 may correspond, for example, to the communication controller discussed herein. The request receiving means 2202 may correspond, for example, to the receivers discussed herein. The configuration server identification means 2204 may correspond, for example, to the configuration server selectors discussed herein. The instruction transmitting means 2206 may correspond, for example, to the transmitters discussed herein. It may correspond to the communication controller discussed in the detailed document. The location information receiving means 2002 may correspond, for example, to the receivers discussed herein. The configuration information determination means 2004 may correspond, for example, to the configuration controller discussed herein. The configuration information transmitting means 2006 may correspond, for example, to the transmitters discussed herein. The message transmitting means 2102 may correspond, for example, to the transmitters discussed herein. The configuration server instruction receiving means 2104 may correspond, for example, to the receivers discussed herein. The address determination means 2106 may correspond, for example, to the communication controller discussed herein. The request receiving means 2202 may correspond, for example, to the receivers discussed herein. The configuration server identification means 2204 may correspond, for example, to the configuration server selectors discussed herein. The instruction transmitting means 2206 may correspond, for example, to the transmitters discussed herein.

It should be understood that references to elements using names such as "first" and "second" herein do not generally limit the quantity or order of those elements. Rather, these names can be used herein as a convenient way to distinguish between two or more elements or multiple examples of an element. Therefore, references to the first and second elements do not mean that only two elements can be used there, or that the first element must somehow precede the second element. Also, unless otherwise specified, a set of elements may include one or more elements. In addition, the term "at least one of A, B, or C" used in the claims or claims means "A or B or C, or any combination of these elements." To do.

Those skilled in the art will appreciate that information and signals can be represented using any of a variety of different techniques and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description are voltages, currents, electromagnetic waves, magnetic or magnetic particles, light fields or optical particles, or them. It can be expressed by any combination of.

In addition, any of the various exemplary logic blocks, modules, processors, means, circuits, and algorithm steps described with respect to the aspects disclosed herein are electronic hardware (eg, source coding or some other). Various forms of program or design code that incorporate instructions, such as digital or analog implementations, or a combination of the two, that can be designed using techniques (for convenience, "software" or "software modules" herein. It will be appreciated by those skilled in the art that it can be implemented as a combination of both) or both. To articulate this compatibility between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been generally described above with respect to their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but decisions on such implementation should not be construed as causing deviations from the scope of this disclosure.

The various exemplary logic blocks, modules and circuits described with respect to aspects disclosed herein can be implemented or implemented within integrated circuits (ICs), access terminals, or access points. ICs are general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, individual gate or transistor logic, individual hardware components, electronic It can be a component, an optical component, a mechanical component, or any combination of them designed to perform the functions described herein, inside the IC, outside the IC, It can execute code or instructions that reside in or both. The general purpose processor can be a microprocessor, but as an alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. Processors can also be implemented as a combination of computing devices, such as a DSP and microprocessor combination, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration. ..

It should be understood that the particular order or hierarchy of steps in the disclosed process is an example of an exemplary approach. It should be understood that, based on design preferences, the particular order or hierarchy of steps in the process can be reconstructed within the scope of this disclosure. The attached method claims present the elements of the various steps in an exemplary order and are not limited to the particular order or hierarchy presented.

The features described can be implemented in hardware, software, firmware, or a combination thereof. When implemented in software, a function can be stored on a computer-readable medium as one or more instructions or codes, or transmitted via a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that allows the transfer of computer programs from one location to another. The storage medium can be any available medium accessible by the computer. By way of example, but not by limitation, such computer-readable media are RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage, or in the form of instructions or data structures. Any other medium that can be used to carry or store the desired program code and is accessible by a computer can be provided. Also, any connection is properly called a computer-readable medium. For example, the software uses coaxial cable, fiber optic cable, twist pair, digital subscriber line (DSL), or wireless technology such as infrared, wireless, and microwave from a website, server, or other remote source. When transmitted, coaxial cables, fiber optic cables, twisted pairs, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the definition of medium. The discs and discs used herein are compact discs (CDs), laser discs (registered trademarks) (discs), optical discs, and digital versatile discs (DVDs). ), Flop (registered trademark) discs and Blu-ray discs (disks) usually play data magnetically, and discs play data optically with a laser. To do. The above set Matches should also be included within the scope of computer-readable media. In summary, it should be understood that computer-readable media can be implemented in any suitable computer program product.

In view of the above, in some embodiments, the first method of communication is to send information indicating the location of the access point from the access point and to receive configuration information for the access point at the access point. That is, the configuration information is to be received based on the information indicating the location. Moreover, in some embodiments, at least one of the following can be applied to the first method of communication. The configuration information includes at least one RF parameter. The configuration information includes at least one of a group consisting of a frequency band, a carrier frequency, a pilot identifier, a maximum transmit power, and a transmit power profile. The access point sends information indicating the location to the configuration server, and receives the configuration information from the configuration server. The method further comprises receiving a request for location information from the configuration server, and the access point sends location information in response to the request. The method further comprises deploying a configuration server. The configuration information has at least one optimization parameter, and the location information associates the city where the access point is located, the country where the access point is located, the macro access point that serves the access point, and the access point. Indicates at least one of a group of zones, cells with which the access point is communicating, GPS coordinates, geographic location, and location address. The access point comprises a femto node or a relay node.

In some embodiments, the second method of communication is to receive information indicating the location of the access point, determine configuration information for the access point based on the information indicating the location, and obtain configuration information. Equipped with sending to the access point. Moreover, in some embodiments, at least one of the following can be applied to the second method of communication. The configuration information includes at least one RF parameter. The configuration information includes at least one of a group consisting of a frequency band, a carrier frequency, a pilot identifier, a maximum transmit power, and a transmit power profile. The method further comprises sending a request for location information, which is received in response to the request. The configuration information has at least one optimization parameter. The location information includes the city where the access point is located, the country where the access point is located, the macro access point that serves the access point, the zone with which the access point is associated, and the cell with which the access point is communicating. Indicates at least one of a group consisting of GPS coordinates, geographic location, and location address. This method is executed by the configuration server.

In some embodiments, a third method of communication is to send a first message to the first configuration server to obtain configuration information for the access point and in response to the first message. It includes receiving instructions from the second configuration server from the first configuration server and sending a second message to the second configuration server to acquire configuration information for the access point. Moreover, in some embodiments, at least one of the following can be applied to a third method of communication. The instructions include the address of the second configuration server. The method further comprises determining the address of the second configuration server based on the instructions. The first message includes information indicating the location of the access point, and the instruction of the second configuration server is received based on the information indicating the location. The location information includes the city where the access point is located, the country where the access point is located, the macro access point that serves the access point, the zone with which the access point is associated, and the cell with which the access point is communicating. , Indicates at least one of a group consisting of the operator network served by the access point, GPS coordinates, geographic location, and location address. The configuration information includes at least one RF parameter. The configuration information includes at least one of a group consisting of a frequency band, a carrier frequency, a pilot identifier, a maximum transmit power, and a transmit power profile. The configuration information has at least one optimization parameter. The access point comprises a femto node or a relay node.

In some aspects, a fourth method of communication is to receive a request for configuration information for the access point on the first configuration server and identify a second configuration server that can provide the configuration information. And to send instructions for a second configuration server in response to a request. Moreover, in some embodiments, at least one of the following can be applied to a fourth method of communication. The identification of the second configuration server is based on the load on the first configuration server and / or the load on the second configuration server. The identification of the second configuration server is based on the location on the first configuration server and / or the location on the second configuration server. The request comprises information indicating the location of the access point, and the identification of the second configuration server is based on the information indicating the location. The location information includes the city where the access point is located, the country where the access point is located, the macro access point that serves the access point, the zone with which the access point is associated, and the cell with which the access point is communicating. , Indicates at least one of a group consisting of the operator network served by the access point, GPS coordinates, geographic location, and location address. The instructions include the address of the second configuration server. The configuration information includes at least one RF parameter. The configuration information includes at least one of a group consisting of a frequency band, a carrier frequency, a pilot identifier, a maximum transmit power, and a transmit power profile. The configuration information has at least one optimization parameter.

In some embodiments, a fifth method of communication is to identify at least one neighbor access point on the first access point and determine at least one configuration on at least one neighbor access point. One access point comprises specifying at least one configuration for the first access point based on at least one configuration of at least one neighbor access point. Moreover, in some embodiments, at least one of the following can be applied to the fifth method of communication. Specifying at least one configuration comprises specifying at least one RF parameter. Specifying at least one configuration specifies at least one of a group consisting of frequency band, carrier frequency, pilot identifier, maximum transmit power, transmit power profile, and set of carrier priority. Be prepared. Specifying at least one configuration comprises specifying a power profile that is the same as the power profile of at least one neighbor access point. Specifying at least one configuration comprises specifying a pilot identifier that is different from any pilot identifier used by at least one neighbor access point. Specifying at least one configuration comprises specifying a set of carrier priorities that complements another set of carrier priorities used by at least one neighbor access point. The method identifies a conflict between at least one determined configuration and the configuration previously specified for the first access point, and in response to the conflict identification of the first access point. Further provides for specifying a non-conflicting configuration for. At least one configuration decision is to receive configuration information wirelessly at the first access point, receive configuration information from the relevant access point at the first access point, and backhaul at the first access point. Receiving configuration information through the hall and to the first access point It has at least one of the groups that consists of receiving configuration information from the server. The determination of at least one configuration comprises receiving information indicating at least one configuration of at least one multi-hop neighbor access point. The identification of at least one neighbor access point is that the first access point sends information indicating the location of the first access point and / or the power profile of the first access point, and at the first access point. , To receive instructions from at least one neighbor access point, comprising receiving instructions based on transmitted information. The first access point sends location information to the configuration server and receives instructions from the configuration server. The first access point sends location information to at least one other neighbor access point and receives instructions from at least one other neighbor access point. The location information is associated with the city where the first access point is located, the country where the first access point is located, the macro access point that serves the first access point, and the first access point. At least one of a group consisting of a zone, a cell with which the first access point is communicating, an operator network served by the first access point, GPS coordinates, a geographic location, and a location address. Show one. The first access point comprises a femto node or a relay node. It comprises transmitting information indicating a profile and receiving instructions from at least one neighbor access point at the first access point, the instructions being based on the transmitted information. The first access point sends location information to the configuration server and receives instructions from the configuration server. The first access point sends location information to at least one other neighbor access point and receives instructions from at least one other neighbor access point. The location information is associated with the city where the first access point is located, the country where the first access point is located, the macro access point that serves the first access point, and the first access point. At least one of a group consisting of a zone, a cell with which the first access point is communicating, an operator network served by the first access point, GPS coordinates, a geographic location, and a location address. Show one. The first access point comprises a femto node or a relay node. It comprises transmitting information indicating a profile and receiving instructions from at least one neighbor access point at the first access point, the instructions being based on the transmitted information. The first access point sends location information to the configuration server and receives instructions from the configuration server. The first access point sends location information to at least one other neighbor access point and receives instructions from at least one other neighbor access point. The location information is associated with the city where the first access point is located, the country where the first access point is located, the macro access point that serves the first access point, and the first access point. At least one of a group consisting of a zone, a cell with which the first access point is communicating, an operator network served by the first access point, GPS coordinates, a geographic location, and a location address. Show one. The first access point comprises a femto node or a relay node. Indicates at least one of a group consisting of a network, GPS coordinates, a geographic location, and a location address. The first access point comprises a femto node or a relay node. Indicates at least one of a group consisting of a network, GPS coordinates, a geographic location, and a location address. The first access point comprises a femto node or a relay node.

In some embodiments, a sixth method of communication is to receive information indicating the location of the first access point and to base at least one neighbor access point on the first access point based on the location information. It comprises making a decision and sending instructions for at least one neighbor access point to the first access point. Moreover, in some embodiments, at least one of the following can be applied to the sixth method of communication. The method further comprises receiving information indicating the power profile of the first access point, and the determination of at least one neighbor access point is further based on the information indicating the power profile. The method further comprises receiving information indicating at least one power profile of at least one other access point, and the determination of at least one neighbor access point is further based on information indicating at least one power profile. The method further comprises determining at least one configuration of at least one neighbor access point and sending instructions for at least one configuration to the first access point. At least one configuration has at least one RF parameter. At least one configuration comprises at least one of a group consisting of a frequency band, a carrier frequency, a pilot identifier, a maximum transmit power, and a transmit power profile. The location information is associated with the city where the first access point is located, the country where the first access point is located, the macro access point that serves the first access point, and the first access point. Indicates at least one of a group consisting of a zone, a cell with which the first access point is communicating, GPS coordinates, a geographic location, and a location address. This method is executed by the configuration server.

In some embodiments, the function corresponding to one or more of the above embodiments relating to the first, second, third, fourth, fifth, and sixth methods of communication is, for example, a book. It can be implemented in an apparatus using the structure taught in the specification. In addition, the computer program product provides the computer with a function corresponding to one or more of the above aspects relating to the first, second, third, fourth, fifth, and sixth methods of communication. It can be equipped with a code configured to allow it.

The above description of the disclosed aspects is provided to enable those skilled in the art to carry out or use the present disclosure. Various changes to these embodiments will be readily apparent to those skilled in the art and the general principles defined herein can be applied to other embodiments without departing from the scope of the present disclosure. Therefore, the disclosure is not limited to the embodiments presented herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein.