Access point configuration schemes

Access point configuration scheme

The system of this application is about communication, and more specifically (but not exclusively), about configuring communication nodes.

This application claims the rights and priority of the following jointly owned US provisional patent applications: US provisional patent application No. 60/989,054 filed on November 19, 2007 and the attorney file number is 072359P1, November 2007 The U.S. Provisional Patent Application No. 60/989,057 filed on February 19 and the attorney file number is 072360P1, and the U.S. Provisional Patent Application No. 61/025,683 filed on February 1, 2008 and the attorney file number is 080744P1, The disclosures of each of these patent applications are incorporated herein by reference.

Wireless communication systems are widely deployed to provide various types of communication (for example, voice, data, multimedia services, etc.) to multiple users. With the rapid growth in demand for high-speed and multimedia data services, there is a challenge to implement an effective and robust communication system with enhanced performance.

In order to supplement the conventional mobile phone network base station (for example, a macro cell), a small coverage base station (for example, installed in a user's home) can be deployed to provide more stable indoor wireless coverage to the mobile unit. These small coverage base stations are usually called access point base stations, native NodeB or femto cells. Usually, these small coverage base stations are connected to the Internet and mobile operators' networks via DSL routers or cable modems.

In practice, these small coverage base stations can be deployed in a special way and in a relatively large number. Therefore, there is a need for improved technologies for configuring such base stations.

A summary of the sample aspect of this disclosure is as follows. It should be understood that any reference to the term aspect herein can refer to one or more aspects of the present disclosure.

In a certain aspect, the present disclosure relates to configuring access points. In various scenarios, the access point can take the form of a pico node, a relay node, a pico node, or some other type of node.

In a certain aspect, the present disclosure relates to configuring an access point based on the configuration of at least one other access point. For example, the access point can obtain configuration information indicating the configuration of at least one adjacent access point and select one or more configuration parameters based on the obtained configuration information.

In a certain aspect, the present disclosure relates to determining the identifier to be used (ie, transmitted) by the access point. For example, the access point may select the identifier based on the identifier used (ie, transmitted) by at least one other access point. These identifiers may include, for example, pilot identifiers (e.g., physical cell identifiers). For convenience, the description herein refers to this identifier as a pilot identifier.

In a certain aspect, the present disclosure relates to the autonomous configuration of the access point. For example, once the access point is initialized (e.g., after deployment, power-on, or reset), the access point can determine its location and then configure itself (e.g., by determining the configuration based on its location). 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 data file, some other parameter, or a combination of two or more of these parameters.

In a certain aspect, the present disclosure relates to an access point that utilizes assistance from a configuration server to configure itself. For example, the access point can send information such as the location of the access point to the configuration server, and the configuration server can respond to that access point with a list of any adjacent access points. The access point can then obtain configuration information indicating the configuration of the identified adjacent access point, and select one or more configuration parameters based on the obtained configuration information.

In some aspects, the present disclosure is about providing configuration information to the access point. For example, the configuration server can provide configuration information to the access point based on the location of the access point.

In some aspects, the present disclosure relates to directing the access point to the configuration server. For example, the configuration server can direct the access point to another configuration server for the configuration information.

These and other sample aspects of the present disclosure will be described in the following detailed description and the scope of additional patent applications and in the accompanying drawings.

Various aspects of the present disclosure are described below. It should be obvious that the teachings in this article can be embodied in various forms, and any specific structure, function, or both disclosed in this article are only representative. Based on the teachings in this article, those familiar with the technology should understand that the aspects disclosed in this article can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects described herein can be used to implement the device or method of practice. In addition, in addition to or different from one or more of the aspects stated herein, other structures, functions, or structures and functions may be used to implement the device or practice the method. In addition, the aspect may include at least one element of the scope of the patent application.

Figure 1 illustrates several nodes in a sample communication system 100 (e.g., part of a communication network). For illustrative purposes, various aspects of the present disclosure will be described in the context of one or more access terminals, access points, and network nodes in communication with each other. However, it should be understood that the teachings herein can be applied to other types of devices or other similar devices referred to by other terms. For example, the access point as taught herein can be implemented or referred to as a base station, eNodeB, native eNodeB, and so on. In addition, the access terminal as taught herein can be implemented or referred to as a mobile, user equipment, and so on. In addition, network nodes can be implemented or referred to as: configuration servers; operation, account processing and management ("OAM") entities; mobility managers; and so on. Other sample terms are stated in the following discussion.

The access point in the system 100 provides one or more services (e.g., Network connectivity). For example, the access terminal 102 can be connected to the access point 104 or the access point 106 at various points in time. Each of the access points 104 and 106 may communicate with one or more network nodes (represented by the network node 108 for convenience) to facilitate wide area network connectivity. The network nodes may take various forms, such as one or more radio and/or core network entities (e.g., implemented as discussed above or implemented as some other suitable network entity).

In some aspects, the configuration of the access point can be advantageously achieved by providing configuration functionality at the access point such as the access point 104. For example, in a network with a relatively large number of access points, it may be more important for the overall operation of the network when each access point has the ability to configure itself at least to a certain extent. Effective. In this way, it is possible to relieve at least some of the burden of the operator of the network (for example, a centralized entity managed by the operator) of determining the appropriate configuration and remembering the configuration of all such access points.

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

In some embodiments, the configuration controller 110 defines the configuration parameters based on the configuration of at least one other access point (for example, an adjacent access point). To this end, the configuration controller 110 can receive configuration information from other access points and/or receive information that can be used to obtain configuration information from other access points.

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

In addition, the access point 104 can directly obtain configuration-related information from the access point 106 via wireless signals. For example, the access point 104 may include a downlink receiver (not shown in FIG. 1) that receives signals transmitted by the access point 106. As a more specific example, the PCI used by the eNodeB can be listened to in the air at another eNodeB by using a downlink receiver.

The access point 104 can also obtain configuration-related information through the access terminal (for example, when the access terminal 102 is being served by the access point 104). For example, the access terminal 102 can forward the information obtained from the access point 106 (for example, information obtained from the transmission of the access point 106) to the access point 104. As a more specific example, the user equipment can report the PCI used by the eNodeB to another eNodeB.

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

In some cases, the network node 108 sends the list of pilot identifiers to the access point 104. The access point 104 can then select its pilot identifier from the list. For example, the access point 104 may randomly select pilot identifiers from the list or select pilot identifiers based on defined criteria. Here, the access point 104 can choose to exclude any pilot identifiers used by other access points (for example, neighboring access points).

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

In some cases, the eNodeB may be removed by the user equipment, reported by the neighboring eNodeB, listened in the air via the downlink, acquired in some other way, or via two or both of these methods. The PCI obtained by the combination of the two or more is used to limit the received list. The eNodeB can then randomly select the PCI value from the restricted PCI list or in some other way select the PCI value from the restricted list.

In some cases, the access point 104 may provide information to the configuration server (eg, as represented by the network node 108) to assist the configuration server in providing configuration information to the access point 104. For example, the access point 104 can determine its location and send the corresponding location information to the 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, where the configuration controller 110 uses the configuration information to configure the access point 104.

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

Configuration operations such as the configuration operations described above can be advantageously used in the network 200 as shown in FIG. 2 where some access points provide huge coverage and other access points provide less coverage. Here, the mega coverage area 204 may be provided by, for example, a mega access point of a large area cellular network (such as a 3G network) commonly referred to as a mega cell network or a wide area network ("WAN"). In addition, the smaller coverage area 206 may be provided by, for example, an access point in a residential or building-based network environment commonly referred to as a local area network ("LAN"). When an access terminal ("AT") moves across the network, the access terminal can be served by an access point that provides giant coverage at some locations, and the access terminal can be served by a provider at other locations Access point servo for smaller coverage. In some aspects, smaller coverage access points can be used to provide incremental capacity growth, in-building coverage, and different services, all of which lead to a more robust user experience.

In the description herein, a node that provides coverage over a relatively large area (for example, an access point) may be referred to as a mega node, and a node that provides coverage over a relatively small area (for example, a residence) may be referred to as As an ultra-micro node. It should be understood that the teachings in this article can be applied to nodes associated with other types of coverage areas. For example, a micro node can provide coverage in an area smaller than a mega area and larger than a super micro area (for example, coverage in a commercial building). In addition, the relay node can provide wireless coverage that enables the access point to communicate with other nodes in the network. In other words, the relay node can provide wireless backhaul that facilitates connectivity to, for example, a network node or another relay node. In various applications, other terms can be used to refer to giant nodes, ultra-micro nodes, or other access point-type nodes. For example, a mega node can be configured or referred to as an access node, base station, access point, eNodeB ("eNB"), mega cell, and so on. In addition, the pico node can be configured or referred to as a home NodeB, home eNodeB, access point, base station, access point base station, eNodeB, pico cell, and so on. In some embodiments, a node may be associated with one or more cells or sectors (e.g., divided into one or more cells or sectors). A cell or sector associated with a macro node, a pico node, or a micro node may be referred to as a macro cell, a pico cell, or a micro cell, respectively. For convenience, the description herein may generally refer to the operations and components of access points and ultra-micro nodes. It should be understood that these operations and components are also applicable to other types of nodes (for example, relay nodes and micro nodes).

In the example of FIG. 2, a number of tracking areas 202 (or routing areas or location areas) are defined, each of which includes a number of giant coverage areas 204. Here, the coverage areas associated with the tracking areas 202A, 202B, and 202C are depicted by thick lines, and the giant coverage area 204 is represented by a hexagon. As mentioned above, the tracking area 202 may also include the ultra-micro coverage area 206. In this example, each of the pico coverage areas 206 (e.g., pico coverage area 206C) is depicted as being within one or more mega coverage areas 204 (e.g., mega coverage area 204B). However, it should be understood that the ultra-micro coverage area 206 may not be completely located within the mega-coverage area 204. Furthermore, one or more micro or ultra-micro coverage areas (not shown) can be defined within a given tracking area 202 or mega coverage area 204.

As indicated by the small cells in the mega coverage area 204A, a large number of access points such as ultra-micro nodes can be deployed in the network. In this situation, the teachings herein can be advantageously used to configure these access points. With attention to the above overview, various techniques that can be used to configure the access point according to the teachings in this article will be described with reference to FIGS. 3 to 11. In a certain aspect, Figures 3 to 6 relate to operations and components that can be used to determine the pilot identifier to be used by the access point. In a certain aspect, FIGS. 7-9 are related to operations and components that can be used to configure the access point based on the configuration of at least one other node. In a certain aspect, Figure 10 is about operations that can be used to provide configuration information to the access point. In a certain aspect, Figure 11 is about operations that can be used to direct the access point to the configuration server.

For illustrative purposes, the operations of FIGS. 3, 5-7, and 9-11 (or any other operations discussed or taught herein) may be described as being defined by specific components (for example, components of system 100, diagrams) The components shown in 4, or the components shown in Figure 8) execute. However, it should be understood that these operations can be performed by other types of components and can be performed using a different number of components. It should also be understood that one or more of the operations described herein may not be used in a given embodiment.

