Systems and methods for managing access node neighbor relations

Systems and methods are described for managing access node neighbor relations. An application requirement associated with a wireless device in communication with a first access node may be determined. A neighbor reporting criteria may be calculated based on the determined application requirement. The first access node may then receive an identifier of a second access node from the wireless device. The second identifier may be transmitted from the wireless device in response to a reporting event triggered based on a first signal level of the first access node, a second signal level of the second access node, and the neighbor reporting criteria. It may be determined, based on the second identifier, if a communication link between the first access node and the second access node has been previously established. If not, a communication link between the first access node and second access node may be established.

TECHNICAL BACKGROUND

Telecommunication systems, such as cellular networks or other wireless networks, use various network links throughout the network to communicate. For example, an access node may use a network link to communicate with another access node while using a separate network link to communicate with a controller node. Accordingly, the system may rely on a well-established network to provide efficient communication services.

In certain circumstances, an access node may be unknown to proximate access nodes within the same communication system. For example, a newly established access node may not be known to its neighboring access nodes. A system designed to efficiently update access nodes about their neighboring access node would allow for an enhanced quality of service for the users of the system.

Overview

Systems and methods are described for managing access node neighbor relations. An application requirement associated with a wireless device in communication with a first access node may be determined. A neighbor reporting criteria may be calculated based on the determined application requirement. The first access node may then receive an identifier of a second access node from the wireless device. The second identifier may be transmitted from the wireless device in response to a reporting event triggered based on a first signal level of the first access node, a second signal level of the second access node, and the neighbor reporting criteria. It may be determined, based on the second identifier, if a communication link between the first access node and the second access node has been previously established. If not, a communication link between the first access node and second access node may be established.

DETAILED DESCRIPTION

FIG. 1illustrates an exemplary communication system100to manage an access node neighbor relations comprising wireless device102, access nodes104and106, communication network108, and communication links110,112,114, and116. Other network elements may be present in the communication system100to facilitate communication but are omitted for clarity, such as controller nodes, base stations, base station controllers, gateways, mobile switching centers, dispatch application processors, and location registers such as a home location register or visitor location register. Furthermore, other network elements may be present to facilitate communication between access node104, access node106, and communication network108which are omitted for clarity, including additional processing nodes, routers, gateways, and physical and/or wireless data links for carrying data among the various network elements.

Wireless device102can be any device configured to communicate over communication system100using a wireless communication link. For example, wireless device102can include a cell phone, a smart phone, a computing platform such as a laptop, palmtop, or a tablet, a personal digital assistant, or an internet access device, and combinations thereof. It is noted that while one wireless device is illustrated inFIG. 1as being in communication with each of access nodes104and106, any number of wireless devices can be implemented.

Access nodes104and106are network nodes capable of providing wireless communications to wireless device102, and can be, for example, a base transceiver station, a radio base station, an eNodeB device, or an enhanced eNodeB device. Access nodes104and106may communicate with communication network108over communication links114and116. Access nodes104and106may also communicate directly with each other over communication link118. In an embodiment, access node104can comprise a serving access node for wireless device102.

Although only two access nodes104and106are illustrated inFIG. 1, wireless device102can be in communication with a plurality of access node. The plurality of access nodes can be associated with different networks and can support different communication protocols and radio access technologies.

Communication links110,112,114,116, and118can be wired or wireless communication links. Wired communication links can comprise, for example, twisted pair cable, coaxial cable or fiber optic cable, or combinations thereof. Wireless communication links can comprise a radio frequency, microwave, infrared, or other similar signal, and can use a suitable communication protocol, for example, GSM, CDMA, UMTS, HSPA, EV-DO, or 3GPP LTE, or combinations thereof. Other wireless protocols can also be used.

FIG. 2illustrates an exemplary communication system200for managing access node neighbor relations. System200comprises wireless device202, access nodes204and206, and signal radii208and210. Wireless device202may comprise a device similar to wireless device102ofFIG. 1. Similarly, access nodes204and206may comprise access nodes similar to access node104ofFIG. 1.

A signal radius, or coverage radius, may comprise an area around an access node within which a wireless device can detect a signal transmitted form the access node. Signal radius208can comprise a radius for reference signal, or pilot signal, transmitted from access node204and signal radius210can comprise a radius for a reference signal, or pilot signal, transmitted from access node206.

