CA2952402C

CA2952402C - Device managed access point lists in wireless communications

Info

Publication number: CA2952402C
Application number: CA2952402A
Authority: CA
Inventors: Srinivasan Balasubramanian; Manoj M. Deshpande; Young C. Yoon; Gavin B. Horn
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2008-03-26
Filing date: 2009-03-26
Publication date: 2018-06-12
Anticipated expiration: 2029-03-26
Also published as: US20090245176A1; TW201334584A; TWI428033B; CA2854961C; CA2952442C; IL235311B; MY174454A; EP2272285A2; EP2272285B1; KR101269058B1; CA2952408A1; TW201330655A; PH12014500376A1; CN102067678B; HK1158422A1; TWI499319B; KR101266316B1; TWI507053B; PH12014500375A1; JP2016067031A

Abstract

Systems and methodologies are described that facilitate device-side access point list management. Blacklists of access points unsuitable for providing network access to a related mobile device can be maintained as well as whitelists of suitable access points. The lists can be managed using an interface provided at the mobile device. In addition, lists can be modified according to provisioned network updates. Also, the lists can be of maximum size such that older entries can be purged upon insertion of newer entries based on a number of factors; timed entry deletion is provided as well. Access points in the lists can be stored and presented according to various identifiers related to the access points.

Description

DEVICE MANAGED ACCESS POINT LISTS IN WIRELESS
COMMUNICATIONS
[0001] This is a divisional of Canadian National Phase Patent Application Serial No. 2,719,604 filed on March 26, 2009.
[0001a] The present Application for Patent claims priority to Provisional Application No. 61/039,728 entitled "SYSTEMS AND METHODS TO MANAGE MOBILE STATION
LEARNED INFORMATION WITHIN A NETWORK" filed March 26, 2008, and assigned to the assignee hereof as well as Provisional Application No. 61/102,325 entitled "SYSTEMS
AND METHODS TO ENABLE USER CONTROLLED ACCESS LISTS FOR BASE
STATIONS" filed October 2, 2008, as well as to U.S. Patent Application No.
12/407,714 entitled "DEVICE MANAGED ACCESS POINT LISTS IN WIRELESS
COMMUNICATIONS" filed March 19, 2009.
Field

[0002] The following description relates generally to wireless communications, and more particularly to access point lists.
Background

[0003] Wireless communication systems are widely deployed to provide various types of communication content such as, for example, voice, data, and so on. Typical wireless communication systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, ...). Examples of such multiple-access systems may include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and the like. Additionally, the systems can conform to specifications such as third generation partnership project (3GPP), 3GPP long term evolution (LTE), ultra mobile broadband (UMB), and/or multi-carrier wireless specifications such as evolution data optimized (EV-D0), one or more revisions thereof, etc.

1a =

[0004] Generally, wireless multiple-access communication systems may simultaneously support communication for multiple mobile devices. Each mobile device may communicate with one or more access points (e.g., base stations) via transmissions on forward and reverse links. The forward link (or downlink) refers to the communication link from access points to mobile devices, and the reverse link (or uplink) refers to the communication link from mobile devices to access points. Further, communications between mobile devices and access points may be established via single-input single-output (SISO) systems, multiple-input single-output (MISO) systems, multiple-input = multiple-output (MTMO) systems, and so forth. In addition, mobile devices can communicate with other mobile devices (and/or access points with other access points) in peer-to-peer wireless network configurations.