Figures 4 and 8 illustrate several sample components that can be incorporated into nodes such as access points, network nodes, and access terminals to perform configuration operations as 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) may include components similar to those described for access point 402 and/or access point 802 to provide similar functionality.

As shown in FIG. 4, the access point 402 and the network node 404 (e.g., configuration server) may include transceivers 406 and 408, respectively, for communicating with other nodes. The transceiver 406 includes a transmitter 410 for sending signals (for example, messages) and a receiver 412 for receiving signals (for example, including configuration-related information). The transceiver 408 includes a transmitter 414 for transmitting signals and a receiver 416 for receiving signals. Similarly, the access point 802 and the network node 804 (e.g., configuration server) shown in FIG. 8 may include a transceiver 806 (including a transmitter 808 and a receiver 810) and a transceiver 812 (including a transmitter), respectively 814 and receiver 816). In addition, the access terminal 818 shown in FIG. 8 may 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 configuration operations as taught herein. For example, as shown in FIG. 8, the access point 802, the network node 804, and the access terminal 818 may include communication controllers 826, 828, and 830, respectively, for managing communication with other nodes (for example, sending And receiving messages/instructions) and used to provide other related functionality as taught in this article. As also shown in FIG. 8, one or more of the access point 802, the network node 804, and the access terminal 818 may respectively include a configuration controller 832 (for example, including an integrated reference point agent IRPAgent), 834 (for example, , Including the integrated reference point manager (IRPManager) and 836, for performing configuration-related operations and for providing other related functionality as taught in this article. The following describes the sample operations of the other components of FIG. 4 and FIG. 8.

For convenience, the nodes of FIGS. 4 and 8 are depicted as including components that can be used in the various examples described below in conjunction with FIGS. 3-11. In practice, one or more of the illustrated components may not be used in a given instance. As an example, in some embodiments, the access terminal 818 may not include the conflict detector 838 and/or the configuration controller 836. As another example, in some embodiments, the network node 804 may not include one or more of the configuration controller 834, the neighbor determiner 840, or the configuration server selector 842. As yet another example, in some embodiments, the access point 802 may not include the location determiner 844.

Also, a given node may contain one or more of the described components. For example, a node may contain multiple transceiver components that enable the node to operate in parallel on multiple frequencies and/or enable the node to communicate via different types of technologies (e.g., wired and/or wireless technologies).

Referring now to FIGS. 3 and 4, the teachings herein can be used to configure an access point with a pilot identifier based on the pilot identifier used by at least one other access point. By using this solution, the access points in the network can select (for example, autonomously select) pilot identifiers in a distributed manner. In this way, the possibility of pilot identifier collisions in the network (for example, when a node listens to multiple access points broadcasting the same pilot identifier) can be reduced or eliminated. In addition, this can be achieved without the use of a centralized manager that assigns and remembers all pilot identifiers used by all access points in the network.

The pilot identifier can take various forms and can be referred to using different terms in different embodiments. For example, the pilot identifier may be referred to as a cell identifier ("cell ID"), a physical cell identifier ("PCI"), or a primary scrambling code sequence ("PSC"). In addition, the pilot identifier can be associated with a pseudo-random noise sequence ("PN sequence") existing in the pilot signal.

As represented by block 302 in FIG. 3, in some embodiments, the configuration server (eg, network node 404 in FIG. 4) determines the guide that can be used by a given access point (eg, access point 402) Frequency identifier list 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 may include a subset (e.g., 10 pilot identifiers) of the set of all pilot identifiers (e.g., 512 pilot identifiers) defined for a given network. In some embodiments, the list contains a series of pilot identifiers.

The list of pilot identifiers can be configurable by the industry. In some cases, a given list can be applied to the entire industry's network (for example, multiple access points in the network can be assigned the same list). In some cases, a unique list can be defined for different access points. For example, each access point in the network can be assigned its own list (however, all such lists may not be unique).

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

In some embodiments, the pilot identifier space is divided into different subsets for different types of access points. For example, a mega access point may be assigned a first subset of pilot identifiers (e.g., pilot identifiers 0-49), and a pico node may be assigned a second subset of pilot identifiers (e.g., pilot identifiers 0-49). Identifiers 50-499), and the mobile access point can be assigned a third subset of pilot identifiers (e.g., pilot identifiers 500-511).

In some embodiments, the pilot identifier space is divided into different subsets based on the transmission power of the access point. For example, higher-power access points (e.g., mega-access points) can be assigned a first subset of pilot identifiers, and lower-power access points (e.g., ultra-micro nodes, micro-nodes, or medium-sized access points) can be assigned a first subset of pilot identifiers. The subsequent node) may be assigned a second subset of pilot identifiers.

In some embodiments, the pilot identifier space may be divided into different subsets based on location. For example, different pilot identifier subsets can be defined for different geographic regions. 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 embodiments, at block 302, the operation of the configuration server may be based on the information received from the access point 402 by the configuration server. For example, at a certain point in time (for example, once the access point 402 establishes an Internet connection), the access point 402 uses its network connectivity to contact the network node 404 and send this information.

The access point 402 (for example, the location determiner 420) can determine information indicating the location of the access point 402, and send this information to the network node 404. This information can take various forms. For example, the information indicating the location of the access point may indicate at least one of the following: the city where the access point is located, the state where the access point is located, the country where the access point is located, server access The giant access point of the point, the area associated with the access point, the cell communicating with the access point, the network identification code or company associated with the cell, GPS coordinates, geographic location, or street address.

In addition, or in an alternative example, the access point 402 may send information indicating the type of the access point 402 to the network node 404. As discussed above, this information can take various forms. For example, this type of information may indicate one or more of the following: the device type of the access point 402 (e.g., ultra-micro, mega, mobile, etc.), and the power type of the access point 402 (e.g., High power, low power, etc.), whether the access point is restricted (for example, as taught herein), whether the access point is stationary or mobile, or some other characteristic(s) associated with the access point 402.

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

As mentioned above, in some embodiments, some or all of the operations of the block 302 may not be used. For example, in some situations, the list of pilot identifiers (e.g., ranges) is standardized. In this situation, the network node 404 can only send the standard pilot identifier list to the access point 402. Alternatively, the access point 402 can be configured using the list of pilot identifiers so that the access point 402 does not receive this information from the network node 404.

As represented by the block 304 of FIG. 3, the access point 402 (for example, the pilot identifier determiner 422) determines at least one pilot identifier used by at least one other access point. For example, the access point 402 can determine which pilot identifiers are being used by its neighbors.

In some embodiments, the access point 402 (eg, the neighbor discovery controller 424) may perform neighbor discovery to identify its neighbors. As will be discussed in more detail below, the access point 402 may find single-hop neighbors or multi-hop neighbors (e.g., double-hop, triple-hop, etc.). In the latter case, the access point 402 may choose to crawl two or three hops or more to obtain the pilot identifier information from the more distant neighbors.

In some embodiments, the access point 402 obtains configuration information from its neighbors through neighbor discovery. For example, due to the neighbor discovery request issued by the neighbor discovery controller 424, the access point 402 can receive the relative information from the neighbor access points (for example, single-hop or multi-hop neighbors). The neighbor discovery response includes the pilot identifier used by the neighbor's access point. The neighbor discovery operation can be performed, for example, via a backhaul.

In some embodiments, the access point 402 can obtain the pilot identifier information of its neighbors from a server (for example, the network node 404). For example, the network node 404 (eg, neighbor determiner 426) can maintain this information independently or obtain this information upon request. The network node 404 may then send the pilot identifier information to the access point 402 in response to the request from the access point 402. In some aspects, the network node 404 can identify the pilot identifier information to be provided based on the location of the access point 402. For example, in its request, the access point 402 may include information indicating its location. The network node 404 can then identify the access points in the neighboring area and determine which pilot identifiers it uses. In addition, the network node 404 can consider the transmission power of such access points when determining whether the pilot signals transmitted by such access points can be received by nodes that also receive the pilot signals from the access point 402. In this way, only those pilot identifiers that can potentially cause pilot identifier collisions can be sent to the access point 402.