In operation, wireless device202may establish communication with access node204such that access node204provides the wireless devices access to a communication network (such as communication network108, illustrated inFIG. 1). Access node204may transmit a reference signal, or a pilot signal, over signal radius208to enable wireless device202to detect access node204. When a wireless device, such as wireless device202, detects the reference signal from access node204, and it is determined that the reference signal from access node204meets a threshold signal level, wireless device202may attempt to establish communication with access node204. For example, the signal level may be represented by received signal strength indication (RSSI), reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), or any other suitable metric.

In an embodiment, communication system200may be configured to manage access node neighbor relations. For example, communication system200may implement a self-organizing network (SON) protocol that includes an automatic neighbor relations (ANR) process, or may implement any other suitable protocol for managing access node neighbor relations.

In an embodiment, access node204may not be aware of access node206. For example, access node204may track neighbor access nodes using a neighbor relations table (NRT) that stores information about access node204's neighbors. The NRT may store identifiers for neighbor access nodes (e.g., PCI, CGI, and the like), connection information (e.g., X2 connection information), handover information, and any other suitable neighbor information. In this example, access node204may not comprise an entry in the neighbor relations table for access node206.

In an embodiment, access node206may comprise a new access node. In other words, access node206may have been connected to communication network200recently (e.g., within a threshold time period). In this example, access node204may not be aware of access node206because it is a new access node. Access node204may be configured to discover access node206using, for example, an ANR process.

In an embodiment, access node204may use wireless devices in communication with access node204in order to discover new neighbor access nodes. For example, access node204may communicate with wireless device202in order to discover neighbor access nodes206. Here, access node204may transmit a criteria, such as an ANR criteria, to wireless devices in communication with access node204(e.g., wireless device202). The ANR criteria may comprise a signal level criteria. An ANR event may be triggered at the wireless device based on a comparison of the received ANR criteria, a signal level for a reference signal or pilot signal received from access node204, and a signal level for a reference signal or pilot signal received from access node206. In response to the triggered ANR event, wireless device202may transmit a measurement report comprising a signal level for each reference signal or pilot signal received at the wireless device (e.g., from a plurality of access nodes), and an identifier (e.g., PCI, CGI, and the like) for each access node. In an embodiment, the measurement report may comprise signal levels that are above a criteria (e.g., a determined threshold).

Access node204may receive the measurement report and compare the access node identifiers in the NRT against those in the received measurement report. Here, because access node204is not aware of access node206, the NRT for access node204does not include information about access node206. Accordingly, access node204may commence a process to add access node206as a neighbor (e.g., update the NRT to include information for access node206). In an embodiment, access node204may instruct wireless device202to retrieve a global identifier for access node206and transmit the global identifier to access node204. Using the global identifier, access node204may retrieve an IP address for access node206(e.g., from a controller node such as an MME). A communication link may then be established between access node204and access node206(e.g., an X2 connection). Based on this process, access node204may update the NRT to include information about access node206.

As a result of the ANR process and the update to the NRT for access node204, a handover may be performed between access node204and access node206. However, in certain circumstances the handover from access node204to access node206may fail. For example, similar to the ANR criteria, a handover criteria used to trigger a handover between access node204and access node206may comprise a signal level criteria (e.g., A3 event signal level criteria). If the ANR signal level criteria is too close to the handover signal level criteria, a handover may fail due to lack of sufficient time to complete the ANR process. On the other hand, where the ANR signal level criteria it too far from the handover signal level criteria, ANR may be performed liberally and system resources may be inefficiently used. Accordingly, a system may be configured with an ANR criteria that efficiently uses system resources.

Systems and methods are described for managing access node neighbor relations. An application requirement associated with a wireless device in communication with a first access node may be determined. A neighbor reporting criteria may be calculated based on the determined application requirement. The first access node may then receive an identifier of a second access node from the wireless device. The second identifier may be transmitted from the wireless device in response to a reporting event triggered based on a first signal level of the first access node, a second signal level of the second access node, and the neighbor reporting criteria. It may be determined, based on the second identifier, if a communication link between the first access node and the second access node has been previously established. If not, a communication link between the first access node and second access node may be established.

FIG. 3illustrates an exemplary method for managing access node neighbor relations. The method will be discussed with reference to the exemplary communication system200illustrated inFIG. 2, however, the method can be implemented with any suitable communication system.