[0005] As mobile devices initiate communications with a wireless network and/or move throughout service areas, the mobile devices can select and/or reselect cells utilized for communication between one or more access points providing the cells (e.g., macrocells, femtocells, etc.). The mobile devices can measure parameters related to one or more = access points and/or related cells, such as signal quality, service level, etc. and rank according to desirability, which can be based on one or more of the parameters. Upon detecting an access point that offers an optimal signal or service as compared to a current access point or other neighboring access points, the mobile device can select or reselect the access point to receive wireless network access.
SUMMARY
[00061 The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
[0007] In accordance with one or more aspects and corresponding disclosure thereof, various aspects are described in connection with facilitating maintaining lists of unsuitable and/or suitable access points, or related cells, at a mobile device. The lists can be utilized in selecting and/or reselecting access points for receiving wireless network access where unsuitable access points are not selected regardless of desirability of other communication parameters and suitable access points can be selected though other neighboring access points can have more desirable communication parameters. In one example, the lists can be maintained by the mobile device and updated using a provided interface, event detector, etc. In addition, however, the wireless network can provision operations on the list including adding/removing entries, flushing the lists, and/or the like, to the mobile device.
[00081 According to related aspects, a method is provided including maintaining an operator controlled list of identifiers related to access points in a wireless network. The method also includes maintaining a user controlled list of identifiers related to access points in the wireless network and utilizing the operator controlled list and the user - controlled list in determining one or more access points for requesting access to the wireless network [0009] Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to manage an operator controlled list of identifiers related to access points in a wireless network. The at least one processor is further configured to manage a user controlled list of identifiers related to access points in the wireless network and determine one or more access points = for requesting access to the wireless network based on the operator controlled list and/or the user controlled list. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
[0010] Yet another aspect relates to an apparatus that includes means for maintaining an operator controlled list of identifiers related to access points in a wireless network and a user controlled list of identifiers related to access points in the wireless network The apparatus can additionally include means for determining one or more access points for ' requesting access to the wireless network based on the operator controlled list and/or the user controlled list.
[00111 Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to maintain an operator controlled list of identifiers related to access points in a wireless network.
The computer-readable medium can also comprise code for causing the at least one computer to maintain a user controlled list of identifiers related to access points in the = wireless network. Moreover, the computer-readable medium can comprise code for causing the at least one computer to utilize the operator controlled list and the user controlled list in determining one or more access points for requesting access to the vireless network.
[0012] Moreover, an additional aspect relates to an apparatus. The apparatus can include a list maintainer that manages an operator controlled list of identifiers related to access points in a wireless network and a user controlled list of identifiers related to access points in the wireless network. The apparatus further includes an access point evaluator that utilizes the operator controlled list and/or the user controlled list in selecting an access point from which to request access to the wireless network.
[0013] According to another aspect, a method is provided including maintaining a blacklist of identifiers related to unsuitable access points for providing access to a wireless network. The method also includes modifying the blacklist according to a command received from the wireless network and utilizing the blacklist in determining one or more access points for requesting access to the wireless network.
[0014] Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to manage a blacklist of access points unsuitable for providing wireless network access to the wireless communications apparatus and update at least one blacklist access point entry based at least in part on a network command related to a determined modification in an operating parameter for the blacklist access point entry. The at least one processor is further configured to request network access to an access point based at least in part on verifying absence of the access point in the blacklist. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
[0015] Yet another aspect relates to an apparatus that includes means for maintaining a blacklist of access points unsuitable for providing access to a wireless network and means for modifying the blacklist according to an update command received from the wireless network. The apparatus can additionally include means for analyzing the blacklist in requesting wireless network access from one or more access points.
[0016] Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to maintain a blacklist of identifiers related to unsuitable access points for providing access to a wireless network. The computer-readable medium can also comprise code for causing the at least one computer to modify the blacklist according to a command received from the wireless network. Moreover, the computer-readable medium can comprise code for = causing the at least one computer to utilize the blacklist in determining one or more access points for requesting access to the wireless network.
[0017] Moreover, an additional aspect relates to an apparatus. The apparatus can include a list maintainer that manages a blacklist of access points unsuitable for providing access to a wireless network and a network command analyzer that processes one or more commands, received from the wireless network, to update the blacklist.
The apparatus further includes an access point evaluator that utilizes the blacklist in selecting an access point from which to request access to the wireless network.
[0018] According to another aspect, a method is provided including determining modification of an operating parameter related to one or more access points.
The method also includes transmitting a command to update a local blacklist to one or more mobile devices based on the operating parameter modification.
[0019] Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to detect a modification to an operating parameter related to one or more access points and generate a network command to provision an update to a blacklist of access points unsuitable for providing network access. The at least one processor is further configured to transmit the network command to a mobile device. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
[0020] Yet another aspect relates to an apparatus that includes means for receiving a parameter modification related to an access point in a wireless network. The apparatus can additionally include means for provisioning a network command to update a local blacklist to one or more mobile devices in the wireless network based on the parameter modification.
[0021] Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to determine modification of an operating parameter related to one or more access points.
The computer-readable medium can also comprise code for causing the at least one computer to transmit a command to update a local blacklist to one or more mobile devices based on the operating parameter modification.
100221 Moreover, an additional aspect relates to an apparatus. The apparatus can include a parameter change evaluator that determines a modified operating parameter related to one or more access points in a wireless network. The apparatus further includes a network command provisioner that transmits a list update command to one or more mobile devices based at least in part on the modified operating parameter.

6 [0023] According to another aspect, a method is provided including maintaining a blacklist of access points unsuitable for providing access to a wireless network based at least in part on one or more commands received from a provided user interface.
The method also includes detecting an access point that provides access to the wireless network and scanning for one or more disparate access points based at least in part on = identifying the access point in the blacklist.
[0024] Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to manage a blacklist of access points unsuitable for providing wireless network access to the wireless communications apparatus based at least in part on one or more requests received from a provided user interface. The at least one processor is further configured to detect an access point that provides access to the wireless network and analyze one or more disparate access points based at least in part on identifying the access point in the blacklist. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
[0025] Yet another aspect relates to an apparatus that includes means for maintaining a blacklist of access points unsuitable for providing access to a wireless network. The apparatus can additionally include means for modifying the blacklist according to an update command received from a provided user interface and means for analyzing the blacklist in requesting wireless network access from one or more access points in the wireless network.
[0026] Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to maintain a blacklist of access points unsuitable for providing access to a wireless network based at least in part on one or more commands received from a provided user interface. The computer-readable medium can also comprise code for causing the at least one computer to detect an access point that provides access to the wireless network.
Moreover, the computer-readable medium can comprise code for causing the at least one computer to scan for one or more disparate access points based at least in part on identifying the access point in the blacklist.
[0027] Moreover, an additional aspect relates to an apparatus. The apparatus can include an interface that receives one or more commands to update a blacklist of access points unsuitable for providing access to a wireless network. The apparatus further

7 includes a list maintainer that manages the blacklist based at least in part on the one or more commands and an access point evaluator that utilizes the blacklist in selecting an access point from which to request access to the wireless network.
[0028] According to another aspect, a method is provided including maintaining a plurality lists of access point identifiers corresponding to a group of access points, which provide similar access to a wireless network and detecting an access point that = advertises an identifier present in at least one of the lists. The method also includes determining whether to establish a connection with the access point based at least in part on presence of the identifier in the at least one list [00291 Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to manage a plurality of lists of access point identifiers, the identifiers are related to a group of access points that provide similar access to a wireless network and detect an access = point that provides access to the wireless network and advertises an identifier present in at least one of the lists. The at least one processor is further configured to determine whether to establish communication with the access point based on presence of the identifier in the at least one list and a type of the at least one list. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
[0030] Yet another aspect relates to an apparatus that includes means for maintaining a ' plurality of lists of access point identifiers, the identifiers are related to a group of access points that provide similar access to a wireless network and means for analyzing at least one of the lists to detect presence of an identifier of an access point. The apparatus can additionally include means for establishing communication with the access point based on analyzing the at least one list.
[0031] Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to maintain a plurality lists of access point identifiers corresponding to a group of access points, which provide similar access to a wireless network. The computer-readable medium can also comprise code for causing the at least one computer to detect an access point that advertises an identifier present in at least one of the lists. Moreover, the computer-readable medium can comprise code for causing the at least one computer to determine =

=
=
whether to establish a connection with the access point based at least in part on presence . of the identifier in the at least one list 10032] Moreover, an additional aspect relates to an apparatus. The apparatus can include a list maintainer that manages a plurality of lists of access point identifiers, the identifiers correspond to groups of access points that provide similar access to a wireless network. The apparatus further includes an access point evaluator that detects an access point that advertises an identifier and establishes communication with the access point based at least in part on analyzing at least one of the lists to determine whether the . identifier is present.
[0033] According to another aspect, a method is provided including maintaining one or more lists of access point communication parameters computed from signals received from the respective access points and computing an access point communication parameter from a signal received from the access point. The method also includes determining whether to establish a connection with the access point based at least in part on presence of the computed communication parameter in the at least one list.
= [0034] Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to manage a list of access point communication parameters computed from one or more signals received from the respective access points. The at least one processor is further configured to determine a communication parameter related to an access point and determine whether to establish communication with the access point based on presence of the communication parameter in the list. The wireless communications apparatus = also comprises a memory coupled to the at least one processor.
100351 Yet another aspect relates to an apparatus that includes means for maintaining a list of access point communication parameters determined from one or more signals received from the access points. The apparatus can additionally include means for determining a communication parameter related to an access point and means for establishing communication with the access point based at least in part on determining whether the communication parameter is in the list.
= [0036] Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to maintain one or more lists of access point communication parameters computed from signals received from the respective access points. The computer-readable medium can also = 74769-3106D6 =

comprise code for causing the at least one computer to compute an access point communication parameter from a signal received from the access point.
Moreover, the computer-readable medium can comprise code for causing the at least one computer to = determine whether to establish a connection with the access point based at least in part on presence of the computed communication parameter in the at least one list.
[00371 Moreover, an additional aspect relates to an apparatus. The apparatus can include a list maintainer that manages a list of access point communication parameters calculated from one or more signals received from related access points. The apparatus further includes an access point evaluator that determines an access point communication parameter and establishes communication with the access point based at = least in part on analyzing the list to determine whether the communication parameter is present.
[00381 According to another aspect, a method is provided including maintaining a blacklist of access points unsuitable for providing access to a wireless network and determining a time duration during which an access point is present in the blacklist.
The method also includes computing a deletion time for the access point from the blacklist based at least in part on the time duration.
= [00391 Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to manage a blacklist of access points unsuitable for providing access to a wireless network. The at least one processor is further configured to discern a time duration related to presence of an access point in the blacklist and calculate a deletion time for the access point from the blacklist based at least in part on the time duration. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
[00401 Yet another aspect relates to an apparatus that includes means for maintaining a blacklist of access points unsuitable for providing access to a wireless network and means for receiving a time duration during which the access point is present in the = blacklist. The apparatus can additionally include means for determining a deletion time for the access point from the list based at least in part on the time duration.
[0041] Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to maintain a blacklist of access points unsuitable for providing access to a wireless network. The computer-readable medium can also comprise code for causing the at least one , 74769-3106D6 =
computer to determine a time duration which an access point is present in the blacklist.
Moreover, the computer-readable medium can comprise code for causing the at least one computer to compute a deletion time for the access point from the blacklist based at least in part on the time duration.
5 [00421 Moreover, an additional aspect relates to an apparatus.
The apparatus can include a list maintainer that manages a blacklist of access points unsuitable for providing access to a wireless network. The apparatus further includes a list entry timer that computes a deletion time for an access point from the blacklist based at least in part on a determined time duration for which the access point has been in the blacklist.
10 [0042a1 According to one aspect of the present invention, there is provided an apparatus, comprising: an interface that receives one or more commands to update a user controlled list of identifiers related to access points for providing access to a wireless network;
at least one processor; a non-transitory computer-readable medium coupled to the interface storing codes that when executed by the processor cause the apparatus to:
manage the user controlled list based at least in part on the one or more commands and based on an update in at least one operating parameter for an access point; and utilize the user controlled list in selecting an access point from which to request access to the wireless network based at least in part on determining an identifier of the access point is not included in the user controlled list.
[00431 To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and this description is intended to include all such aspects and their equivalents.
BRIEF DESCRIPTION OF THE DRAWINGS
[0044] FIG. 1 is an illustration of a wireless communication system in accordance with various aspects set forth herein.

, 74769-3106D6 =
10a [0045] FIG. 2 is an illustration of a wireless communication network in accordance with aspects described herein.
[0046] FIG. 3 is an illustration of an example communications apparatus for employment within a wireless communications environment.
[0047] FIG. 4 is an illustration of an example wireless communications system that effectuates maintaining local lists of access points for subsequent communication establishment.
[0048] FIG. 5 is an illustration of example interfaces in accordance with aspects described herein.
[0049] FIG. 6 is an illustration of an example methodology that facilitates utilizing a locally managed blacklist.
100501 FIG. 7 is an illustration of an example methodology that facilitates managing access point lists based on commands received from an interface.

=

[0051] FIG. 8 is an illustration of an example methodology that facilitates network provisioning of access point lists and related updates.
[0052] FIG. 9 is an illustration of an example methodology that facilitates maintaining a plurality of access point lists.
[0053] FIG. 10 is an illustration of an example mobile device that facilitates managing lists of access points.
[0054] FIG. 11 is an illustration of an example wireless network environment that can be employed in conjunction with the various systems and methods described herein.
[0055] FIG. 12, is an illustration of an example system that maintains multiple access point lists.
[0056] FIG. 13 is an illustration of an example system that facilitates maintaining a local blacklist based at least in part on received network commands.
[0057] FIG. 14 is an illustration of an example system that facilitates providing network update commands for local blacklist management.
[0058] FIG. 15 is an illustration of an example system that updates a blacklist of access points according to user interface commands.
[0059] FIG. 16 is an illustration of an example system that receives whitelist updates from a provided user interface.
= [0060] FIG. 17 is an illustration of an example system that maintains a plurality of lists of access points.
[0061] FIG. 18 is an illustration of an example system that facilitates maintaining a list of access points using communication parameters associated therewith.
[0062] FIG. 19 is an illustration of an example system that manages access point lists based on timers.
DETAILED DESCRIPTION
[0063] Various aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details.
[0064] As used in this application, the terms "component," "module," "system"
and the . like are intended to include a computer-related entity, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in . .

execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.
. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal_ [0065] Furthermore, various aspects are described herein in connection with a terminal, = which can be a wired terminal or a wireless terminal. A terminal can also be called a system, device, subscriber unit, subscriber station, mobile station, mobile, mobile device, remote station, remote terminal, access terminal, user terminal, terminal, communication device, user agent, user device, or user equipment (UE). A
wireless terminal may be a cellular telephone, a satellite phone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless connection capability, a computing device, or other processing devices connected to a wireless modem. Moreover, various aspects are described herein in connection with a base station. A base station may be utilized for communicating with wireless terminal(s) and may also be referred to as an access point, a Node B, or some other terminology.
[0066] Moreover, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless specified otherwise, or clear from the context, the phrase "X employs A or B" is intended to mean any of the natural inclusive permutations.
That is, the phrase "X employs A or B" is satisfied by any of the following instances: X
employs A; X employs B; or X employs both A and B. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from the context to be directed to a singular form.

[0067] The techniques described herein may be used for various wireless = communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are often used interchangeably. A
COMA system may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and other variants of COMA. Further, cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE
802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM , etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP
= Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). Additionally, cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2"
(3GPP2). Further, such wireless communication systems may additionally include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often using unpaired unlicensed spectrums, 802.xx wireless LAN, BLUETOOTH and any other short- or long- range, wireless communication techniques.
[00681 Various aspects or features will be presented in terms of systems that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc.
discussed in connection with the figures. A combination of these approaches may also be used.
[0069] Referring now to Fig. 1, a wireless communication system 100 is illustrated in accordance with various embodiments presented herein. System 100 comprises a base station 102 that can include multiple antenna groups. For example, one antenna group can include antennas 104 and 106, another group can comprise antennas 108 and 110, and an additional group can include antennas 112 and 114. Two antennas are illustrated for each antenna group; however, more or fewer antennas can be utilized for each group. Base station 102 can additionally include a transmitter chain and a receiver chain, each of which can in turn comprise a plurality of components associated with signal transmission and reception (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, antennas, etc.), as will be appreciated by one skilled in . the art.
100701 Base station 102 can communicate with one or more mobile devices such as mobile device 116 and mobile device 126; however, it is to be appreciated that base station 102 can communicate with substantially any number of mobile devices similar to mobile devices 116 and 126. Mobile devices 116 and 126 can be, for example, cellular phones, smart phones, laptops, handheld communication devices, handheld computing devices, satellite radios, global positioning systems, PDAs, and/or any other suitable ' device for communicating over wireless communication system 100. As depicted, mobile device 116 is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to mobile device 116 over a forward link 118 and receive information from mobile device 116 over a reverse link 120. In a frequency division duplex (FDD) system, forward link 118 can utilize a different frequency band than that used by reverse link 120, for example. Further, in a time division duplex (TDD) system, forward link 118 and reverse link 120 can utilize a common frequency.
[00711 Each group of antennas and/or the area in which they are designated to communicate can be referred to as a sector or cell of base station 102. For example, antenna groups can be designed to communicate to mobile devices in a sector of the areas covered by base station 102. In communication over forward link 118, the transmitting antennas of base station 102 can utilize beamforming to improve signal-to-noise ratio of forward link 118 for mobile device 116. Also, while base station 102 utilizes beamforming to transmit to mobile device 116 scattered randomly through an associated coverage, mobile devices in neighboring cells can be subject to less interference as compared to a base station transmitting through a single antenna to all its mobile devices. Moreover, mobile devices 116 and 126 can communicate directly with one another using a peer-to-peer or ad hoc technology.
100721 In addition, the base station 102 can communicate with a network 122, which can be one or more networks including a wireless service access network (e.g., a 3G
- network), over a backhaul link connection. The network 122 can store information regarding access parameters related to the mobile device 116 and 126 and other parameters of a wireless access network to provide service to the devices 116 and 126.

Furthermore, a femtocell 124 can be provided to facilitate communicating with the mobile device 126 over forward link 128 and reverse link 130 (similarly to forward link 118 and reverse link 120, as described supra). The femtocell 124 can provide access to one or more mobile devices 126 much like the base station 102, but on a smaller scale.
In one example, femtocell 124 can be configured in a residence, business, and/or other . close range setting (e.g., theme park, stadium, apartment complex, etc.).
The femtocell 124 can connect to the network 122 utilizing a backhaul link connection, which can be over a broadband Internet connection (T1/T3, digital subscriber line (DSL), cable, etc.), in one example. The network 122 can similarly provide access information for the mobile device 126.
[0073] According to an example, mobile devices 116 and 126 can travel over service areas initiating wireless access or performing cell reselection among disparate base = stations and/or femtocells during travel or while stationary. In this regard, the mobile devices 116 and 126 can effectuate continuous wireless service seamless to users of the mobile devices 116 and 126. In one example (not shown), mobile device 126 can have been communicating with the base station 102 similarly to the mobile device 116, and can have moved into a specified range of the femtocell 124. In this regard, the mobile device 126 can have reselected one or more cells related to the femtocell 124 to receive more desirable wireless service access. In one example, the femtocell 124 can be a home access point for the mobile device 126 offering more desirable billing and/or other access options. In another example, the femtocell 124 can be related to a business or venue offering options or data tailored to the respective business or venue.
Thus, mobile device 126 can reselect one or more cells related to the femtocell 124, in an idle and/or connected mode, to receive such tailored options. In addition, where mobile device 126 moves toward base station 102, it can reselect a cell related thereto, at some point, for a variety of reasons (e.g., to mitigate interference on the femtocell 124, to receive a more optimal signal or increased throughput, etc.).
[0074] In traveling over the service area, a given mobile device 116 and/or 126 can continually measure available base stations (such as base station 102), femtocells (such as femtocell 124), and/or other access points, to determine when cell reselection is beneficial to the mobile device 116 and/or 126. The measuring can include, for example, evaluating signal quality, throughput, services available, a wireless access provider related to the access point, and/or the like. Based on one or more of the measurements, the mobile device 116 and/or 126 can rank access points for reselection.
Upon determining the ranking, the mobile device 116 and/or 126 can attempt cell reselection with the highest ranking access point.
[00751 In addition, the mobile devices 116 and 126 can maintain a blacklist of unsuitable access points and/or groups of access points, a whitelist of suitable access points and/or groups of accessible access points, and/or the like. The lists can comprise identifiers related to the cells, such as a cell identifier, a related PN
offset, bandclass, . radio channel, a group identifier associated with cells having common communication parameters, offering similar services, and/or the like. The mobile devices 116 and 126 can receive such identifiers from the base station 102 and/or femtocell 124 and can utilize the lists in selecting or reselecting cells for communication. In one example, at least one mobile device 116 and/or 126 can ignore or otherwise not choose cells or related access points or groups in the blacklist for selection/reselection and/or measuring related thereto. Similarly, the mobile device 116 and/or 126 can select cells or related access points or groups in the whitelist over other cells though the other cells have more desirable communication metrics, in one example. Moreover, the mobile device and/or 126 can maintain the blacklist and/or whitelist.
100761 In one example, the mobile device 116 and/or 126 can comprise an interface that allows a user to manage and maintain the blacklist and/or whitelist; the interface can permit a user thereof to add and/or remove cells from the lists, mark cells as permanent list members, and/or the like. In this regard, a user desiring access to a cell whenever the cell is in range can add the cell to the whitelist, and a user that wishes to ignore a cell though the cell is in range can add the cell to the blacklist. In the depicted example, mobile device 126 can have added femtoCell 124 to its whitelist, and the mobile device = 126 can select femtocell 124 for access though the base station 102 may have more desirable communication parameters. Similarly, the mobile device 116 can have added the femtocell 124 to its blacklist and accordingly connect to the base station 102 though . the femtocell 124 may have various more desirable parameters with respect to the mobile device 116.
[00771 In another example, the mobile devices 116 and 126 can maintain the lists based on events occurring with respect to the mobile device, base station 102, network 122, etc. For example, where the mobile device 116 and/or 126 receives one or more denials or failures in attempting to access a base station related to a given cell, the mobile =

device 116 and/or 126 can add the cell or related base station to its blacklist In addition, the lists can be modified according to a command from the network 122.
Thus, the mobile devices 116 and 126 can receive such a command and modify its respective list accordingly. Moreover, the network 122 can provision a global list to the mobile devices 116 and 126, as well as changes to the global list; the mobile devices 116 and 126 can also maintain their respective local lists. Additionally, the mobile devices 116 and 126 can resolve conflicts between local and global lists according to schemes provisioned by the user, mobile device, network 122, and/or the like.
[0078] Now referring to Fig. 2, a wireless communication system 200 configured to support a number of mobile devices is illustrated. The system 200 provides " communication for multiple cells, such as for example, macrocells 202A ¨
2020, with each cell being serviced by a corresponding access point 204A ¨ 2040. As described previously, for instance, the access points 204A ¨ 204G related to the macrocells 202A
= ¨ 2020 can be base stations. Mobile devices 206A ¨ 2061 are shown dispersed at various locations throughout the wireless communication system 200. Each mobile device 206A ¨ 2061 can communicate with one or more access points 204A ¨ 204G
on a forward link and/or a reverse link, as described. In addition, access points 208A ¨ 2080 are shown. These can be smaller scale access points, such as femtocells, offering services related to a particular service location, as described. The mobile devices 206A
¨ 2061 can additionally or alternatively communicate with these smaller scale access points 208A ¨ 208C to receive offered services. The wireless communication system 200 can provide service over a large geographic region, in one example (e.g., macrocells 202A ¨ 202G can cover a few blocks in a neighborhood, and the femtocell access points . 208A ¨ 2080 can be present in areas such as residences, office buildings, and/or the like as described). In an example, the mobile devices 206A ¨ 2061 can establish connection with the access points 204A ¨ 204G and/or 208A ¨ 208C over the air and/or over a backhaul connection.
[0079] Additionally, as shown, the mobile devices 206A ¨ 2061 can travel throughout the system 200 and can reselect cells related to the various access points 204A ¨ 2040 and/or 208A ¨ 2080 as it moves through the different macrocells 202A ¨ 2020 or femtocell coverage areas. In one example, the one or more of the mobile devices 206A
¨ 2061 can be associated with a home femtocell related to at least one of femtocell access points 208A ¨ 2080. For example, mobile device 2061 can be associated with femtocell access point 208B as its home femtocell. Thus, though mobile device 2061 is in macrocell 202B, and thus in coverage area of access point 204B, it can communicate with the femtocell access point 208B instead of (or in addition to) access point 204B. In one example, the femtocell access point 208B can provide additional services to the mobile device 2061, such as desirable billing or charges, minute usage, enhanced services (e.g., faster broadband access, media services, etc.).
10080] For example, mobile device 2060 can be associated with femtocell access point 208C. As the mobile device 206D moves from maerocell 202C into 2020 and closer to access points 204D and/or 208C, it can begin the cell rmelection process, as described herein. This can include, for example, measuring surrounding cell parameters (e.g., related to access points 204C, 204D, and 208C) to determine a desirable connection.
The parameters can relate to, for example, signal quality, connection throughput, services offered, a service provider related to the access point, and/or the like. The mobile device 206D can additionally determine whether an identifier of the access point, or a related group identifier, is present in a blacklist of unsuitable access points and/or a whitelist of suitable access points, as described. In one example, this can occur before cell measurement such that cells in the blacklist need not be measured, and if at least one of the cells is in the whitelist, only cells in the whitelist need to be measured.
. In one example, the mobile device 206D can consider access points 204C, 204D, and 208C for selection/reselection. Where the access points 204C, 204D, and 208C
are in a whitelist of the mobile device 2060 and/or not in a blacklist of the mobile device 2060, the mobile device 206D can measure parameters for access points 204C, 204D, and 208C and rank the cells to determine whether to perform cell reselection from access point 204C to one of the others if their rank is higher.
[0081] Where one or more of the access points 204C, 204D, and 208C are in a blacklist = of the mobile device 206D, however, the mobile device 2060 can ignore the blacklisted cells during selection/reselection or measurement, in one example, regardless of other parameters related thereto. Similarly, where at least one of the access points 204C, 204D, and 208C is in a whitelist of the mobile device 2060, the mobile device can ignore any of the access points 204C, 2040, and 208C not in the whitelist.
The mobile device 206D can select/reselect at least one of the access points 204C, 2040, and/or 208C that has the most desirable measurements, is not in the blacklist, and is not = 74769-31061)6 . absent from the whitelist where at least one of the other access points 204C, 204D, and/or 208C is present in the whitelist.
[0082] As described, the mobile device 20613 can maintain a local blacklist and/or whitelist according to user interface input, device events, network provisioning, etc. In addition, the mobile device 206D can receive maintenance provisioning from the network (e.g., via access points 204C, 2041), and/or 208C or other access points communicating with the mobile device 206D). The maintenance provisioning can = affect the local blacklists/whitelists and/or global blacklists or whitelists (e.g., lists generated by the network and maintained at the mobile device 20613). Moreover, the mobile device 206D can conform the blacklists/wlaitelists to defined boundaries when adding entries via user specification, network specification, or otherwise, as described in further detail infra.
[0083] Turning to Fig. 3, illustrated is a communications apparatus 300 for employment within a wireless communications environment. The communications apparatus 300 can be a mobile device or a portion thereof, or substantially any communications apparatus that communicates over and/or receives access to a wireless network.
The communications apparatus 300 can include an interface 302 that allows specification of access point list entries from a user or disparate device or component of the communications apparatus 300, an event detector 304 that can determine occurrences that affect list entry maintenance, a network command receiver 306 that can detect network list maintenance control events, a list maintainer 308 that can manage a list of access points, a list entry timer 310 that can remove list entries based at least in part on expiration of one or more timers, and an access point evaluator 312 that can analyze neighboring access points to determine an identifier, operating or communication parameters, and/or the like related to the access points to determine whether to establish subsequent communication therewith.
[0084] In one example, as described, the list maintainer 308 can manages a blacklist of unsuitable access points from which access should not be requested, a whitelist of suitable access points from which access should be requested over other access points regardless or with less emphasis on other communication parameters, and/or the like. In addition, the list maintainer 308 can manage a local list (e.g., a user controlled list or device controlled list that can be respectively managed via the interface 302 or the event detector 304) and/or a global network provisioned list (e.g., an operator controlled list that can be managed based on commands received from a network operator by the network command receiver 306 over the wireless network), as described. The list . maintainer 308 can manage the lists based on access point identifiers, which can include base identifiers of the access points, group association identifiers (e.g., related to groups offering common services, etc.), one or more communication parameters, such as PN
offset, bandclass, radio channel, and/or the like, etc. In one example, the list maintainer 308 can manage a list of access points that can be identified as blacklisted or whitelisted entries in a single list. The list maintainer 308 can manage both local and global lists in this example as well.
[0085] According to an example, the interface 302 can allow user and/or other component specification of list additions, deletions, flushing, or other management tasks. In this regard, the interface 302 can be a user interface (UI), such as a graphical UI (GUI), an application program interface (API), and/or the like. In one example, the list maintainer 308 can manage a blacklist of unsuitable access points, and the interface 302 can allow a user to add access points to the blacklist by explicitly identifying the access point. For example, the interface 302 can prompt the user for addition to the blacklist upon detecting a new access point. Additionally, the interface 302 can allow a user to remove access points from the blacklist by displaying the access points and facilitating selecting one or more for deletion; in one example, the interface 302 can allow searching for access points in the list for deletion, deletion of groups related by one or more communication parameters, and/or the like. Similarly, the interface 302 can allow the user to flush the list. In addition, the interface 302 can allow a user or component to perform similar functionality to a whitelist of suitable access points. For example, the interface 302 can allow a user to add an access point to the whitelist upon entering the cell of the access point, receiving an indication to establish wireless access with the access point, and/or the like. Moreover, the interface 302 can allow permanent list additions, for example where the list maintainer 308 is limited in list entries. The interface 302, in one example, can also allow manual scans of neighboring access points, causing the access point evaluator 312 to detect one or more neighboring access points and provide a list of resulting neighboring access points for display on the interface 302.
[00861 In another example, the event detector 304 can perform list operations (e.g., add/remove entries, flush the list, etc.) based at least in part on certain events. For example, as described, the event detector 304 can determine one or more failed access attempts related to an access point and can automatically add the access point to the blacklist via the list maintainer 308 (e.g., by requesting addition or otherwise) after a threshold number of request failures or denials. In yet another example, the event detector 304 can determine a current or previous access point that provides desirable wireless access to the communications apparatus 300 and can accordingly add the access point to the whitelist managed by the list maintainer 308. The determination of desirable access can be based on a number of access requests via the interface 302, a determined level of service, throughput or other functionality, a measured time of access point utilization by the communications apparatus 300, a number of requests or data transferred between the communications apparatus 300 and/or the access point, packet error rate (PER), such as when using voice over intemet protocol (VOIP), etc.
[0087] In one example, the event detector 304 can determine a change in operating parameters by the access point. For example, the access point can advertise an identifier along with other parameters. The list maintainer 308, or other component, can store the parameters, and the event detector 304 can compare parameters upon communicating with the access point with those stored. Where the parameters have changed, in one example, the event detector 304 can utilize the list maintainer to remove the access point from the blacklist and/or whitelist so the communications apparatus 300 can determine whether to re-add the access point based on the modified parameters.
Similarly, the event detector 304 can detect modification in access point authorization credentials (e.g, and/or the access point evaluator 312 can determine changing parameters upon detecting a neighboring access point). In this case, the event detector 304 can remove the access point from the blacklist or whitelist, if present; this allows the communications apparatus 300 to try selecting/reselecting (or camping on) the access point before determining whether to re-add it to the blacklist or whitelist. In another example, the event can be caused by a user on the communications apparatus 300, such as dialing a number to indicate list operation (e.g., dial *229 to flush the list).
[00881 Moreover, in an example, the network command receiver 306 can determine network commands related to list management. In one example, the network command receiver 306 can receive a global blacklist or whitelist of access points from a network component (via an access point, other communications apparatus, or otherwise).

Similarly, the network command receiver 306 can receive a list related to the . . 74769-3106D6 =
=

communications apparatus 300 specifically (and/or a group to which the communications apparatus belongs). Further, the network command receiver 306 can receive commands related to managing local and/or global lists, such as commands to add/remove certain access point or related group entries, commands to flush the lists, and/or the like.
0089] In one example, the network command receiver 306 can receive the commands . based at least in part on a previous request for network list information;
it is to be appreciated that the commands can be received without query as well, however.
Additionally, the network command receiver 306 can receive a notification of access point operating parameter or authorization credential change and can accordingly remove the access point from the blacklist or whitelist, as described previously with respect to the event detector 304, for example. Moreover, the network command receiver 306 can receive the commands over the air (OTA), via short message service ' (SMS) message from the network, using a backhaul link, and/or the like. In addition, the command can be to add a preferred user zone list (PUZL) or preferred roaming list (PRL) entry corresponding to the access point ¨ this allows the communications apparatus 300 to prefer the access point similarly to whitelisting, as described herein, on an individual access point basis. In one example, the whitelist and/or related entries can be stored in a PUZL database. In addition, this mechanism can be used to supersede blacklist entries since PUZL can take precedent over the lists manages by the list maintainer 308. Where PUZL is utilized, it is to be appreciated that the list maintainer 308 can additionally manage a list of additional parameters not stored in the PUZL, for example.
[0090] The list maintainer 308, in one example, can manage local and/or global whitelists and/or blacklists, as described. The lists can respectively relate to a user controlled list and/or an operator controlled list, as described above. The list maintainer . 308 can manage the lists using access point identifiers, which can be received over the air by the various access points, in one example. Additionally or alternatively, the list maintainer 308 can utilize a group identifier advertised by a given access point that indicates a commonality between the access point and other access points (e.g., a common service provider, architecture, communication protocol(s), bandwidth, and/or the like). In addition, the list maintainer 308 can manage the list based on communication parameters, such as a PN offset, bandclass, radio channel, and/or the =

like related to one or more access points. In this regard, the list maintainer 308 can allow additions and/or deletions to the list using the proper indicator.
[0091] In addition, the list maintainer 308 can process add/remove requests with respect to the blacklist(s) and/or whitelist(s) received from the interface 302, event detector 304, and/or network command receiver 306, as described. In addition, the list maintainer 308 can flush the list based on events or commands received at the interface 302, event detector 304, and/or network command receiver 306. The list maintainer 308 can also respond to requests from other components of the communications apparatus 300, such . as access point evaluator 312, to determine whether certain access points being measured for selection/reselection are present in the blacklist(s) and/or whitelist(s). It is to be appreciated that where the list maintainer 308 manages local and global lists, conflicts can occur (e.g., a local whitelist may have a common entry with the global blacklist). In this case, the list maintainer 308 can determine which list takes precedent - this can be based on network or communication apparatus 300 specification, list entry update time for the access point, etc. In addition, the list maintainer 308 can perform automated activities; for example, where a whitelist access point is added to the blacklist, the list maintainer 308 can automatically delete the access point from the whitelist, prompt via the interface 302 for a resolution, query the underlying wireless network for resolution, and/or the like.
[00921 Also, the list maintainer 308 can enforce rules for processing additions, deletions etc. In one example, the lists can have maximum sizes such that the list maintainer 308 can insert entries into the list and expunge some list entries to make room for new entries where necessary (e.g., in view of the maximum size). In one example, the list maintainer 308 can use first-in-first-out (FIFO) to remove latest entries in favor of new entries. Thus, where an access point entry is the oldest or otherwise last entry in the list, it can be deleted upon the list maintainer 308 inserting a new access point.
In another example, the list maintainer 308 can maintain a histogram of encountered black list access points and can remove list entries that are oldest and have a lowest number of . encounters, in favor of new entries. In one example, the following formula can be utilized to compute a metric for given list entries to select for removal.
NE
(K + (Ta.

= 74769-3106D6 where NE is the number of number of encounters of the blacklisted access point, K is a positive constant, T is the current time, T, is the last time of encounter by the communications apparatus 300, an a is selectable tuning variable to .achieve desirable = results.
[0093] Also, the list maintainer 308 can utilize PUZL formatting and/or a PUZL
in the communications apparatus 300 to provide the list functionality. For example, the list maintainer 308 can assume all access points are blacklisted unless in the PUZL
(in which case they are whitelisted). Using this functionality, in one example, the list maintainer 308 can manage the PUZL according to list commands received (e.g., a command to add to a blacklist can correspond to deleting from the PUZL, removing = from the blacklist can correspond to adding to the PUZL, etc.). In addition, the list maintainer 308, for example, can store the lists in a memory related to the communications apparatus 300, such as on a removable user identity module (R-U11/1), subscriber identity module (SIM), universal integrated circuit (UICC) or similar card.
Thus, in this example, the list information can be related to the card and transferred among wireless devices.
[0094] In an example, the list maintainer 308 can leverage the list entry timer 310 to remove list entries. In this regard, after a period of time, entries can be removed from the blacklist and/or whitelist such that the communications apparatus 300 re-evaluates the access point or group of access points corresponding to the entry. The list entry timer 310 can determine times for removing access point list entries using substantially any timing mechanism. For example, the list entry timer 310 can comprise an expiration timer where each entry has an associated time after which it is removed from . the list. In another example, the list entry timer 310 can comprise a telescopic timer that can be index based. For example, a back off timer can be utilized after expiration of an initial timer where the timer value is based on an index related to a number of times the access point is added to the blacklist. In another example, the timer can be based on a number of failed access attempts, as described, such that a back off timer parameter can be multiplied by the number of failed attempts to produce the timer. It is to be appreciated that the list entry timer 710 can escalate the back off timer per failed attempt (or encounter in the previous example), for instance. In addition, it is to be appreciated that the list entry timer 710 can utilize a combination of the above timers as well.

= 74769-3106D6 =
[0095] According to an example, the list maintainer 308 can manage and provide virtual lists. For example, the list maintainer 308 can consider substantially all femtocell access points analyzed by the access point evaluator 312 as blacklist entries unless they are in an associated whitelist or PUZL. Thus, the list maintainer 308, in this example, . can provide a blacklist (e.g., to the interface 302) based on generating a list of neighboring femtocell access points and removing those access points already in the associated whitelist or PUZL. In another example, the list maintainer 308 can initially add substantially all femtocells discovered by the access point evaluator 312 to an actual blacklist. In this regard, the access point evaluator 312 can additionally differentiate between femtocell access points and macrocell access points and can, in one example, implement the foregoing lists and respective management functionality for only = femtocell access points, only macrocell access points, a combination, and/or the like.
[0096] In this example, the access point evaluator 312 can, for example, collect geographic information related to discovered access points to filter out access points that are not in preferred geo-locations, which can be indicated by a user via interface 302, in one example. The access point evaluator 312 can deliver identifiers related to the access points (e.g., base access point identifiers, group identifiers, communication parameters, and/or the like, as described) to the interface upon receiving a request for a current list of neighboring access points. The access point evaluator 312 can filter access points that do not match desired geo-location parameters out of the list. The interface 302 can allow selection of an access point from list for which to establish wireless communications. In one example, the interface 302 can additionally add the access point to a blacklist or whitelist by explicit indication and/or implicitly based on selecting the access point for communication establishment It is to be appreciated that the access point evaluator can establish connection to one or more access points based on analyzing the blacklist(s) and/or whitelist(s), in one example.
[0097] Now referring to Fig. 4, illustrated is a wireless communications system 400 that facilitates wireless device access point list management. Wireless device 402 can be a mobile device (including not only independently powered devices, but also modems, for example), a base station, and/or portion thereof, or substantially any wireless device.
The network device 404 can be substantially any core network component that communicates with and provides wireless access to the wireless device 402 via substantially any communications medium (e.g., wired or wireless connection, via base station or other access point, etc.). Moreover, system 400 can be a MEMO
system and/or can conform to one or more wireless network system specifications (e.g., EV-DO, 3GPP, 3GPP2, 3GPP LTE, WiMAX, etc.) and can comprise additional components to facilitate communication between wireless device 402 and network device 404 as well as providing network access to the wireless device 402.
[0098] The wireless device 402 can comprise a network command analyzer 406 that can receive and evaluate network list provisioning commands, as described, a list maintainer 408 that can maintain local and/or global blacklist(s) and/or whitelist(s) related to discovered access points (e.g., user and/or operator controlled lists), and an access point evaluator 410 that can discover one or more access points and associated communication parameters. The network device 404 comprises a list generator 412 that can create a global blacklist and/or whitelist of access points related to the network device 404 (e.g., an underlying service provider of the network device 404) or the wireless device 402 (e.g., based on a type or service provider of the wireless device 402), a parameter change evaluator 414 that can detect modification in communication or operating parameters of an access point (not shown), and a network command provisioner 416 that can generate and transmit network commands related to maintaining the local and/or global whitelist(s) and/or blacklist(s).
[00991 According to an example, the list maintainer 408 can manage local and/or global whitelist(s) and/or blacklist(s). Management can occur, as described, via a provided interface, local event processing, network command processing, and/or the like. The list maintainer 408 can acquire a list or create a list with no initial entries. In addition, as described, the list maintainer 408 can place access points, which the access point evaluator 410 initially discovers, in a blacklist allowing subsequent removal and/or specification in a whitelist. Thus, as the wireless device 402 travels over a wireless network coverage area, the access point evaluator 410 can discover access points and provide related information to the list maintainer 408 for list processing, as described above. In another example, the list maintainer 408 can receive one or more list and/or list management commands from the network device 404.
[0100] For example, the list generator 412 can generate access point lists related to a service provider associated with the network device 404, loading of different access points related to the wireless device 402, a service provider associated with the wireless device 402, a type or capability of the wireless device 402, a subscription related to the . 74769-3106D6 =

wireless device 402, a user of the wireless device 402, and/or the like. In addition, the list can identify the access points using one or more different identifiers, such as an explicit access point identifier advertised by the access point, a group identifier related to a set of access points having common parameters or features, a communication parameter (e.g., PN offset, bandelass, radio channel, etc.) and/or the like.
In this regard, the list generator 412 can create and manage lists for provisioning to wireless devices.
The lists can be provisioned to the wireless device 402, for example, using the network command provisioner 416. In one example, the provisioning of initial local and/or global blacklist(s)/whitelist(s) can be performed upon communication establishment from the wireless device 402 or substantially any network or device event. The network =
command analyzer 406 can receive and accordingly store the list(s) for local management, as described herein.
[01011 Thus, whether obtained from a network device 404 or locally created, as described herein, the list maintainer 408 can store lists and manage list operations such . that the wireless device 402 can obtain a current list when evaluating access points for initial selection or reselection. Once lists are provisioned and/or created, the network device 404 can also provision list updates (e.g., additions, removals, flushes, etc.) as well. For example, the parameter change evaluator 414 can detect modification to one or more parameters related to an access point in one or more lists managed by the list generator 412. The parameters, for example, can relate to PN offset, bandclass, group association, authorization credentials, added or removed functionality, bandwidth, service provider compatibility, and/or the like. The network command provisioner 416 can generate a network command update to the wireless device 402 based on the parameters. The network command analyzer 406 can receive the update and determine the parameter modification. Based on the modification, the network command analyzer 406 can forward the modification information to the list maintainer 408 for local updating of the list. In another example, the modification can cause the list maintainer 408 to remove or add the access point to a managed whitelist and/or blacklist.
For example, where the modification is a change in authorization credentials, and the access point is in a blacklist, the list maintainer 408 can remove the access point from the blacklist causing the access point evaluator 410 to detect the access point when in range such that the wireless device 402 can reattempt connection with the modified parameters. It is to be appreciated, however, that the access point can be re-added to the = 74769-3106D6 blacklist, for example, where reattempted access fails regardless of the modified parameters. It is to be appreciated that the network command provisioner 416 can also determine appropriate list action based on the modification and can transmit a list action = command to the wireless device 402.
[0102] In one example, the network command provisioner 416 can also generate and transmit commands to the wireless device 402 related to setting maximum list sizes and/or list removal instructions, as described above. Additionally, the network command provisioner 416 can transmit commands to the wireless device 402, and the network command analyzer 406 can receive the commands, using SMS
functionality, via a base station, over a backhaul link, and/or the like. In addition, provisions can be PUZL list entry commands. Thus, in one example, the parameter change evaluator can determine a modification to one or more parameters related to an access point The network command provisioner 416 can accordingly generate an SMS message = comprising a command to add the access point to a whitelist (e.g., a PUZL
addition command) or remove from a blacklist, in one example. The network command provisioner 416 can subsequently transmit the SMS to the wireless device 402.
The network command analyzer 406 can receive the SMS message, and the list maintainer 408 can perform the action indicated in the message.
[0103] For example, where the command is a whitelist addition, the list maintainer 408 can add the access point to a whitelist or PUZL in view of the parameter modification to attempt wireless access to the access point upon a subsequent discovery of the access point by the access point evaluator 410. In one example, the list maintainer 408 can determine network provisioned PUZL entries supersede locally housed lists and can = additionally remove the access point from a blacklist, if present, when receiving a PUZL
entry command, as described. In another example, the network command provisioner 416 can indicate the actual update in the SMS message, in which case the network command analyzer 406 can determine an action based on the SMS message (e.g., modify parameters of the local list to match the update, add the access point or related group identifier to a whitelist, remove the access point or related group identifier from a blacklist, etc.). The list maintainer 408 can perform the determined action, as described.
[01041 In yet another example, the network command provisioner 416 can generate timed events to the wireless device 402. For example, the network command provisioner 416 can create and transmit an event to flush all lists at a given time in the . 74769-3106D6 =

future. The network command analyzer 406 can receive the message, determine the command, and accordingly instruct the list maintainer 408 to flush the lists at the specified time. The list maintainer 408 can comply with the flush instructions, in one example. It is to be appreciated that the network command provisioner 416 can implement measures to ensure the commands are received by substantially all intended wireless devices, such by repetitive transmission, requiring acknowledgement responses, and/or the like.
[0105] Turning now to Fig. 5, example user interfaces 500 and 502 are shown that can be utilized to provide access point list management at a mobile device, as described herein. Interface 500, for example, shows a list of blacklisted access points 504; an access point identifier is shown, but other identifiers can be used as well, such as a group association identifier, communications parameters or metrics, and/or the like, as described. The access points can have been blacklisted by a user via the interface, by the device based on network command and/or events as described, and/or the like, for example. As shown, the interface 500 can allow selection of access points in the list 504. The interface 500 also provides a remove button 506 to facilitate removal of one or more selected access points in the list 504. Additionally, a flush button 508 is shown to allow flushing the entire list It is to be appreciated that many other functionalities can be provided by interfaces, such as obtaining further information regarding the access points, setting a timer for access point removal from the blacklist, marking a blacklist entry as permanent, and/or the like; the interface 500 shown is but one example.
[0106] Interface 502 shows a list of in-range access points 510. The list 510 can be displayed in response to engaging a scan button 514, in one example. Again, the list 510 is selectable, and an add button 512 is provided to add a selected access point from the list 510 to a blacldist. It is to be appreciated that similar interfaces can be provided for a whitelist; in fact, the interface 502 can have both whitelist and blacklist add buttons. These interfaces 500 and 502 are but one of substantially limitless possible interfaces and are presented herein as examples. In addition, the layout of the example interfaces 500 and 502 are but one of substantially limitless layouts that can be utilized.
Also, it is to be appreciated that substantially any available interface technology or framework can be utilized to develop and render the interface to a mobile device.

. .
[0107] Referring to Figs. 6-9, methodologies relating to locally managing blacklist and/or whitelists for wireless devices are illustrated. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with one or more aspects, occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with one or more aspects.
[01081 Turning to Fig. 6, an example methodology 600 that facilitates utilizing a blacklist in evaluating cells for initial selection and/or reselection is displayed. At 602, an access point advertising an identifier is detected. As described, the identifier can be = related to a base identifier of the access point, a group association identifier, one or more communication parameters, and/or the like; further, the identifier can be utilized to differentiate macrocell from femtocell access points, in one example. At 604, the identifier can be compared to a list of identifiers related to unsuitable access points. The list can be locally or globally maintained and/or specified, as described.
Furthermore, the functionality can be similarly implemented for a whitelist of suitable access points.
At 606, it can be determined whether to establish communication with the access point based on the comparison. For example, if the access point is in the list of unsuitable access points, communication should not be established. At 608, one or more disparate access points can be scanned based at least in part on identifying the access point in the list of unsuitable access points. Thus, the blacklisted access point is ignored, as described.
[0109] Referring to Fig. 7, an example methodology 700 is shown that facilitates allowing blacklist and/or whitelist manipulation through a provided interface.
At 702, a list of in-range access points is provided to an interface. The list can be obtained, for example, by scanning for the access points and recording a base identifier, group association identifier, communication parameters, and/or the like as advertised by the access point. In addition, the interface can be a GUI, API, and/or the like.
At 704, a list = management command can be received from the interface. The command can relate to, for example, adding or removing access points from the list, flushing the list, retrieving . 74769-3106D6 =

access point parameters, and/or the like. At 706, the list can be modified to reflect the = list management command. Thus, upon subsequent request for the list by an interface or for selecting/reselecting access points in the wireless network, an updated list can be retrieved and provided.
[01101 Turning to Fig. 8, illustrated is an example methodology 800 that facilitates network provisioning of list updates to one or more mobile devices. At 802, a list of access points can be generated. The list can correspond to a blacklist or whitelist according to network specification, specific to a wireless network provider, specific to a subscriber or device, and/or the like. In one example, the list can be retrieved from a database that stores the list for a given mobile device. At 804, the list can be transmitted to one or more mobile devices for local management thereof. Thus, the mobile device can retain a copy of the list and receive provisioned updates to ensure its copy reflects network specific information.
[0111] At 806, a modification in an operating parameter of an access point in the list can be detected, and at 808, a list update command can be transmitted to the one or more mobile devices. Thus, for example, if the access point was in a blacklist and changed an operating parameter, a list update indicating the change can be transmitted to the mobile device indicating to remove the access point from the blacklist.
In this regard, the mobile device can attempt connection to the access point in view of the modified parameter. In another example, the modified parameter can be transmitted to the mobile device to allow the device to determine whether to reattempt access in view . of the modified parameter.
[0112] Fig. 9 illustrates an example methodology that facilitates maintaining multiple access point lists. At 902, an operator controlled list of access points can be maintained.
As described, this can relate to a list of access points for which updates are received from a wireless network and accordingly processed. In addition, the list can be a blacklist or whitelist, as described, and/or a general list with blacklist/whitelist identifiers. At 904, a user controlled list of access points can be maintained as well.
This can relate to a list of access points that can be updated using a provided interface (e.g., GUI, API, and/or the like), as described. Similarly, this list can be a blacklist, whitelist, etc. At 906, an access point for providing wireless network access can be determined based on the user and/or operator controlled lists. Thus, where at least one of the lists is a black list, access points in the blacklist will not be considered for =

requesting wireless network access. Similarly, where at least one of the lists is a whitelist, the access point can be considered for access. It is to be appreciated that list conflicts can exist between the user and operator controlled lists, and mechanisms can be defined to handle such conflicts, as described. At 908, access to the wireless network can be requested from the determined access point.
[0113] It will be appreciated that, in accordance with one or more aspects described herein, inferences can be made regarding updating blacklists and/or whitelists according to interface command, detected events, network provisioning, and/or the like.
As used herein, the term to "infer" or "inference" refers generally to the process of reasoning = about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for = example. The inference can be probabilistic¨that is, the computation of a probability distribution over states of interest based on a consideration of data and events.
Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
= [0114] Fig. 10 is an illustration of a mobile device 1000 that facilitates maintaining a blacklist and/or whitelist related to access points in a wireless network.
Mobile device 1000 comprises a receiver 1002 that receives one or more signals over one or more carriers from, for instance, a receive antenna (not shown), performs typical actions on (e.g., filters, amplifies, downconverts, etc.) the received signals, and digitizes the conditioned signals to obtain samples. Receiver 1002 can comprise a demodulator 1004 that can demodulate received symbols and provide them to a processor 1006 for channel estimation. Processor 1006 can be a processor dedicated to analyzing information received by receiver 1002 and/or generating information for transmission by a transmitter 1018, a processor that controls one or more components of mobile device = 1000, and/or a processor that both analyzes information received by receiver 1002, generates information for transmission by transmitter 1018, and controls one or more components of mobile device 1000.

. 74769-3106D6 [01151 Mobile device 1000 can additionally comprise memory 1008 that is operatively coupled to processor 1006 and that can store data to be transmitted, received data, information related to available channels, data associated with analyzed signal and/or interference strength, information related to an assigned channel, power, rate, or the like, and any other suitable information for estimating a channel and communicating via the channel. Memory 1008 can additionally store protocols and/or algorithms associated with estimating and/or utilizing a channel (e.g., performance based, capacity based, etc.).
= [01161 It will be appreciated that the data store (e.g., memory 1008) described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of illustration, and not limitation, nonvolatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable PROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM
= (DRRAM). The memory 1008 of the subject systems and methods is intended to comprise, without being limited to, these and any other suitable types of memory.
[01171 Processor 1006 can further be operatively coupled to an interface 1010 that allows specification of commands related to managing a blacklist or whitelist of access points, as described herein, a list maintainer 1012 that manages such lists, and an access point evaluator 1014 that can establish communication with an access points based at least in part on the list(s). In one example, the interface 1010 can list available access points and can allow selection and/or specification of access points to a blacklist and/or whitelist. In addition, the interface 1010 can allow scanning for access points, marking one or more access points as a permanent list entry, and/or the like, as described. In addition, the list maintainer 1012 can process requests from the interface 1010 as well as event driven and network provisioned list management, as described. The access point evaluator 1014 can initially select and/or reselect an access point or related cell for . wireless network communication based at least in part on whether the access point is in one or more of the lists. For example, where the access point is in the black list, the access point evaluator 1014 can attempt to locate another access point for providing wireless network access. Mobile device 1000 still further comprises a modulator 1016 and transmitter 1018 that respectively modulate and transmit signals to, for instance, a base station, another mobile device, etc. Although depicted as being separate from the processor 1006, it is to be appreciated that the interface 1010, list maintainer 1012, access point evaluator 1014, demodulator 1004, and/or modulator 1016 can be part of . the processor 1006 or multiple processors (not shown).
=
[0118] Fig. 11 shows an example wireless communication system 1100. The wireless communication system 1100 depicts one base station 1110 and one mobile device for sake of brevity. However, it is to be appreciated that system 1100 can include more than one base station and/or more than one mobile device, wherein additional base stations and/or mobile devices can be substantially similar or different from example base station 1110 and mobile device 1150 described below. In addition, it is to be = appreciated that base station 1110 and/or mobile device 1150 can employ the systems (Figs. 1-4 and 10), interfaces (Fig. 5) and/or methods (Figs. 6-9) described herein to facilitate wireless communication there between.
[0119] At base station 1110, traffic data for a number of data streams is provided from a data source 1112 to a transmit (TX) data processor 1114. According to an example, each data stream can be transmitted over a respective antenna. TX data processor 1114 formats, codes, and interleaves the traffic data stream based on a particular coding scheme selected for that data stream to provide coded data.
[0120] The coded data for each data stream can be multiplexed with pilot data using orthogonal frequency division multiplexing (OFDM) techniques. Additionally or = alternatively, the pilot symbols can be frequency division multiplexed (FDM), time division multiplexed (TDM), or code division multiplexed (CDM). The pilot data is typically a known data pattern that is processed in a known manner and can be used at mobile device 1150 to estimate channel response. The multiplexed pilot and coded data for each data stream can be modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), etc.) selected for that data stream to provide modulation symbols.
The data rate, coding, and modulation for each data stream can be determined by instructions performed or provided by processor 1130.

. 74769-3106D6 =
[0121] The modulation symbols for the data streams can be provided to a TX
MIMO
processor 1120, which can further process the modulation symbols (e.g., for OFDM).
TX MIMO processor 1120 then provides NT modulation symbol streams to NT
transmitters (TMTR) 1122a through 1122t. In various aspects, TX IVIIMO
processor 1120 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.
[0122] Each transmitter 1122 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MEMO channel. Further, NT modulated signals from transmitters 1122a through 1122t are transmitted from NT antennas 1124a through 1124t, respectively.
[0123] At mobile device 1150, the transmitted modulated signals are received by NR
antennas 1152a through 1152r and the received signal from each antenna 1152 is provided to a respective receiver (RCVR) 1154a through 1154r. Each receiver conditions (e.g., filters, amplifies, and downconverts) a respective signal, digitizes the = conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.
[0124] An RX data processor 1160 can receive and process the NR received symbol streams from NR receivers 1154 based on a particular receiver processing technique to provide NT "detected" symbol streams. RX data processor 1160 can demodulate, deinterleave, and decode each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 1160 is complementary to that =
performed by TX MIMO processor 1120 and TX data processor 1114 at base station 1110.
[0125] A processor 1170 can periodically determine which precoding matrix to utilize as discussed above. Further, processor 1170 can formulate a reverse link message comprising a matrix index portion and a rank value portion.
101261 The reverse link message can comprise various types of information regarding the communication link and/or the received data stream. The reverse link message can be processed by a TX data processor 1138, which also receives traffic data for a number of data streams from a data source 1136, modulated by a modulator 1180, conditioned by transmitters 1154a through 1154r, and transmitted back to base station 1110.

= = 74769-3106D6 [0127] At base station 1110, the modulated signals from mobile device 1150 are received by antennas 1124, conditioned by receivers 1122, demodulated by a demodulator 1140, and processed by a RX data processor 1142 to extract the reverse link message transmitted by mobile device 1150. Further, processor 1130 can process the extracted message to determine which precoding matrix to use for determining the beamforming weights.
[0128] Processors 1130 and 1170 can direct (e.g., control, coordinate, manage, etc.) operation at base station 1110 and mobile device 1150, respectively.
Respective processors 1130 and 1170 can be associated with memory 1132 and 1172 that store program codes and data. Processors 1130 and 1170 can also perform computations to derive frequency and impulse response estimates for the uplink and downlink, respectively.
[0129] It is to be understood that the aspects described herein can be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof For a hardware implementation, the processing units can be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
[0130] When the aspects are implemented in software, firmware, rniddleware or microcode, program code or code segments, they can be stored in a machine-readable medium, such as a storage component. A code segment can represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment can be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. can be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, etc.
[0131] For a software implementation, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes can be stored in memory units and =

= 74769-3106D6 executed by processors. The memory unit can be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.
[0132] With reference to Fig. 12, illustrated is a system 1200 that maintains multiple access point lists for subsequent utilization in selecting/reselecting access points for receiving access to a wireless network. For example, system 1200 can reside at least partially within a base station, mobile device, etc. It is to be appreciated that system 1200 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1200 includes a logical grouping 1202 of electrical components that can act in conjunction. For instance, logical grouping 1202 can include an electrical component for maintaining an operator controlled list of identifiers related to access . points in a wireless network and a user controlled list of identifiers related to access points in the wireless network 1204. For example, the operator controlled list can be managed based on commands received from the wireless network, and the user controlled list can be managed based at least in part on commands specified on a provided user interface, as described. Further, logical grouping 1202 can comprise an electrical component for determining one or more access points for requesting access to the wireless network based on the operator controlled and/or the user controlled list 1206. As described, the lists can relate to blacklists and/or whitelists, and access points can be selected if in the whitelist or ignored if in the blacklist Additionally, system 1200 can include a memory 1208 that retains instructions for executing functions associated with electrical components 1204 and 1206. While shown as being external to memory 1208, it is to be understood that one or more of electrical components 1204 and 1206 can exist within memory 1208.
[0133] With reference to Fig. 13, illustrated is a system 1300 that maintains a local blacklist through network provisioning for subsequent utilization in selecting/reselecting access points for receiving access to a wireless network. For example, system 1300 can reside at least partially within a base station, mobile device, etc. It is to be appreciated that system 1300 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1300 includes a logical grouping 1302 of electrical = components that can act in conjunction. For instance, logical grouping 1302 can =

include an electrical component for maintaining a blacklist of access points unsuitable = for providing access to a wireless network 1304. For example, as described, the access points in the list can be identified using a base identifier, group identifier, communication parameter, etc. to allow granular specification of access points for which connection is not desired. Thus, in addition, the blacklist can be consulted in subsequent access point selection/reselection to determine whether one or more access points considered are in the blacklist Further, logical grouping 1302 can comprise an electrical component for modifying the blacklist according to an update command received from the wireless network 1306.
[0134] As described, the blacklist can be updated and/or specified by the wireless network, and the system 1300 can keep a local copy for use in evaluating access points for subsequent communication establishment. Furthermore, logical grouping 1302 can =
include an electrical component for analyzing the blacklist in requesting wireless network access from one or more access points 1308. In addition, logical grouping 1302 can include an electrical component for receiving a user request to update the blacklist 1310. Thus, blacklist updates can be generated not only at the wireless network, but also on the system 1300 by user specification, for example.
Additionally, system 1300 can include a memory 1312 that retains instructions for executing functions associated with electrical components 1304, 1306, 1308, and 1310.
While shown as being external to memory 1312, it is to be understood that one or more of electrical components 1304, 1306, 1308, and 1310 can exist within memory 1312.
= [0135] With reference to Fig. 14, illustrated is a system 1400 for provisioning blacklist updates to a mobile device over a wireless network. For example, system 1400 can reside at least partially within a wireless network component. It is to be appreciated that system 1400 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1400 includes a logical grouping 1402 of electrical components that can act in conjunction. For instance, logical grouping 1402 can = include an electrical component for receiving a parameter modification related to an access point in a wireless network 1404. The modification, for example, can correspond to authorization credentials of an access point, changes in support protocols, supported services, supported network providers, supported devices, and/or the like.
Further, .
logical grouping 1402 can comprise an electrical component for provisioning a network =

. 74769-3106D6 command to update a local blacklist to one or more mobile devices in the wireless network based on the parameter modification 1406. Thus, the mobile devices that may have blacklisted that access point can be required to delete the access point from their blacklist to reattempt connection in view of the new parameters. Moreover, logical grouping 1402 can also comprise an electrical component for creating the local blacklist 1408. Thus, the blacklist can be created by the wireless network and can be based on the mobile device, a subscriber, a network provider, and/or the like.
Furthermore, the electrical component 1406 can also provision the blacklist itself to the mobile devices.
Additionally, system 1400 can include a memory 1410 that retains instructions for executing functions associated with electrical components 1404, 1406, and 1408. While shown as being external to memory 1410, it is to be understood that one or more of electrical components 1404, 1406, and 1408 can exist within memory 1410.
[0136] With reference to Fig. 15, illustrated is a system 1500 that updates a blacklist of access points according to user interface commands. For example, system 1500 can reside at least partially within a base station, mobile device, etc. It is to be appreciated that system 1500 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1500 includes a logical grouping 1502 of electrical components that can act in conjunction. For instance, logical grouping 1502 can include an electrical component for maintaining a blacklist of access points unsuitable for providing access to a wireless network 1504. For example, as described, the access points in the list can be identified using a base identifier, group identifier, communication parameter, etc. to allow granular specification of access points for which connection is not desired. Thus, in addition, the blacklist can be consulted in subsequent access point selection/reselection to determine whether one or more access points considered are in the blacklist. Further, logical grouping 1502 can comprise an electrical component for modifying the blacklist according to an update command received from a provided user interface 1506.
10137] As described, the blacklist can be updated according to user specification using a GUI. In this regard, for example, blacklist entries can be added, deleted, marked as permanent, etc. using the interface. Furthermore, logical grouping 1502 can include an electrical component for analyzing the blacklist in requesting wireless network access from one or more access points 1508. Additionally, system 1500 can include a memory = = 74769-3106D6 1510 that retains instructions for executing functions associated with electrical components 1504, 1506, and 1508. While shown as being external to memory 1510, it is to be understood that one or more of electrical components 1504, 1506, and 1508 can exist within memory 1510.
[0138] With reference to Fig. 16, illustrated is a system 1600 for receiving whitelist . updates from a provided user interface. For example, system 1600 can reside at least partially within a wireless network component. It is to be appreciated that system 1600 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1600 includes a logical grouping 1602 of electrical components that can act in conjunction. For instance, logical grouping 1602 can include an electrical component for maintaining a whitelist of access points for providing access to a = wireless network 1604. For example, as described, the access points in the list can be identified using a base identifier, group identifier, communication parameter, etc. to allow granular specification of access points for which connection is desired.
Thus, in addition, the whitelist can be consulted in subsequent access point selection/reselection to determine whether one or more access points considered are in the whitelist. Further, logical grouping 1602 can comprise an electrical component for modifying the whitelist according to an update command received from a provided user interface 1606.
[0139] As described, the whitelist can be updated according to user specification using a GUI. In this regard, for example, whitelist entries can be added, deleted, marked as permanent, etc. using the interface. Moreover, logical grouping 1602 can also comprise an electrical component for analyzing the whitelist in requesting wireless network access from one or more access points in the wireless network 1608.
Additionally, system 1600 can include a memory 1610 that retains instructions for executing functions associated with electrical components 1604, 1606, and 1608. While shown as being external to memory 1610, it is to be understood that one or more of electrical components 1604, 1606, and 1608 can exist within memory 1610.
[0140] With reference to Fig. 17, illustrated is a system 1700 that maintains a plurality of lists of access points for utilization in requesting wireless network access. For example, system 1700 can reside at least partially within a base station, mobile device, etc. It is to be appreciated that system 1700 is represented as including functional = blocks, which can be functional blocks that represent functions implemented by a =
= = 74769-3106D6 processor, software, or combination thereof (e.g., firmware). System 1700 includes a logical grouping 1702 of electrical components that can act in conjunction.
For instance, logical grouping 1702 can include an electrical component for maintaining a plurality of lists of access points identifiers, the identifiers are related to a group of access points that provide similar access to a wireless network 1704. For example, as described, the identifiers can be group identifiers where the access points in the group have a commonality, such as common service provider, brand, network type, supported protocols, services offered, price packaging, bandwidth, connection constraints, and/or the like. Further, logical grouping 1702 can comprise an electrical component for analyzing at least one of the lists to detect presence of an identifier of an access point 1706.
[01411 As described, the lists can relate to blacklists and/or whitelists.
Thus, identifying an access point identifier in the list can indicate whether the access point should be ignored or considered during cell selection/reselection, as described.
. Furthermore, logical grouping 1702 can include an electrical component for establishing communication with the access point based on analyzing the at least one list 1708.
Additionally, system 1700 can include a memory 1710 that retains instructions for executing functions associated with electrical components 1704, 1706, and 1708. While shown as being external to memory 1710, it is to be understood that one or more of electrical components 1704, 1706, and 1708 can exist within memory 1710.
[01421 With reference to Fig. 18, illustrated is a system 1800 that facilitates maintaining = a list of access points using communication parameters associated therewith. For example, system 1800 can reside at least partially within a wireless network component.
It is to be appreciated that system 1800 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1800 includes a logical grouping 1802 of . electrical components that can act in conjunction. For instance, logical grouping 1802 can include an electrical component for maintaining a list of access point communication parameters determined from one or more signals received from the access points 1804. For example, as described, the access points in the list can be identified using the associated communication parameters, such as PN
offset, bandclass, radio channels, and/or the like. Further, logical grouping 1802 can comprise an electrical component for determining a communication parameter related to an access = 74769-3106D6 point 1806. This can be similarly determined from a signal transmitted by the access point. Moreover, logical grouping 1802 can also comprise an electrical component for . establishing communication with the access point based at least in part on determining whether the communication parameter is in the list 1808. As described, the list can relate to a blacklist and/or whitelist, and communication can be accordingly established if the communication parameter is in the whitelist, or not established if in the blacklist.
Additionally, system 1800 can include a memory 1810 that retains instructions for executing functions associated with electrical components 1804, 1806, and 1808. While shown as being external to memory 1810, it is to be understood that one or more of - electrical components 1804, 1806, and 1808 can exist within memory 1810.
[0143] With reference to Fig. 19, illustrated is a system 1900 for managing access point lists based on timers. For example, system 1900 can reside at least partially within a wireless network component. It is to be appreciated that system 1900 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware).
System 1900 includes a logical grouping 1902 of electrical components that can act in conjunction. For .instance, logical grouping 1902 can include an electrical component for maintaining a blacklist of access points unsuitable for providing access to a wireless network 1904. For example, as described, the access points in the list can be identified using a base identifier, group identifier, communication parameter, etc. to allow granular specification of access points to which connection is not desired.
Thus, in addition, the blacklist can be consulted in subsequent access point selection/reselection to determine whether one or more access points considered are in the blacklist. Further, logical grouping 1902 can comprise an electrical component for receiving a time duration during which the access point is present in the blacklist 1906.
[0144] As described, time duration can be determined from a timer initialized upon entry of the access point in the blacklist. Moreover, logical grouping 1902 can also comprise an electrical component for determining a deletion time for the access point from the list based at least in part on the time duration 1908. Thus, for example, a = deletion threshold can be compared to the time duration to determine when to delete the access point from the list, as described. Additionally, system 1900 can include a memory 1910 that retains instructions for executing functions associated with electrical components 1904, 1906, and 1908. While shown as being external to memory 1910, it = = 74769-3106D6 is to be understood that one or more of electrical components 1904, 1906, and 1908 can exist within memory 1910.
[0145] The various illustrative logics, logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with 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 device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing = devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Additionally, at least one processor may comprise one or more modules operable to perform one or more of the steps and/or actions described above.
[0146] Further, the steps and/or actions of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A
software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium may be coupled to the processor, such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. Further, in some aspects, the processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a user terminal.
In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. Additionally, in some aspects, the steps and/or actions of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a machine readable medium and/or computer readable medium, which may be incorporated into a computer program product.
= [0147] In one or more aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof If implemented in software, . = . 74769-3106D6 =
= 44 the functions may be stored or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a = computer program from one place to another. A storage medium may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROlq, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection may be termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, . DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (t)VD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[01481 While the foregoing disclosure discusses illustrative aspects and/or embodiments, it should be noted that various changes and modifications could be made herein without departing from the scope of the described aspects and/or embodiments as defined by the appended claims. Furthermore, although elements of the described aspects and/or embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
Additionally, all or a portion of any aspect and/or embodiment may be utilized with all or a portion of any other aspect and/or embodiment, unless stated otherwise. Furthermore, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising"
as "comprising" is interpreted when employed as a transitional word in a claim.
Furthermore, although elements of the described aspects and/or aspects may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or = = 74769-3106D6 embodiment may be utilized with all or a portion of any other aspect and/or embodiment, unless stated otherwise.

Claims

CLAIMS:

1. An apparatus, comprising:
an interface that receives one or more commands to update a user controlled list of identifiers related to access points for providing access to a wireless network;
at least one processor;
a non-transitory computer-readable medium coupled to the interface storing codes that when executed by the processor cause the apparatus to:
manage the user controlled list based at least in part on the one or more commands and based on an update in at least one operating parameter for an access point; and utilize the user controlled list in selecting an access point from which to request access to the wireless network based at least in part on determining an identifier of the access point is not included in the user controlled list.

2. The apparatus of claim 1, wherein the interface receives a command to add an access point to the user controlled list and the processor causes the apparatus to add the access point to the user controlled list.

3. The apparatus of claim 2, wherein the processor causes the apparatus to ignore an unsuitable access point in selecting an access point based at least in part on determining an identifier of the unsuitable access point is not included in the user controlled list.

4. The apparatus of claim 1, wherein the interface displays a prompt to add an access point to the user controlled list based at least in part on the processor encountering the access point.

5. The apparatus of claim 2, wherein the interface further receives a command to remove the access point from the user controlled list and the processor causes the apparatus to remove the access point from the user controlled list.