In some embodiments, the access point 402 may initially obtain its neighbor list and then perform neighbor discovery for the access point identified by the list. For example, the network node 404 (e.g., neighbor determiner 426) can send the list to the access point 402 based on the location of the access point 402 (e.g., it can be provided by the access point 402 to the network node 404). Point 402. Also, the access terminal associated with the access point 402 (for example, served by the access point 402) can indicate which access points the access terminal is currently listening to (that is, from which access points) or A report of which access points have been listened to is sent to the access point 402.

In some embodiments, the access point 402 can determine the pilot identifier used by its neighbors without performing formal neighbor discovery. For example, the access point 402 may include an downlink receiver (e.g., as represented by the receiver 412) configured to detect pilot signals from neighboring access points. That is, the access point 402 can receive configuration information in the air. In this situation, the access point 402 can determine the pilot identifier used by the neighboring access point based on the detected signal (for example, based on the PN sequence derived from the received pilot signal), and depending on In case, the identification of neighbors is determined (for example, by analyzing information in other downlink messages).

In some embodiments, the access point 402 can receive the pilot identifier or other neighbor information from an access terminal (for example, the access terminal 102 in FIG. 1). For example, the access terminal associated with the access point 402 may send a report to the access point 402 indicating the pilot signal that the access terminal is receiving. Here, the access terminal can obtain information (for example, pilot identifier, PN sequence, or other access point identification code information) from the signal it receives, and forward this information to the access point 402.

As represented by block 306 of FIG. 3, when applicable, the access point 402 (for example, the pilot identifier selector 428) is based on the pilot identifier determined by the block 304 and the list of designated pilot identifiers. Select the pilot identifier to be used by the access point 402. For example, the access point 402 can select a pilot identifier from the designated list that does not conflict with (for example, is not the same as) any pilot identifier used by the neighboring access point.

The access point 402 may try to avoid conflicts with the pilot identifiers of its immediate neighbors (e.g., single-hop neighbors) and (as the case may be) multi-hop neighbors. The multi-hop neighbor discovery will be discussed in more detail below in conjunction with FIGS. 5 and 6.

The access point 402 can organize the pilot identifiers of its neighbors into groups and use these groups in the pilot identifier selection process. The groups can be organized in various ways. For example, the first group may include pilot identifiers listened by the access point 402 and/or pilot identifiers reported by the access terminal associated with the access point 402. The second group may include second-hop neighbors identified during neighbor discovery, but only those identified through neighbor lists provided by neighboring ultra-micro nodes (eg, low-power access points) Neighbors. The third group may include second-hop neighbors identified during neighbor discovery, but only through the neighbor list provided by neighboring mega access points (eg, high-power access points) Neighbors. Here, the difference between group two and group three can be used because neighboring giant access points can report a large number of neighbors of ultra-micro nodes, most of which can be located relatively far from access point 402 and therefore relatively It is impossible to cause a conflict with the pilot identifier used by the access point 402.

Continuing the above example, if one of the pilot identifiers in the designated list is not used by any neighbors of the access point 402 (for example, any identifiers of group 1, group 2, and group 3), save The point 402 can only select this pilot identifier. Conversely, if all the pilot identifiers in the specified set are used by at least one of the neighbors, the access point 402 can determine whether any pilot identifiers in the specified set are only compatible with the access points from group three. Conflict (that is, there is no conflict with group one or group two). If so, the access point 402 can select one of these pilot identifiers in an attempt to minimize the risk of collision. In the case that all the pilot identifiers in the specified list conflict with group one or group two, the access point 402 can select only the pilot identifiers that conflict with group two (in the case where the pilot identifier exists). In some embodiments, the access point 402 is not allowed to select pilot identifiers from group one. In the case that there are multiple pilot identifiers to be selected, the access point 402 may select one of the pilot identifiers randomly or in some other designated manner.

As represented by block 308, the access point 402 is then configured to use the selected pilot identifier for wireless communication. For example, the transmitter 410 may use the selected pilot identifier to generate the pilot signal for its broadcast.

As represented by block 310, the access point 402 can continue to monitor the pilot identifier used by its neighbors (for example, using the operation of block 304), so that the access point can continue to ensure that the pilot is being used. The frequency identifier does not conflict with the pilot identifier used by neighbors. For example, the conflict can be caused by a new access point that has recently been installed in the vicinity of the access point 402 or a mobile access point that has entered the vicinity of the access point 402. Moreover, if two access points that are not within the listening range of each other select the same pilot identifier, a pilot identifier conflict (for example, collision) may occur. This conflict can ultimately be detected, for example, by access terminals receiving signals from two access points. In this situation, one or two access points can be configured to change their pilot identifiers. As described below in conjunction 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 can be connected to one of these access points to transmit this information, or an access terminal can be connected to another access point to send this information to the relevant access point point.

In the case of identification conflicts, the access point 402 may perform operations similar to those described above to select a new pilot identifier that does not conflict with any pilot identifier used by any neighboring access point. Therefore, by using these techniques, the access point 402 can independently recover pilot identifier collisions (e.g., pilot identifier collisions). For example, after receiving the conflict notification or identifying the conflict, the access point 402 can move its current pilot identifier to the identifier group designated as forbidden (for example, group one discussed above) and repeat The operations described above.

In some cases, when changing its pilot identifier, the access point 402 can cut off all the connections it currently maintains and force the associated access terminal to reconnect. As an optimization, the access point 402 can send a message in advance to notify the access terminal of the new pilot identifier and the time when the access point 402 will switch to use the new pilot identifier. In this way, the switch to the new pilot identifier can be achieved with minimal service interruption.

Referring now to FIGS. 5 and 6, an access point can discover its neighbors through neighbor discovery initiated by the access point and/or neighbor discovery assisted by the access terminal. Figure 5 shows an example of neighbor discovery at the beginning of an access point. Figure 6 shows an example of neighbor discovery assisted by the access terminal.

In FIG. 5, access point A can initiate neighbor discovery after knowing the existence of neighboring access point B. For example, as discussed above, access point A can listen to the broadcast information of its RF neighbors (for example, by using a downlink receiver) or obtain information about its neighbors in some other way. As represented by block 502 in FIG. 5, access point A can therefore know the identifier (eg, address) of one of its neighbors.

Access point A (for example, through the operation of the neighbor discovery controller component) can directly connect to the neighbor on the backhaul and perform the exchange of neighbor discovery messages. 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 operation of the 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 may include information about its neighbors (e.g., access point C). For example, the information about the access point C may include sufficient information (for example, identifier, address, etc.) to enable another node to access the access point C. Here, it should be understood that the access point C can be a second hop (or higher hop) adjacent to the access point A (for example, the access point A cannot listen to the access point C). In some embodiments, access point B can automatically include information about its neighbors in its report. Alternatively, access point A can specifically request access point B to include this information in the report.

Access point A can therefore use any information about any multi-hop neighbors it receives from the first-hop neighbor (e.g., access point B) to communicate with the multi-hop neighbors. For example, as indicated in FIG. 5, access point A sends a neighbor discovery request to access point C and receives a neighbor discovery report in response. Similarly, the access point C sends the neighbor discovery report to the access point A and receives the neighbor discovery report in response. In a similar manner as discussed above, the neighbor discovery report from access point C may include information about neighbors of access point C (not shown in FIG. 5). In this way, access point A can obtain information about its third-hop neighbors.

In FIG. 6, access point A knows information about its neighbors through neighbor discovery assisted by the access terminal. Here, the access terminal sends a pilot report indicating all pilots (for example, pilot ID2 and other pilot IDs) that the access terminal is receiving to its servo access point (access point A). In the case that 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 (for example, IP address) of the new access point. For example, the access point A may send a sector ID request or other appropriate request (for example, including the pilot ID of the new access point) to the access terminal. The access terminal can then send a sector response including the corresponding sector ID (or the access terminal sends some other appropriate response) to the access point A.

Access point A can then perform a neighbor discovery exchange with the new access point (e.g., access point B). As discussed above in conjunction with FIG. 5, the access point A can receive information about the neighbor of the second hop (for example, access point C) from the access point B, and then perform the communication with the neighbor of the second hop Neighbors find the exchange.

Now referring to Figures 7-9, generally speaking, the teachings in this article can be applied to the configuration of the access point. For example, the techniques described above and other techniques described in this article can be used to determine various configuration parameters of the access point. Examples of such configuration parameters include (but are not limited to) frequency band, carrier frequency, pilot identifier, maximum transmission power, and transmission power data file.

As represented by the block 702 in FIG. 7, the access point 802 (for example, the neighbor discovery controller 846) may determine the identification code of its neighbor as appropriate. For example, in a similar manner as discussed above, the access point 802 may receive its neighbor list from a configuration server (e.g., network node 804). Here, the industry can provide one or more centralized configuration servers in its network to assist in the configuration of access points in the network. Once the access point 802 has been initialized, it can start the configuration process.

In some aspects, the initialization of the access point 802 involves the access point 802 gaining connectivity with the operator's network. Here, it may be necessary to authenticate the access point 802 before allowing the access point 802 to access the operator's network.