Referring toFIG. 3, at step302, an application requirement of a wireless device communicating with a first access node is determined. For example, wireless device202may be in communication with access node204, and an application requirement for the wireless device may be determined. An application requirement, or a quality of service (QoS) requirement, may be one or more service conditions that a wireless device requests from an access node, such as a quality of service class identifier (QCI), a minimum guaranteed bit rate (GBR), maximum bit rate (MBR), a priority, a minimum bit rate, a maximum permitted data delay, a minimum throughput, a maximum error rate, a maximum data loss rate, and any other application requirement. In an embodiment, the determined application requirement may be based on one or more applications running on wireless device202.

At step304, a neighbor reporting criteria is calculated based on the determined application requirement. For example, based on an application requirement determined for wireless device202, a neighbor reporting criteria may be calculated. In an embodiment, the determined application requirement may comprise a minimum data rate, and the reporting criteria may be based on the minimum data rate.

At step306, an identifier of a second access node is received in response to a reporting event triggered at the wireless device based on a first signal level of the first access node, a second signal level of the second access node, and the neighbor reporting criteria. For example, the calculated neighbor reporting criteria may be transmitted form access node204to wireless device202. In addition, wireless device202may receive a reference signal or pilot signal from access node204at a received signal level and a reference signal or pilot signal from access node206at a received signal level. In an embodiment, a reporting event may be triggered at the wireless device based on the received first signal level, the received second signal level, and the received neighbor reporting criteria. In response to the triggered reporting event, wireless device202may transmit signal information comprising a signal level for the reference signal or pilot signal received from access node206and an identifier for access node206(e.g., a PCI, CGI, or the like).

At step308, a communication link is established between the first access node and the second access node based on the identifier when it is determined that the communication link has not previously been established between the first access node and the second access node. For example, access node204may comprise an NRT and it may be determined that neighbor information for access node206is not included in the NRT. Accordingly, a communication link (e.g., an X2 connection) may be established between access node204and access node206. In an embodiment, a handover may be performed of wireless device202from access node204to access node206based on the established communication link.

FIG. 4illustrates another exemplary communication system400to for managing access node neighbor relations. Communication system400may comprise a wireless device402, access nodes404and406, controller node408, gateway node410, communication network412, and communication links414,416,418,420,422,424,426,428, and430. Other network elements may be present in the communication system400to facilitate communication but are omitted for clarity, such as base stations, base station controllers, gateways, mobile switching centers, dispatch application processors, and location registers such as a home location register or visitor location register.

Wireless device402can be any device configured to communicate over communication system400using a wireless communication link. For example, wireless device402can include a cell phone, a smart phone, a computing platform such as a laptop, palmtop, or a tablet, a personal digital assistant, or an internet access device, and combinations thereof.

Access nodes404and406are network nodes capable of providing wireless communications to wireless device402, and can be, for example, a base transceiver station, a radio base station, an eNodeB device, or an enhanced eNodeB device. In an embodiment, access node404can comprise a serving access node for wireless device402. Access nodes404and406may communicate with controller node408over communication links420and422, and with gateway node410over communication links424and426. Access nodes404and406may also communicate directly with each other over communication link418.

Controller node408can be any network node configured to manage services within system400. Controller node408may provide other control and management functions for system400. The controller node408can be a single device having various functions or a plurality of devices having differing functions. For example, controller node408can include at least one of a multi-cell/multicast coordination entity (MCE), a mobility management entity (MME), a radio network controller (RNC), a mobile switching center (MSC), and a combination thereof. In an embodiment, controller node408may perform all or parts of the methods ofFIGS. 3 and 6-8.

Gateway node410is a network element which can comprise a processor and associated circuitry to execute or direct the execution of computer-readable instructions. Gateway node410may retrieve and execute software from storage, which can include a disk drive, flash drive, memory circuitry, or some other memory device, and which can be local or remotely accessible. The software comprises computer programs, firmware, or some other form of machine-readable instructions, and may include an operating system, utilities, drivers, network interfaces, applications, or some other type of software, including combinations thereof. In an embodiment, gateway node410can provide instructions to access nodes404and406related to channel selection in communications with wireless device402. For example, gateway node410can comprise at least one of a serving gateway (SGW), a packet data network gateway (PDNGW), a cellular gateway (CGW), and a combination thereof.

Communication links414,416,418,420,422,424,426,428, and430can be wired or wireless communication links. Wired communication links can be, for example, twisted pair cable, coaxial cable or fiber optic cable, or combinations thereof. Wireless communication links can be a radio frequency, microwave, infrared, or other similar signal, and can use a suitable communication protocol, for example, Global System for Mobile telecommunications (GSM), Code Division Multiple Access (CDMA), or Long Term Evolution (LTE), or combinations thereof. Other wireless protocols can also be used.

Other network elements may be present in the communication system400to facilitate wireless communication but are omitted for clarity, such as base stations, base station controllers, gateways, mobile switching centers, dispatch application processors, and location registers such as a home location register or visitor location register. Furthermore, other network elements may be present to facilitate communication among access nodes404and406, controller node408, gateway node410, and communication network412which are omitted for clarity, including additional processing nodes, routers, gateways, and physical and/or wireless data links for carrying data among the various network elements.

FIGS. 5A-5Cillustrates an exemplary communication system500for managing access node neighbor relations. System500comprises wireless device502A,502B, and502C, access nodes504and506, and communication link508B and508C. Wireless device502A,502B, and502C may comprise a single wireless device at different locations, and the device may be similar to wireless device402ofFIG. 4. Similarly, access nodes504and506may comprise access nodes similar to access node404ofFIG. 4. Communication link508B and508C may comprise a single communication link at different stages of completion (e.g.,508B may represent a communication link in the process of being established and508C may represent the established communication link), and the communication link may be similar to communication link418ofFIG. 4.

In operation, wireless device502A may establish communication with access node504such that access node504provides the wireless devices access to a communication network (such as communication network412, illustrated inFIG. 1). In an embodiment, communication system500may be configured to manage access node neighbor relations. For example, communication system500may implement a self-organizing network (SON) protocol that includes an automatic neighbor relations (ANR) process, or may implement any other suitable protocol for managing access node neighbor relations.

In an embodiment, access node504may not be aware of access node506. For example, access node504may track neighbor access nodes using a neighbor relations table (NRT) that stores information about access node504's neighbors. The NRT may store identifiers for neighbor access nodes (e.g., PCI, CGI, and the like), connection information (e.g., X2 connection information), handover information, and any other suitable neighbor information. In this example, access node504may not comprise an entry in the neighbor relations table for access node506.

In an embodiment, access node506may comprise a new access node. In other words, access node506may have been connected to communication network500recently (e.g., within a predetermined time period). In this example, access node504may not be aware of access node506because it is a new access node. Access node504may be configured to discover access node506using, for example, an ANR process.

In an embodiment, access node504may communicate with wireless device502A in order to discover neighbor access nodes506. Here, access node504may transmit a criteria, such as an ANR criteria, to wireless devices in communication with access node504(e.g., wireless device502A). The ANR criteria may comprise a signal level criteria. An ANR event may be triggered at the wireless device based on a comparison of the received ANR criteria, a signal level for a reference signal or pilot signal received from access node504, and a signal level for a reference signal or pilot signal received from access node506. For example, as illustrated inFIGS. 5A and 5B, as the wireless device moves from the location near access node504(i.e., wireless device502A) toward the location between access nodes504and506(i.e., wireless device502B), an ANR event may be triggered at the wireless device. In response to the triggered event, wireless device502B may transmit a measurement report comprising a signal level for each reference signal or pilot signal received at the wireless device (e.g., from a plurality of access nodes), and an identifier (e.g., PCI, CGI, and the like) for each access node. In an embodiment, the measurement report may comprise signal levels that are above a criteria (e.g., a determined threshold).

Access node504may receive the measurement report and compare the access node identifiers in the NRT against those in the received measurement report. Here, because access node504is not aware of access node506, the NRT for access node504does not include information about access node506. Accordingly, access node504may commence a process to add access node506as a neighbor (e.g., update the NRT to include information for access node506). For example, the process may include establishing a link between access node504and access node506(i.e., communication link508B in the process of being established). In an embodiment, access node504may instruct wireless device502to retrieve a global identifier for access node506and transmit the global identifier to access node504. Using the global identifier, access node504may retrieve an IP address for access node506(e.g., from a controller node such as an MME). A communication link (e.g., an X2 connection) may then be established between access node504and access node506(i.e., communication link508C has been established). Based on this process, access node504may update the NRT to include information about access node506.