In addition, the access point 802 can locate the configuration server. For example, the access point 802 can be pre-configured by using a well-known address (for example, an IP address) of the configuration server. Alternatively, the access point 802 can be aware of the operator of the network connected to it (for example, operator.com), so that the access point 802 can perform a DNS query for FQDN "config_server.operator.com" and receive an IP address in return . In other embodiments, the access point 802 may use some other technology to obtain the appropriate address information. The access point 802 can then establish communication with the configuration server. For example, standardized SNMP or other configuration protocols (such as NetConf, OMA DM, CWMP (TR 069), or DOCSIS) can be used or communication can be established by using a dedicated CLI over SSH (CLI over SSH).

As discussed above, the configuration server can provide the neighbor list to the access point based on the location information received by the configuration server from the access point. These operations will be described in more detail with reference to the flowchart of FIG. 9 and the nodes 802 and 804 of FIG. 8.

As represented by the block 902 in FIG. 9, after the access point 802 is initialized, the location determiner 844 can determine the location of the access point 802. The position determiner 844 can determine the position in various ways. For example, the location can be determined by using global positioning system ("GPS") technology, assisted GPS technology, network-based location determination methods, RF-based methods, or some other appropriate method.

As represented by the block 904, the access point 802 sends its location-related information (for example, an estimate of its location) to the network node 804. In some embodiments, this operation can be initiated by the access point 802 (for example, once the access point 802 is connected to the configuration server). In some embodiments, the configuration server may explicitly request this location information as part of its connection establishment protocol (for example, via request). The access point 802 can also send to the network node 804 other information (eg, power data file, node type) that can be used by the network node 804 to provide an appropriate response.

As represented by block 906, once the network node 804 (for example, the neighbor determiner 840) receives the location information from the access point 802, the network node 804 recognizes the neighbors of the access point 802 and generates a correlation. Neighbor list. This neighbor list may include, for example, any giant access points relatively close to the access point 802, and any other access points in the geographic vicinity of the access point 802 (e.g., ultra-micro nodes, etc.) ).

The neighbor list can be based on the power category (or power data file) of the access point 802 and its neighbors. For example, a far mega access point that transmits at high power may be a neighbor of the access point 802. In contrast, a low-power access point relatively close to the access point 802 (for example, a nano node) may not be included in the neighbor list when the low-power access point and the coverage area of the access point 802 do not intersect. . Therefore, in some situations, the access point 802 may send the power class information together with the location information to the network node 804. In addition, the network node 804 can obtain power-related information from other access points in the network. As represented by block 908, once the neighbor list has been generated, the network node 804 sends the neighbor list to the access point 802.

Referring again to FIG. 7, as represented by block 704, the access point 802 (e.g., configuration controller 832) determines the configuration of its neighbors. As discussed above, the access point 802 can obtain configuration information of its neighbors in various ways. For example, the access point 802 can directly connect with the neighbor via the backhaul and thereby read the selected parameter set. The access point 802 can listen in the air to discover one or more parameters of the neighboring access point (e.g., the pilot identifier as discussed above). The access point 802 can be discovered by neighbors assisted by the access terminal, whereby the access terminal associated with the access point 802 can send configuration information to the access point 802. For example, the access terminal 818 (e.g., the configuration controller 836) can notify the access point 802 of the neighbor access point that the access terminal 818 has listened to. Further, the access point 802 may be freely discussed herein the configuration server (such as network node 804 (e.g., configuration control 834)) adjacent to the received configuration information of the node. It should be understood that the access point 102 can obtain configuration information by using one or more of the technologies described herein or by using other technologies.

As represented by the block 706, the access point 802 (for example, the configuration determiner 848) can specify the configuration of the access point 802 based on the configuration information obtained at the block 704. In some aspects, the access point 802 can autonomously select its own set of parameters (e.g., RF parameters) based on the parameters of its neighbors (e.g., RF parameters).

In some cases, the access point 802 may select its power data file based on the power data file of its neighbors. For example, the access point 802 can select the same power data file used by its neighbors. Alternatively, the access point 802 can select a power data file that is complementary to the power data file used by its neighbors. The power data file can define, for example, the maximum transmission power, different transmission powers for different conditions, or other power parameters.

As discussed above, in some cases, the access point 802 may select a pilot identifier (e.g., pilotPN) based on the pilot identifier used by its neighbors. For example, the access point 802 can select a pilot identifier that is different from its neighbors.

In some cases, the access point 802 may select a carrier (e.g., RF band) based on the carrier used by its neighbors. For example, neighboring nodes in the network can select complementary carrier priority sets (e.g., as indicated by a carrier mask or some other appropriate indication) in order to implement interference management solutions. Here, each access point can radiate more energy on some carriers and less energy on other carriers (for example, or no energy at all). If adjacent access points select these carrier priorities in a complementary manner, it can be ensured that the access terminals associated with each access point can have a more favorable interference environment (at least on some carriers). In order to achieve this situation in an autonomous manner, a new access point (for example, an access point that has been initialized recently) can determine the priority of the carriers used by its neighbors, and choose its own priority with those carriers Complementary carrier priority as much as possible.

In some aspects, the configuration of the access point 802 may depend on its location. For example, the configuration server (e.g., configuration controller 834) can specify a list of parameters (e.g., a subset) (e.g., allowable parameter range) that can be used by the access point. As discussed above in connection with FIG. 3, the designated list may be based on the location of the access point 802. For example, a list of specific power data files that can be used by the access point 802 can be specified based on the location of the access point 802. Similarly, a list of specific frequency bands that can be used by the access point 802 can be specified based on the location of the access point 802. Under a wide range of levels, the city, state, or country where the access point 802 currently resides can restrict which frequency band the access point 802 can use. For example, the same company can have different frequency bands in different countries, or the same company can designate different frequency bands for use in different cities.

In some embodiments, the configuration information may include certain optimization parameters (for example, non-radio parameters). Such parameters may include, for example, a security key that can be used to enable access to one or more services (e.g., network connectivity). These parameters may also include the addresses of other nodes that the access point 802 may need to connect to.

As represented by the block 708 of FIG. 7, the access point 802 can then use the configuration specified in the block 706 for communication or other operations. For example, as discussed above, the determined RF parameters can be used to configure the transceiver 806 to determine which pilot identifier will be advertised, which carriers will be operated and the transmission power level to be used on these carriers.

As represented by the block 710, the access point 802 can continue to monitor the configuration of its neighbors to detect conflicts (e.g., collisions). As mentioned above, in the event of a conflict, the access point 802 can perform the configuration operations described above to resolve the conflict.

In some embodiments, the access point 802 may receive an indication of the conflict from an access terminal (e.g., the access terminal 818). For example, if the access terminal 818 detects a conflict (for example, the conflict detector 838 detects two access points using the same pilot identifier), the access terminal 818 may send a corresponding message To access point 802. Based on this information, the configuration controller 832 can perform operations as discussed above to select different configurations of the access point 802.

It should be understood that the operations and components described above in conjunction with FIG. 7 to FIG. 9 are applicable to the configuration schemes described with reference to other figures in this text. For example, these operations and components can be used in conjunction with configuring the pilot identifier of the access point (for example, as described above in conjunction with FIGS. 3 to 6).

Referring now to FIGS. 10 and 11, in some embodiments, the access point can obtain configuration information from another node (for example, a configuration server), whereby the configuration information depends on the location of the access point. For convenience, the operations of FIGS. 10 and 11 will be described in the context of the access point 802 and the network node 804 of FIG. 8.

As represented by blocks 1002 and 1004 in FIG. 10, the access point 802 (for example, the location determiner 844) determines its location and provides this information to the network node 804. This operation can therefore be similar to the position determination operation described above (for example, at blocks 902 and 904).

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

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

Now referring to Figure 11, in some cases, the configuration server can choose to redirect the access point to a different configuration server. This determination can be made, for example, based on the location of the access point and/or the load on the configuration server.

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

As represented by block 1104, the network node 804 (e.g., configuration server selector 842) can determine whether to provide requested configuration information. For example, the network node 804 may determine based on the location of the access point 802 that another configuration server (for example, it is closer to the access point 802) should handle the request. Furthermore, the network node 804 may elect to reboot the request based on the load at the network node 804. For example, if the network node 804 is heavily loaded, the network node 804 can redirect the request to another configuration server that is not heavily loaded.

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

As represented by block 1110, if the network node 804 determines that it will not handle the request (for example, based on its load or the proximity of the access point 802), then the network node 804 (for example, the configuration server selector 842 ) Identify another configuration server that can provide configuration information to the access point 802. To this end, the network node 804 can maintain a database that includes information about other configuration servers on the network. Additionally or alternatively, the network node 804 may be configured, discover, or communicate with another node to obtain this information.

As represented by block 1112, the network node 804 sends instructions from other configuration servers to the access point 802 (for example, in the form of a reboot message). In some embodiments, the indication may include information that will enable the access point 802 to determine the addresses of other configuration servers. For example, the indication may include the location of the configuration server (e.g., city). After receiving this information, the access point 802 can determine the addresses of other configuration servers (for example, via DNS query).

In some embodiments, the indication may include the address of another configuration server. In some embodiments, the reboot can be achieved by a configuration server that sets a parameter indicating the address of a different configuration server. After determining that there is a subsequent change in this parameter, the access point 802 will attempt to establish a connection with the new configuration server.