As a result of the ANR process and the update to the NRT for access node504, a handover may be performed between access node504and access node506. For example, a handover from access node504to access node506may be performed when the wireless device is near access node506(i.e., wireless device502C) using communication link508C. However, in certain circumstances the handover may fail. For example, similar to the ANR criteria, a handover criteria used to trigger a handover between access node504and access node506may comprise a signal level criteria (e.g., A3 event signal level criteria). If the ANR signal level criteria is too close to the handover signal level criteria, a handover may fail due to lack of sufficient time to complete the ANR process. For example, if the handover were attempted prior to establishing communication link508C, the handover may fail. On the other hand, where the ANR signal level criteria it too far from the handover signal level criteria, ANR may be performed liberally and system resources may be inefficiently used. Accordingly, a system may be configured with an ANR criteria that efficiently uses system resources.

FIG. 6illustrates an exemplary method for managing access node neighbor relations. The method will be discussed with reference to the exemplary communication system500illustrated inFIG. 5, however, the method can be implemented with any suitable communication system.

Referring toFIG. 6, at step602, an application requirement of a wireless device communicating with a first access node is determined. For example, wireless device502A may be in communication with access node504, and an application requirement for the wireless device may be determined. An application requirement, or a quality of service (QoS) requirement, may be one or more service conditions that a wireless device requests from an access node, such as a quality of service class identifier (QCI), a minimum guaranteed bit rate (GBR), maximum bit rate (MBR), a priority, a minimum bit rate, a maximum permitted data delay, a minimum throughput, a maximum error rate, a maximum data loss rate, and any other application requirement. In an embodiment, the determined application requirement may be based on one or more applications running on wireless device502A.

At step604, a delta is calculated based on the determined application requirement. A delta may comprise a difference between a signal level for a handover criteria (e.g., A3 handover criteria) and a signal level for an ANR criteria (e.g., signal level to trigger an ANR reporting event at a wireless device). For example, based on an application requirement determined for wireless device502A, a delta may be calculated. The method ofFIG. 8further describes step604.

At step606, a neighbor reporting criteria is calculated based on the calculated delta. For example, a delta may be calculated based on an application requirement determined for wireless device502A, and a neighbor reporting criteria may be calculated as a sum of the delta and a handover signal level criteria. This may be expressed as: NRCriteria=HOCriteria+Delta, where NRCriteria=Neighbor reporting criteria, HOcriteria=Handover criteria (e.g., A3 event signal level criteria), and Delta=Calculated Delta (e.g., at step604).

At step608, the calculated neighbor reporting criteria is transmitted from the first access node. For example, the calculated neighbor reporting criteria may be transmitted from access node504to wireless devices in communication with the access node (e.g., wireless device502A).

At step610, an identifier of a second access node is received in response to a reporting event triggered at the wireless device based on a first signal level of the first access node, a second signal level of the second access node, and the neighbor reporting criteria. For example, the calculated neighbor reporting criteria may be transmitted from access node504to wireless device502A. The wireless device may move to the location illustrated as wireless device502B, and wireless device502B may receive a reference signal or pilot signal from access node504at a received signal level and a reference signal or pilot signal from access node506at a received signal level. In an embodiment, a reporting event may be triggered at wireless device502B based on the received first signal level, the received second signal level, and the received neighbor reporting criteria. In response to the triggered reporting event, wireless device502B may transmit signal information comprising a signal level for the reference signal or pilot signal received from access node506and an identifier for access node506(e.g., a PCI, CGI, or the like).

At step612, a communication link is established between the first access node and the second access node based on the identifier when it is determined that the communication link has not previously been established between the first access node and the second access node. For example, access node504may comprise an NRT and it may be determined that neighbor information for access node506is not included in the NRT. Accordingly, a process may be implemented to established a communication link508B (e.g., an X2 connection) between access node204and access node206. At the conclusion of the process, communication link508C may be established. The NRT may be updated to include neighbor information about access node206, as described herein. In an embodiment, a handover may be performed of wireless device202from access node204to access node206based on the established communication link.

FIG. 7illustrates an exemplary method for managing access node neighbor relations. The method ofFIG. 7may follow the method ofFIG. 6. The method will be discussed with reference to the exemplary communication system500illustrated inFIG. 5, however, the method can be implemented with any suitable communication system.