As represented by block 1114, the access point 802 can therefore send messages to other configuration servers to obtain configuration information. Once the access point 802 completes its configuration exchange with the configuration server, the access point 802 can start user communication operations.

As mentioned above, the teachings herein can be implemented in networks that use giant access points, ultra-micro nodes, relay nodes, and so on. Figures 12 and 13 illustrate examples of how access points can be deployed in the network. FIG. 12 illustrates in a simplified manner how a cell 1202 (e.g., macro cell 1202A-1202G) of the wireless communication system 1200 can be served by a corresponding access point 1204 (e.g., access point 1204A-1204G). Here, the mega cell 1202 may correspond to the mega coverage area 204 in FIG. 2. As shown in FIG. 12, the access terminals 1206 (for example, the access terminals 1206A-1206L) can be scattered at various locations in the entire system over time. Each access terminal 1206 can communicate with one or more access points 1204 on the forward link ("FL") and/or reverse link ("RL") at a given moment, depending on (for example, ) It depends on whether the access terminal 1206 is active and whether it is in soft handover. By using this cellular solution, the wireless communication system 1200 can provide services in a large geographic area. For example, each of the megacells 1202A-1202G can cover a few blocks in a neighborhood or a few square miles in a rural environment.

Figure 13 illustrates an example of how one or more ultra-micro nodes can be deployed in a network environment (e.g., system 1200). In the system 1300 of FIG. 13, multiple ultra-micro nodes 1310 (e.g., ultra-micro nodes 1310A and 1310B) are installed in a relatively small area coverage network environment (e.g., in one or more user residences 1330). Each ultra-micro node 1310 can be coupled to a wide area network 1340 (for example, the Internet) and a mobile operator core network 1350 ( For example, including network nodes as discussed in this article).

The owner of the ultra-micro node 1310 can subscribe to mobile services, such as 3G mobile services provided via the mobile operator's core network 1350. In addition, the access terminal 1320 may be able to operate in a giant environment and in a small area coverage (for example, residential) network environment. In other words, depending on the current location of the access terminal 1320, the access terminal 1320 can be served by the mega cell access point 1360 associated with the mobile operators core network 1350 or aggregated by the ultra micro node 1310 (e.g., residing in Servo corresponding to any one of the ultra-micro nodes 1310A and 1310B) in the user residence 1330. For example, when the user is outside his home, the user can be served by a standard giant access point (e.g., access point 1360), and when the user is near or inside his home, the user can be served by a super micro node (e.g., node 1310A). ) Servo. Here, the ultra-micro node 1310 can be retrospectively compatible with the traditional access terminal 1320.

The ultra-micro node 1310 can be deployed on a single frequency or in the alternative on multiple frequencies. Depending on the specific configuration, a single frequency or one or more of the multiple frequencies may overlap with one or more frequencies used by the mega access point (e.g., access point 1360).

In some aspects, the access terminal 1320 can be configured to connect to a preferred ultra-micro node (for example, the native ultra-micro node of the access terminal 1320), as long as the connectivity is possible. For example, as long as the access terminal 1320A is in the user's residence 1330, the access terminal 1320A only needs to communicate with the native ultra-micro node 1310A or 1310B.

In some aspects, if the access terminal 1320 operates in the giant cellular network 1350, but does not reside on its best network (for example, as defined in the better roaming list), then the access terminal The machine 1320 can continue to use the best system reselection ("BSR") to search for the best network (e.g., the best ultra-micro node 1310). The BSR can involve periodically scanning available systems to determine whether the best system is currently available, And then worked hard to be associated with these better systems. With the acquisition entry, the access terminal 1320 can restrict the search for specific frequency bands and channels. For example, the search for the best system can be repeated periodically. After finding a better ultra-micro node 1310, the access terminal 1320 selects the ultra-micro node 1310 for camping in its coverage area.

In some aspects, ultra-micro nodes may be restricted. For example, a given ultra-micro node may only provide certain services to certain access terminals. In deployments with so-called restricted (or closed) associations, a given access terminal can only be operated by a mega-cell mobile network and defined ultra-micro nodes (e.g., ultra-micro nodes residing in the corresponding user residence 1330). Node 1310) aggregate servo. In some embodiments, nodes may be restricted to not provide at least one node with at least one of the following: signaling, data access, registration, paging, or service.

In some aspects, a restricted ultra-micro node (which may also be referred to as a closed user group home NodeB) is a node that provides services to a set of restricted access terminals. This collection can be temporarily or permanently expanded when necessary. In some aspects, a closed user group ("CSG") can be defined as a collection of access points (e.g., ultra-micro nodes) that share a common access control list of access terminals. The channel on which all the ultra-micro nodes (or all the restricted ultra-micro nodes) in an area operate can be called the ultra-micro channel.

Therefore, there are various relationships between a given ultra-micro node and a given access terminal. For example, from the point of view of access terminals, an open micro node may refer to a micro node with no restricted association (for example, a micro node allows access to any access terminal). A restricted nano node may refer to a nano node that is restricted in some way (for example, restricted for association and/or registration). The native ultra-micro node may refer to the ultra-micro node where the access terminal is authorized to access and operate (for example, provide permanent access to a defined set of one or more access terminals). The object ultra-micro node may refer to the ultra-micro node where the access terminal is temporarily authorized to access or operate. A foreign micro node may refer to a micro node where the access terminal is unauthorized to access or operate (except for possible emergency situations (for example, a 911 call)).

From the viewpoint of restricted ultra-micro nodes, the home access terminal may refer to an access terminal authorized to access the restricted ultra-micro node (for example, the access terminal can permanently access the ultra-micro node). An object access terminal may refer to an access terminal that can temporarily access restricted ultra-micro nodes (for example, restricted based on expiration, usage time, bytes, connection count, or some other criteria). External access terminals can refer to access terminals that do not have permission to access restricted ultra-micro nodes (except for possible emergencies (for example, 911 calls)) (for example, do not have the certificate to register with restricted ultra-micro nodes) Or allowed access terminal).

For convenience, the disclosure in this article describes various functionalities in the context of ultra-micro nodes. However, it should be understood that micro nodes or relay nodes may provide the same or similar functionality to different (e.g., larger) coverage areas. For example, mini-nodes or relay nodes can be restricted, and native mini-nodes or native relay nodes can be defined for a given access terminal.

The teachings in this article can be implemented in various types of communication devices. In some aspects, the teachings herein can be implemented in a wireless device, and the wireless device can be deployed in a multiple access communication system that can simultaneously support communication for multiple wireless access terminals. Here, each terminal can communicate with one or more access points via transmissions on the forward link and the reverse link. The forward link (also called the downlink) refers to the communication link from the access point to the terminal, and the reverse link (also called the uplink) refers to the terminal to the access point The communication link. This communication link can be established via a single-input single-output system, a multiple-input multiple-output ("MIMO") system, or some other type of system.

For illustrative purposes, Figure 14 depicts sample communication components that can be used in wireless devices in the context of a MIMO-based system 800. System 1400 will be more than (N_T) Transmission antenna and multiple (N_R) The receiving antenna is used for data transmission. Can be changed by N_TTransmission antennas and N_RThe MIMO channel formed by two receiving antennas is decomposed into N_SIndependent channels, which are also called spatial channels, where<img file="TW200939803A_D0001.tif" />N_R}. N_SEach of the independent channels corresponds to a size. If the additional dimensions created by multiple transmit and receive antennas are utilized, the MIMO system can provide improved performance (e.g., higher throughput and/or greater reliability).

The system 1400 can support time division duplex ("TDD") and frequency division duplex ("FDD"). In a TDD system, the forward and reverse link transmissions are on the same frequency region, so that the principle of reciprocity allows the forward link channel to be estimated from the reverse link channel. This enables the access point to capture transmission beamforming gain on the forward link when multiple antennas are available at the access point.

The system 1400 includes a wireless device 1410 (for example, an access point) and a wireless device 1450 (for example, an access terminal). At the device 1410, the traffic data of many data streams are provided from the data source 1412 to the transmission ("TX") data processor 1414.

In some aspects, each data stream is transmitted on a separate transmission antenna. The TX data processor 1414 formats, encodes, and interleaves the traffic data of each data stream based on a specific encoding scheme selected for each data stream to provide encoded data.

The coded data and pilot data of each data stream can be multiplexed using OFDM technology. The pilot data is usually a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. Then based on the specific modulation scheme selected for each data stream (for example, BPSK, QSPK, M-PSK, or M-QAM) to modulate (that is, symbol mapping) the multiplexed pilot and channel of that data stream. Encode data to provide modulation symbols. The data rate, coding, and modulation of each data stream can be determined by the instructions executed by the processor 1430. The data memory 1432 can store program codes, data, and other information used by the processor 1430 or other components of the device 1410.

The modulation symbols of all data streams are then provided to the TX MIMO processor 1420, which can further process the modulation symbols (for example, for OFDM). The TX MIMO processor 1420 then transfers N_TModulation symbol streams are provided to N_TTransceivers ("XCVR") 1422A to 1422T. In some aspects, the TX MIMO processor 1420 applies beamforming weights to the symbols of the data stream and to the antenna from which the symbol is being transmitted.

Each transceiver 1422 receives and processes a respective symbol stream to provide one or more analog signals, and further adjusts (e.g., amplifies, filters, and up-converts) the analog signals to provide a modulated signal suitable for transmission on the MIMO channel Signal. Then separately from N_TAntennas 1424A to 1424T transmit N from transceivers 1422A to 1422T_TA modulated signal.

At device 1450, by N_RThere are two antennas 1452A to 1452R to receive the transmitted modulated signal, and to provide the received signal from each antenna 1452 to respective transceivers ("XCVR") 1454A to 1454R. Each transceiver 1454 adjusts (eg, filters, amplifies, and down-converts) a respective received signal, digitizes the adjusted signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

The receive ("RX") data processor 1460 then receives and processes data from N_RTransceiver 1454 of N_RReceived symbol streams to provide N_TA stream of "detected" symbols. The RX data processor 1460 then demodulates, deinterleaves and decodes each detected symbol stream to recover the traffic data of the data stream. The processing performed by the RX data processor 1460 is complementary to the processing performed by the TX MIMO processor 1420 and the TX data processor 1414 at the device 1410.

The processor 1470 periodically determines which precoding matrix to use (discussed below). The processor 1470 formulates the reverse link message including the matrix index part and the matrix sequence value part. The data memory 1472 can store program codes, data, and other information used by the processor 1470 or other components of the device 1450.

The reverse link message may 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 for many data streams from the data source 1436), modulated by the modulator 1480, adjusted by the transceivers 1454A to 1454R, and transmitted back to The device 1410.

At device 1410, the modulated signal from device 1450 is received by antenna 1424, adjusted by transceiver 1422, demodulated by demodulator ("DEMOD") 1440, and processed by RX data processor 1442 to capture The reverse link message transmitted by the device 1450. The processor 1430 then determines which precoding matrix will be used to determine the beamforming weight, and then processes the retrieved information.

FIG. 14 also illustrates that the communication components may include one or more components that perform configuration ("CONFIG.") control operations as taught herein. For example, the configuration control component 1490 may cooperate with the processor 1430 of the device 1410 and/or other components to send signals to/from another device (eg, device 1450)/receive signals from another device (eg, device 1450) , As taught in this article. Similarly, the configuration control component 1492 can cooperate with the processor 1470 of the device 1450 and/or other components to send signals to/receive signals from another device (eg, device 1410). It should be understood that for each device 1410 and 1450, a single component can provide the functionality of two or more of the described components. For example, a single processing component can provide the functionality of the configuration control component 1490 and the processor 1430, and a single processing component can provide the functionality of the configuration control component 1492 and the processor 1470.

The teachings herein can be incorporated into various types of communication systems and/or system components. In some aspects, the teachings in this article can be used to support multiple users by sharing available system resources (for example, by specifying one or more of bandwidth, transmission power, encoding, interleaving, etc.) The communication of multiple access systems. For example, the teachings in this article can be applied to any one or a combination of the following technologies: code division multiple access ("CDMA") system, multi-carrier CDMA ("MCCDMA"), broadband 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 ("SC-FDMA") ") system, Orthogonal Frequency Division Multiple Access ("OFDMA") system, or other multiple access technology. Wireless communication systems using the teachings herein can be designed to implement one or more standards, such as 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 Rate ("LCR"). cdma2000 technology covers IS-2000, IS-95 and IS-856 standards. TDMA networks can implement radio technologies such as the Global System for Mobile Communications ("GSM"). OFDMA network can implement such as evolved UTRA ("E-UTRA"), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM<img file="TW200939803A_D0002.tif" />And so on radio technology. UTRA, E-UTRA and GSM are part of the Global Mobile Telecommunications 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 version of UMTS that uses E-UTRA. Although 3GPP terminology can be used to describe certain aspects of the present disclosure, it should be understood that the teachings herein can be applied to 3GPP (Re199, Re15, Re16, Re17) technologies, and 3GPP2 (IxRTT, 1xEV-DO RelO, RevA) , RevB) technology and other technologies.

The teachings herein may be incorporated into a variety of devices (e.g., nodes) (e.g., implemented in or executed by multiple devices (e.g., nodes)). In some aspects, nodes implemented in accordance with the teachings herein (eg, wireless nodes) include access points or access terminals.

For example, the access terminal may include, be implemented as, or be referred to as user equipment, user station, user unit, mobile station, mobile body, mobile node, remote station, remote terminal, user terminal , User agent, user device, or some other term. In some embodiments, the access terminal may include a cellular phone, a wireless phone, a session initiation protocol ("SIP") phone, a wireless area loop ("WLL") station, a personal digital assistant ("PDA"), A handheld device with wireless connection capability, or some other appropriate processing device connected to a wireless modem. Therefore, one or more aspects taught herein can be incorporated into phones (e.g., cellular phones or smart phones), computers (e.g., laptops), portable communication devices, portable computing devices (e.g., , Personal data assistants), entertainment devices (for example, music devices, video devices, or satellite radios), global positioning system devices, or any other suitable devices configured to communicate via wireless media.

An access point may include, be implemented as, or be referred to as NodeB, eNodeB, Radio Network Controller ("RNC"), Base Station ("BS"), Radio Base Station ("RBS"), Base Station Controller ( "BSC"), base transceiver station ("BTS"), transceiver function ("TF"), radio transceiver, radio router, basic service set ("BSS"), extended service set ("ESS") or Some other similar term.

In some aspects, nodes (e.g., access points) may include access nodes for communication systems. The access node may, for example, provide connectivity to the network or provide connectivity to the network via a wired or wireless communication link to a network (e.g., a wide area network (such as the Internet)). Therefore, an access node can enable another node (e.g., an access terminal) to access the network or some other functionality. In addition, it should be understood that one or both of the nodes may be portable, or in some cases, relatively non-portable.

Also, it should be understood that wireless nodes may be able to transmit and/or receive information in a non-wireless manner (for example, via a wired connection). Therefore, receivers and transmitters as discussed herein may include appropriate communication interface components (e.g., electrical or optical interface components) to communicate via non-wireless media.

A wireless node may communicate via one or more wireless communication links based on or otherwise supporting any suitable wireless communication technology. For example, in some aspects, wireless nodes may be associated with the network. In some aspects, the network may include a local area network or a wide area network. The wireless device may support or otherwise use one or more of a variety of wireless communication technologies, protocols, or standards, such as those discussed herein (eg, CDMA, TDMA, OFDM, OFDMA, WiMAX, Wi-Fi, etc.) . Similarly, the wireless node may support or otherwise use one or more of a variety of corresponding modulation or multiplexing schemes. The wireless node may therefore include appropriate components (e.g., air interface) to use the above or other wireless communication technologies to establish one or more wireless communication links and communicate via the one or more wireless communication links. For example, a wireless node may include a wireless transceiver with associated transmitter and receiver components, which may include various components (e.g., signal generators and signal processors) that facilitate communication over wireless media.

The components described herein can be implemented in a variety of ways. 15-22, the devices 1500, 1600, 1700, 1800, 1900, 2000, 2100, and 2200 are represented as a series of related functional blocks. In some aspects, the functionality of these blocks can be implemented as a processing system that includes one or more processor components. In some aspects, at least a portion of one or more integrated circuits (e.g., ASIC) may be used, for example, to implement the functionality of these blocks. As discussed herein, an integrated circuit may include a processor, software, other related components, or some combination thereof. The functionality of these blocks can also be implemented in some other way as taught herein. In some aspects, one or more of the dashed blocks in FIGS. 15-22 are optional.

The devices 1500, 1600, 1700, 1800, 1900, 2000, 2100, and 2200 may include one or more modules that can perform one or more of the functions described above with respect to the various figures. For example, the identifier determination component 1502 or the conflict identification component 1516 may correspond to, for example, an identifier determiner as discussed herein. The identifier selection member 1504 may correspond to, for example, an identifier selector as discussed herein. The type transmission component 1506 or the position transmission component 1510 may correspond to, for example, a transmitter as discussed herein. The manifest receiving component 1508 may correspond to, for example, a receiver as discussed herein. The neighbor receiving, generating, and sending component 1512 and the access point identifying component 1514 may correspond to, for example, a neighbor discovery controller as discussed herein. The identifier list determination component 1602 may correspond to, for example, a configuration controller as discussed herein. The manifest sending component 1604 may correspond to, for example, a transmitter as discussed herein. The receiving member 1606 may correspond to, for example, a receiver as discussed herein. The neighbor determination and transmission component 1608 may correspond to, for example, a neighbor determiner as discussed herein. The access point identification component 1702 may correspond to, for example, a neighbor discovery controller as discussed herein. The configuration determination component 1704 may correspond to, for example, a configuration determiner as discussed herein. The configuration specifying member 1706 may correspond to, for example, a configuration controller as discussed herein. The conflict identification component 1708 may correspond to, for example, a configuration determiner as discussed herein. The sending member 1710 may correspond to, for example, a transmitter as discussed herein. The receiving member 1712 may correspond to, for example, a receiver as discussed herein. The receiving member 1802 may correspond to, for example, a receiver as discussed herein. The access point determination component 1804 may correspond to, for example, a neighbor determiner as discussed herein. The sending member 1806 may correspond to, for example, a transmitter as discussed herein. The configuration determination component 1808 may correspond to, for example, a configuration controller as discussed herein. The location information sending component 1902 may correspond to, for example, a location determiner as discussed herein. The configuration information receiving component 1904 may correspond to, for example, a configuration controller as discussed herein. The server positioning member 1906 may correspond to, for example, a communication controller as discussed herein. The location information receiving component 2002 may correspond to, for example, a receiver as discussed herein. Configuration resources The information determination component 2004 may correspond to, for example, a configuration controller as discussed herein. The configuration information sending component 2006 may correspond to, for example, a transmitter as discussed herein. The message sending member 2102 may correspond to, for example, a transmitter as discussed herein. The configuration server indicates that the receiving component 2104 may correspond to, for example, a receiver as discussed herein. The address determination component 2106 may correspond to, for example, a communication controller as discussed herein. The request receiving component 2202 may correspond to, for example, a receiver as discussed herein. The configuration server identification component 2204 may correspond to, for example, the configuration server selector as discussed herein. The indication sending member 2206 may correspond to, for example, a transmitter as discussed herein.