Referring toFIG. 7, at step702, a measurement report may be received from the wireless device comprising a determined signal level for the first access node and a determined signal level for the second access node. For example, the wireless device may move from the location illustrated as wireless device502B to the location illustrated as wireless device502C. Wireless device502C may receive a reference signal or pilot signal from access node504at a received signal level and a reference signal or pilot signal from access node506at a received signal level. A reporting event may be triggered at wireless device502C based on the received first signal level, the received second signal level, and a handover signal level criteria, such as the handover signal level criteria used to calculate the delta at step606ofFIG. 6(e.g., A3 event signal level criteria).

At step704, the wireless device is instructed to perform a handover. For example, based on one or more measurement reports received at access node504from wireless device502C, the wireless device may be instructed to communicate with access node506rather than access node504.

At step706, a handover may be performed using the established communication link. For example, a handover of wireless device502from access node504to access node506may be performed, where access node504and access node506communicate over established communication link508C to perform the handover.

FIG. 8illustrates an exemplary method for calculating a delta used in neighbor relations management. Step604ofFIG. 6may further comprise the method steps ofFIG. 8. The method will be discussed with reference to the exemplary communication system500illustrated inFIG. 5, however, the method can be implemented with any suitable communication system.

Referring toFIG. 8, at step802, an application requirement of a wireless device communicating with a first access node is determined. For example, wireless device502A may be in communication with access node504, and an application requirement for the wireless device may be determined. An application requirement, or a quality of service (QoS) requirement, may be one or more service conditions that a wireless device requests from an access node, such as a quality of service class identifier (QCI), a minimum guaranteed bit rate (GBR), maximum bit rate (MBR), a priority, a minimum bit rate, a maximum permitted data delay, a minimum throughput, a maximum error rate, a maximum data loss rate, and any other application requirement. Based on the determined application requirement, an application requirement factor may be calculated. Here, when the application requirement has been determined to meet a criteria (e.g., a maximum allowed delay below a threshold), the application requirement factor may be adjusted from a default value to a lower value. When the application requirement has been determined not to meet a criteria (e.g., a maximum allowed delay above a threshold) the application requirement factor may be adjusted from a default value to a higher value.

At step804, a mobility may be determined for the wireless device. For example, a mobility may be determined for wireless device502A. The mobility may comprise a movement vector for the wireless device based on, for example, signal levels reported from the wireless device (e.g., to access node504). Based on the determined mobility, a mobility factor may be calculated. Here, when the wireless device502A has been determined to be of high mobility (e.g., mobility above a mobility criteria), the mobility factor may be adjusted from a default value to a higher value. When the wireless device502A has been determined to be of low mobility (e.g., mobility below a mobility criteria), the mobility factor may be adjusted from a default value to a lower value.

At step806, a probability may be determined. For example, a probability of access node504discovering a new access node (e.g., access node506) may be determined. In an embodiment, access node504may comprise an NRT and the probability may be the probability that neighbor information about access node506is not included in the NRT. Based on the determined probability, a probability factor may be calculated. Here, when the network has been updated recently (e.g., a portion of the network near access node504has been updated with a new network element), the probability factor may be adjusted from a default value to a higher value. When the network has not been updated recently, the probability factor may be adjusted from a default value to a lower value.

At step808, a number of signals received by a wireless device in communication with the first access node is determined. For example, wireless device502A may transmit a report (e.g., a measurement report or a neighbor report) to access node504that comprises signal levels for signals received at wireless device502A from a plurality of access nodes. A number of signals included in the report may be determined. Based on the determined number of signals, a signals factor may be calculated. Because a high number of signals may be indicative of a densely populated network (e.g., many access nodes near access node504), performing ANR too liberally may be an inefficient use of resources. On the other hand, a low number of signals may indicate that access node504could benefit from additional neighbors, and therefore ANR may be encouraged. Accordingly, when the number of signals are high (e.g., above a threshold), the signals factor may be adjusted from a default value to a lower value, and when the number of signals are low (e.g., below a threshold), the signals factor may be adjusted from a default value to a higher value.

At step810, it may be determined whether the wireless device is performing inter-frequency scanning. For example, it may be determined whether wireless device502A is performing inter-frequency scanning. Inter-frequency scanning may be performed at wireless device502A based on, for instance, instruction from access node504. When received signal levels from wireless device502A fall below a criteria (e.g., as reported to access node504in a measurement report), access node504may instruct wireless device502A to perform inter-frequency scanning. Based on the determination, an inter-frequency factor may be calculated. Here, where wireless device502A is determined not to be performing inter-frequency scanning, the inter-frequency factor may be zero. In an embodiment, where wireless device502A is determined to be performing inter-frequency scanning and wireless device502A comprises an application requirement that meets a criteria (e.g., a maximum allowed delay below a threshold), the inter-frequency factor may be adjusted from a default value to a lower value.