It should be understood that the use of names such as "first", "second", etc. herein and any reference to elements generally does not limit the quantity or order of these elements. More precisely, these nomenclature can be used herein as a convenient way to distinguish two or more elements or examples of an element. Therefore, the reference to the first and second elements does not mean that only two elements can be used there or that the first element must precede the second element in some way. Also, unless otherwise stated, a set of elements may include one or more elements. In addition, the terms of the form "at least one of the following: A, B, or C" used in description or application for patents means "A or B or C or any combination of these elements".

Those familiar with this technology should understand that any of a variety of different technologies can be used to represent information and signals. For example, voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof can be used to represent data, instructions, commands, information, signals, bits, Symbols and chips.

Those familiar with this technology should further understand that any of the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed in this article can be implemented as electronic Hardware (for example, a digital embodiment, an analog embodiment, or a combination of the two, which can be designed using source code or some other technology), and various forms of programs or design codes with instructions (for convenience, its It can be referred to as "software" or "software module") or a combination of the two in this article. In order to clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether the functionality is implemented as hardware or software depends on the specific application and design constraints imposed on the entire system. Those skilled in the art can implement the described functionality in various ways for each specific application, but these embodiment decisions should not be construed as causing a departure from the scope of this disclosure.

The various descriptive logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented in or executed by: integrated circuits ("IC"), access terminals, or Access point. The IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic designed to perform the functions described in this article Devices, discrete gates or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof, and can execute program codes or instructions residing in the IC, outside the IC, or both. The general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with DSP cores, or any other such configuration.

It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the process can be rearranged while remaining within the scope of this disclosure. The accompanying method items present the elements of the various steps in a sample order, and are not intended to be limited to the specific order or hierarchy presented.

The described functions can be implemented by hardware, software, firmware, or any combination thereof. If implemented by software, these functions can be stored on a computer-readable medium or transmitted on a computer-readable medium as one or more instructions or program codes. Computer-readable media includes both computer storage media and communication media. Communication media includes any media that facilitates the transfer of computer programs from one location to another. The storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, these computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or may be used to carry or store instructions or data structures Any other media that can be accessed by the computer in the form of the desired code. Also, any connection can be appropriately referred to as a computer-readable medium. For example, if you use coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave to transmit software from a website, server, or other remote source, the coaxial cable, Fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of media. Disks and optical discs as used in this article include compact discs (CD), laser discs, optical discs, digital versatile discs (DVD), floppy disks, and Blu-ray discs. Disks usually reproduce data magnetically, while optical discs usually reproduce data magnetically. The laser optically reproduces the data. The combination of the above should also be included in the category of computer-readable media. In short, it should be understood that computer-readable media can be implemented in any suitable computer program product.

In view of the above, in some aspects, the first communication method includes: sending information indicating the location of the access point from the access point; and receiving configuration information of the access point at the access point, where the configuration information is Information based on the indicated location. In addition, in some aspects, at least one of the following items may also be applied to the first communication method: the configuration information includes at least one RF parameter; the configuration information includes at least one of the following groups : Frequency band, carrier frequency, pilot identifier, maximum transmission power and transmission power data file; the access point sends the information indicating the position to the configuration server, and the access point receives the configuration information from the configuration server; method further It includes receiving a request for information indicating a location from a configuration server, wherein the access point sends information indicating the location in response to the request; the method further includes locating the configuration server; the configuration information includes at least one optimization parameter; wherein The information indicating the location is at least one of the following groups: the city where the access point is located, the country where the access point is located, the giant access point of the server access point, and the access point associated The area, the cell that communicates with the access point, GPS coordinates, geographic location, and street address; the access point includes ultra-micro nodes or relay nodes.

In some aspects, the second communication method includes: receiving information indicating the location of the access point; determining the configuration information of the access point based on the information indicating the location; and sending the configuration information to the access point. In addition, in some aspects, at least one of the following items may also be applied to the second communication method: the configuration information includes at least one RF parameter; the configuration information includes at least one of the following groups : Frequency band, carrier frequency, pilot identifier, maximum transmission power, and transmission power data file; the method further includes sending a request for information indicating the position, wherein the information indicating the position is received in response to the request; the configuration information includes at least one maximum Optimized parameters; at least one of the information indicating the location of the indicated location consists of at least one of the following groups: the city where the access point is located, the country where the access point is located, the giant access point of the servo access point, and the storage Get the area associated with the point, the cell that communicates with the access point, GPS coordinates, geographic location, and street address; the method is executed by the configuration server.

In some aspects, the third communication method includes: sending the first message to the first configuration server to obtain the configuration information of the access point; in response to the first message, receiving the second message from the first configuration server Instructions for configuring the server; and sending the second message to the second configuration server to obtain the configuration information of the access point. In addition, in some aspects, at least one of the following can also be applied to the third communication method: the instruction includes the address of the second configuration server; the method further includes determining the second configuration server based on the instruction The first message contains information indicating the location of the access point, and based on the information indicating the location, an instruction from the second configuration server is received; the information indicating the location indicates at least one of the following groups Those: cities with access points located, countries with access points located, giant access points serving access points, areas associated with access points, communities communicating with access points, and access points are serving The operators network, GPS coordinates, geographic location and street address; configuration information includes at least one RF parameter; configuration information includes at least one of the following groups: frequency band, carrier frequency, pilot identification The configuration information includes at least one optimized parameter; the access point includes a super-micro node or a relay node.

In some aspects, the fourth communication method includes: receiving a request for configuration information of the access point at the first configuration server; identifying the second configuration server that provides configuration information; and responding to the request Send the instructions of the second configuration server. In addition, in some aspects, at least one of the following can also be applied to the fourth communication method: the identification of the second configuration server is based on the load at the first configuration server and/or the second group The load at the state server; the identification of the second configuration server is based on the location of the first configuration server and/or the location of the second configuration server; the request contains information indicating the location of the access point, and the first 2. The identification of the configuration server is based on the information of the indicated location; the information of the indicated location indicates at least one of the following groups: the city where the access point is located, the country where the access point is located, and the server storage The giant access point to take the point, the area associated with the access point, the cell communicating with the access point, the business network where the access point is being served, GPS coordinates, geographic location and street address; instructions include the second The address of the configuration server; the configuration information includes at least one RF parameter; the configuration information includes at least one of the following groups: frequency band, carrier frequency, pilot identifier, maximum transmission power, and transmission power Data file; the configuration information includes at least one optimization parameter.

In some aspects, the fifth communication method includes: identifying at least one neighbor access point of the first access point; determining at least one configuration of the at least one neighbor access point; and at the first access point At least one configuration of the first access point is specified based on at least one configuration of the at least one neighboring access point. In addition, in some aspects, at least one of the following items may also be applied to the fifth communication method: the designation of at least one configuration includes the designation of at least one RF parameter; the designation of at least one configuration includes the designation of the following At least one of the group consisting of: frequency band, carrier frequency, pilot identifier, maximum transmission power, transmission power data file, and carrier priority set; the designation of at least one configuration includes designating the same access as at least one neighbor The power data file of the power data file of a point; the designation of at least one configuration includes the designation of a pilot identifier that is different from any pilot identifier used by at least one neighboring access point; the designation of at least one configuration includes Designating a carrier priority set complementary to another carrier priority set used by at least one neighboring access point; the method further comprises: identifying the determined at least one configuration and the previously specified carrier priority set for the first access point The conflict between the configurations, and the non-conflicting configuration that specifies the first access point in response to the identification of the conflict; the determination of at least one configuration includes at least one of the following groups: The configuration information is received in the air at the fetch point, the configuration information is received from the associated access point at the first access point, the configuration information is received through the backhaul at the first access point, and the configuration information is received from the first access point at the first access point. The server receives configuration information; the determination of at least one configuration includes 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 includes: An access point sends information indicating the location of the first access point and/or the power data file of the first access point, and receives instructions from at least one neighboring access point at the first access point, wherein The instructions are based on the sent information; the first access point sends the information indicating the location to the configuration server, and the first access point receives the instructions from the configuration server; the first access point sends the information indicating the location to at least one Other adjacent access points, and the first access point receives instructions from at least one other adjacent access point; the information indicating the location indicates at least one of the following groups: the first access point is located The city where the point is taken, the country where the first access point is located, the giant access point that serves the first access point, the area associated with the first access point, the cell that communicates with the first access point, the first The access point is serving the business network, GPS coordinates, geographic location, and street address where the access point is located; the first access point includes an ultra-micro node or a relay node.

In some aspects, the sixth communication method includes: receiving information indicating the location of the first access point; determining at least one neighboring access point of the first access point based on the information indicating the location; The instruction of the neighbor's access point is sent to the first access point. In addition, in some aspects, at least one of the following items may also be applied to the sixth communication method: The method further includes receiving information indicating the power data file of the first access point, and at least one of the neighbors accesses The point determination is further based on the information indicating the power data file; the method further includes receiving information indicating at least one power data file of at least one other access point, wherein the determination of at least one neighboring access point is further based on the instruction at least one Information of the power data file; the method further includes: determining at least one configuration of at least one neighboring access point, and sending an indication of the at least one configuration to the first access point; at least one configuration includes at least one RF parameter ; At least one configuration includes at least one of the following groups: frequency band, carrier frequency, pilot identifier, maximum transmission power and transmission power data file; the information indicating the position indicates the group consisting of the following At least one of: the city where the first access point is located, the country where the first access point is located, the giant access point that serves the first access point, the area associated with the first access point, and The community, GPS coordinates, geographic location and street address of the first access point communication; the method is executed by the configuration server.

In some aspects, the functionality corresponding to one or more of the above aspects related to the first, second, third, fourth, fifth, and sixth communication methods can be implemented (for example) for use as herein In the device of the structure taught in. In addition, the computer program product may include a computer configured to provide functionality corresponding to one or more of the above aspects of the first, second, third, fourth, fifth, and sixth communication methods Code.

The previous descriptions of the disclosed aspects are provided to enable those familiar with the art to make or use the present disclosure. Without departing from the scope of this disclosure, various modifications to these aspects will be obvious to those familiar with the art, and the general principles defined in this article can be applied to other aspects. Therefore, this disclosure is not intended to be limited to the aspects shown in this article, but will conform to the broadest scope consistent with the principles and novel features disclosed in this article.

<p>100. . . Communication Systems</p><p>102. . . Access terminal</p><p>104. . . Access point</p><p>106. . . Access point</p><p>108. . . Network node</p><p>110. . . Configuration controller</p><p>112. . . Wireless transceiver</p><p>200. . . network</p><p>202A. . . Tracking area</p><p>202B. . . Tracking area</p><p>202C. . . Tracking area</p><p>204A. . . Huge coverage area</p><p>204B. . . Huge coverage area</p><p>206A. . . Small coverage area/Ultra-micro coverage area</p><p>206B. . . Small coverage area/Ultra-micro coverage area</p><p>206C. . . Small coverage area/Ultra-micro coverage area</p><p>402. . . Access point</p><p>404. . . Network node</p><p>406. . . transceiver</p><p>408. . . transceiver</p><p>410. . . Transmitter</p><p>412. . . receiver</p><p>414. . . Transmitter</p><p>416. . . receiver</p><p>418. . . Configuration controller</p><p>420. . . Position determiner</p><p>422. . . Pilot Identifier Decider</p><p>424. . . Neighbor discovers the controller</p><p>426. . . Neighbor Determinator</p><p>428. . . Pilot identifier selector</p><p>800. . . MIMO-based system</p><p>802. . . Access point</p><p>804. . . Network node</p><p>806. . . transceiver</p><p>808. . . Transmitter</p><p>810. . . receiver</p><p>812. . . transceiver</p><p>814. . . Transmitter</p><p>816. . . receiver</p><p>818. . . Access terminal</p><p>820. . . transceiver</p><p>822. . . Transmitter</p><p>824. . . receiver</p><p>826. . . Communication controller</p><p>828. . . Communication controller</p><p>830. . . Communication controller</p><p>832. . . Configuration controller</p><p>834. . . Configuration controller</p><p>836. . . Configuration controller</p><p>838. . . Conflict detector</p><p>840. . . Neighbor Determinator</p><p>842. . . Configuration server selector</p><p>844. . . Position determiner</p><p>846. . . Neighbor discovers the controller</p><p>848. . . Configuration determiner</p><p>1200. . . Wireless communication system</p><p>1202A. . . Mega cell</p><p>1202B. . . Mega cell</p><p>1202C. . . Mega cell</p><p>1202D. . . Mega cell</p><p>1202E. . . Mega cell</p><p>1202F. . . Mega cell</p><p>1202G. . . Mega cell</p><p>1204A. . . Access point</p><p>1204B. . . Access point</p><p>1204C. . . Access point</p><p>1204D. . . Access point</p><p>1204E. . . Access point</p><p>1204F. . . Access point</p><p>1204G. . . Access point</p><p>1206A. . . Access terminal</p><p>1206B. . . Access terminal</p><p>1206C. . . Access terminal</p><p>1206D. . . Access terminal</p><p>1206E. . . Access terminal</p><p>1206F. . . Access terminal</p><p>1206G. . . Access terminal</p><p>1206H. . . Access terminal</p><p>1206I. . . Access terminal</p><p>1206J. . . Access terminal</p><p>1206K. . . Access terminal</p><p>1206L. . . Access terminal</p><p>1300. . . system</p><p>1310A. . . Ultra-micro node</p><p>1310B. . . Ultra-micro node</p><p>1320A. . . Access terminal</p><p>1320B. . . Access terminal</p><p>1330. . . User residence</p><p>1340. . . Wide area network</p><p>1350. . . Mobile operator core network</p><p>1360. . . Mega cell access point</p><p>1400. . . system</p><p>1410. . . Wireless device</p><p>1412. . . Data source</p><p>1414. . . Transmission ("TX") data processor</p><p>1420. . . TX MIMO processor</p><p>1422A. . . Transceiver ("XCVR")</p><p>1422T. . . Transceiver ("XCVR")</p><p>1424A. . . antenna</p><p>1424T. . . antenna</p><p>1430. . . processor</p><p>1432. . . Data memory</p><p>1436. . . Data source</p><p>1438. . . TX data processor</p><p>1440. . . Demodulator ("DEMOD")</p><p>1442. . . RX data processor</p><p>1450. . . Wireless device</p><p>1452A. . . antenna</p><p>1452R. . . antenna</p><p>1454A. . . Transceiver ("XCVR")</p><p>1454R. . . Transceiver ("XCVR")</p><p>1460. . . Receive ("RX") data processor</p><p>1470. . . processor</p><p>1472. . . Data memory</p><p>1480. . . Modulator</p><p>1490. . . Configuration control component</p><p>1492. . . Configuration control component</p><p>1500. . . Device</p><p>1502. . . Identifier determination component</p><p>1504. . . Identifier selection component</p><p>1506. . . Type sending widget</p><p>1508. . . List receiving component</p><p>1510. . . Location sender</p><p>1512. . . Neighbors receive, produce and send components</p><p>1514. . . Access point identification component</p><p>1516. . . Conflict identification component</p><p>1600. . . Device</p><p>1602. . . Identifier List Judgment Component</p><p>1604. . . List sending component</p><p>1606. . . Receiving component</p><p>1608. . . Neighbor Judgment and Sending Component</p><p>1700. . . Device</p><p>1702. . . Access point identification component</p><p>1704. . . Configuration decision component</p><p>1706. . . Configure designated components</p><p>1708. . . Conflict identification component</p><p>1710. . . Send widget</p><p>1712. . . Receiving component</p><p>1800. . . Device</p><p>1802. . . Receiving component</p><p>1804. . . Access point determination component</p><p>1806. . . Send widget</p><p>1808. . . Configuration decision component</p><p>1900. . . Device</p><p>1902. . . Location information sending component</p><p>1904. . . Configuration information receiving component</p><p>1906. . . Server positioning component</p><p>2000. . . Device</p><p>2002. . . Location information receiving component</p><p>2004. . . Configuration information judging component</p><p>2006. . . Configuration information sending component</p><p>2100. . . Device</p><p>2102. . . Message sending component</p><p>2104. . . Configuration server instruction receiving component</p><p>2106. . . Address determination component</p><p>2200. . . Device</p><p>2202. . . Request receiving component</p><p>2204. . . Configuration server identification component</p><p>2206. . . Instruct the sender</p>

Figure 1 is a simplified block diagram of several sample states of a communication system for configuring an access point based on received information;

Figure 2 is a simplified diagram illustrating a sample coverage area for wireless communication;

Figure 3 is a flowchart of several sample states of operations that can be performed to configure the access point;

Figure 4 is a simplified block diagram of several sample configurations of components that can be used in a communication node;

Figure 5 is a simplified diagram illustrating sample operations on neighbor discovery;

Figure 6 is a simplified diagram illustrating sample operations on neighbor discovery;

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

Figure 8 is a simplified block diagram of several sample configurations of components that can be used in a communication node;

Figure 9 is a flowchart of several sample states of operations that can be performed to configure access points based on location;

FIG. 10 is a flowchart of several sample modes of operations that can be executed to configure an access point based on received configuration information;

Figure 11 is a flowchart of several sample states of operations that can be executed to direct the access point to the configuration server;

Figure 12 is a simplified diagram of a wireless communication system;

Figure 13 is a simplified diagram of a wireless communication system including ultra-micro nodes;

Figure 14 is a simplified block diagram of several sample configurations of the communication component; and

Figures 15-22 are simplified block diagrams of several sample configurations of a device configured to perform the configuration-related operations taught herein.

According to general practice, the various features illustrated by the drawings may not be drawn to scale. Therefore, the size of various features can be arbitrarily enlarged or reduced for clarity. In addition, some diagrams may be simplified for clarity. Therefore, the drawings may not depict all the components of a given apparatus (e.g., device) or method. Finally, the same reference numbers can be used to represent the same features throughout the specification and the figures.