At step812, a delta may be calculated. For example, a delta may be calculated based on the one or more factors. This may be expressed as: Delta=AppReqFactor+MobilityFactor+ProbabilityFactor+SignalsFactor+Inter-FrequencyFactor, where AppReqFactor=Application Requirement Factor, MobilityFactor=Mobility Factor, ProbabilityFactor=Probability Factor, SignalsFactor=Signals Factor, and Inter-FrequencyFactor=Inter-Frequency Factor. In an embodiment, the delta may be calculated based on one of these factors, or a combination of at least two of these factors. In this example, when an ANR process is encouraged (e.g., encouraged to occur more than a default setting), the calculated delta value may be a value greater than a default delta value, and when the ANR process is discouraged (e.g., discouraged to occur less than the default setting), the calculated delta value may be a value less than the default delta value.

After the delta is calculated, a neighbor reporting criteria may be calculated based on the delta, as described with reference to step606ofFIG. 6. For example, the delta may comprise a difference between a signal level for a handover criteria (e.g., A3 handover criteria) and a signal level for an ANR criteria (e.g., signal level to trigger an ANR reporting event at a wireless device). In an embodiment, the neighbor reporting criteria may be calculated as a sum of the delta and the handover signal level criteria. The method may then proceed to step608ofFIG. 6, as described herein.

Although the methods described perform steps in a particular order for purposes of illustration, the methods discussed herein are not limited to any particular order or arrangement. One skilled in the art, using the disclosure provided herein, will appreciate that various steps of the methods can be omitted, rearranged, combined, and/or adapted in various ways.

FIG. 9illustrates an exemplary processing node900in a communication system. Processing node900comprises communication interface902, user interface904, and processing system906in communication with communication interface902and user interface904. Processing node900can be configured to determine a communication access node for a wireless device. Processing system906includes storage908, which can comprise a disk drive, flash drive, memory circuitry, or other memory device. Storage908can store software910which is used in the operation of the processing node900. Storage908may include a disk drive, flash drive, data storage circuitry, or some other memory apparatus. Software910may include computer programs, firmware, or some other form of machine-readable instructions, including an operating system, utilities, drivers, network interfaces, applications, or some other type of software. Processing system906may include a microprocessor and other circuitry to retrieve and execute software910from storage908. Processing node900may further include other components such as a power management unit, a control interface unit, etc., which are omitted for clarity. Communication interface902permits processing node900to communicate with other network elements. User interface904permits the configuration and control of the operation of processing node900.

Examples of processing node900include controller node408and gateway node410. Processing node900can also be an adjunct or component of a network element, such as an element of access nodes104,106,404, or406. Processing node1300can also be another network element in a communication system. Further, the functionality of processing node1300can be distributed over two or more network elements of a communication system.

Examples of the computer-readable recording medium include, but are not limited to, read-only memory (ROM), random-access memory (RAM), erasable electrically programmable ROM (EEPROM), flash memory or other memory technology, holographic media or other optical disc storage, magnetic storage including magnetic tape and magnetic disk, and solid state storage devices. The computer-readable recording medium can also be distributed over network-coupled computer systems so that the computer-readable code is stored and executed in a distributed fashion. The communication signals transmitted through a transitory medium may include, for example, modulated signals transmitted through wired or wireless transmission paths. The above description and associated figures teach the best mode of the invention. The following claims specify the scope of the invention. Note that some aspects of the best mode may not fall within the scope of the invention as specified by the claims. Those skilled in the art will appreciate that the features described above can be combined in various ways to form multiple variations of the invention, and that various modifications may be made to the configuration and methodology of the exemplary embodiments disclosed herein without departing from the scope of the present teachings. Those skilled in the art also will appreciate that various features disclosed with respect to one exemplary embodiment herein may be used in combination with other exemplary embodiments with appropriate modifications, even if such combinations are not explicitly disclosed herein. As a result, the invention is not limited to the specific embodiments described above, but only by the following claims and their equivalents.