Facilitation of timed fingerprint mobile device locating

Information

  • Patent Grant
  • 10225816
  • Patent Number
    10,225,816
  • Date Filed
    Friday, June 24, 2016
    8 years ago
  • Date Issued
    Tuesday, March 5, 2019
    5 years ago
Abstract
Downlink signal strength measurements from base stations (BSs) are reported by mobile devices to facilitate mobile device locating. A system receives the signal strength information and determines whether the mobile device is within a selected distance from any of the BSs in response to detecting that signal strength information for one of the BSs is greater than a predefined value. The system determines an area over which to search for the mobile device if the system fails to detect that the signal strength information for any of the BSs is greater than the predefined value. The area over which the search is performed is an intersection of all regions determined by the signal strengths of the BSs.
Description
TECHNICAL FIELD

The subject disclosure relates to wireless communications and, more particularly, to various embodiments that facilitate timed fingerprint mobile device locating.


BACKGROUND

The computational resources expended to perform processing for mobile device locating can be extensive. Further, performing such processing can be time-consuming. Accordingly, real-time applications based on mobile device locating can be limited, and the cost of such applications can be driven up due to the processing required to facilitate such services.


SUMMARY

The following presents a simplified summary of one or more of the embodiments in order to provide a basic understanding of some embodiments of the embodiments. This summary is not an extensive overview of the embodiments described herein. It is intended to neither identify key or critical elements of the embodiments nor delineate any scope particular embodiments of the embodiments or any scope of the claims. Its sole purpose is to present some concepts of the embodiments in a simplified form as a prelude to the more detailed description that is presented later. It will also be appreciated that the detailed description may include additional or alternative embodiments beyond those described in this summary.


In one or more embodiments, a method can include: receiving, by a system including at least one processor, signal strength information for a plurality of base stations (BSs), wherein the signal strength information is measured by a mobile device; determining, by the system, that the mobile device is within a selected distance from at least one of the plurality of BSs in response to detecting that signal strength information, measured by the mobile device, for the at least one of the plurality of BSs satisfies a pre-defined condition; and determining, by the system, an area over which to search for the mobile device, wherein the determining the area is based, at least, on failing to detect that the signal strength information for any of the plurality of BSs, measured by the mobile device, satisfies the pre-defined condition.


In one or more embodiments, a non-transitory computer-readable storage medium can store computer-executable instructions that, in response to execution, cause a system including a processor to perform operations. The operations can include: determining signal strength information for a plurality of BSs, wherein the signal strength information is measured by a mobile device; determining that the mobile device is within a selected distance from at least one of the plurality of BSs in response to detecting that signal strength information, measured by the mobile device, for the at least one of the plurality of BSs satisfies a pre-defined condition; and determining an area over which to search for the mobile device, wherein the determining the area is in response to determining that signal strength information for each of the plurality of BSs, measured by the mobile device, fails to satisfy the pre-defined condition.


In one or more embodiments, a system can include a memory that stores computer-executable instructions, and a processor, communicatively coupled to the memory, that facilitates execution of computer-executable instructions to: receive signal strength information for a plurality of BSs, wherein the signal strength information is measured by a mobile device; and search an area for the mobile device, wherein the area comprises an intersection of regions associated with the plurality of BSs, and wherein the search is performed based, at least, on a determination that the signal strength information for each of the plurality of BSs, measured by the mobile device, fails to satisfy the pre-defined condition.


The following description and the annexed drawings set forth certain illustrative embodiments of the embodiments. These embodiments are indicative, however, of but a few of the various ways in which the principles of the embodiments can be employed. Other features of the embodiments will become apparent from the following detailed description of the embodiments when considered in conjunction with the drawings.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates an example system in which mobile device locating can be facilitated in accordance with embodiments described herein.



FIG. 2 illustrates an example diagram illustrating an intersection region employed by the system of FIG. 1 to facilitate processing for mobile device locating in accordance with embodiments described herein.



FIG. 3 illustrates an example mobile device locating system that facilitates processing for mobile device locating in accordance with embodiments described herein.



FIG. 4 illustrates an example data storage that facilitates processing for mobile device locating in accordance with embodiments described herein.



FIG. 5 illustrates an example search area determination component that facilitates processing for mobile device locating in accordance with embodiments described herein.



FIGS. 6-9 illustrate example flowcharts of methods that facilitate processing for mobile device locating in accordance with embodiments described herein.



FIG. 10 illustrates a block diagram of a computer operable to facilitate processing for mobile device locating.





DETAILED DESCRIPTION

One or more embodiments are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. It is evident, however, that the various embodiments can be practiced without these specific details (and without applying to any particular networked environment or standard).


As used in this application, in some embodiments, the terms “component,” “system” and the like are intended to refer to, or include, a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution. As an 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, computer-executable instructions, a program, and/or a computer. By way of illustration and not limitation, both an application running on a server and the server can be a component. One or more components may 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 via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., 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 via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can include a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components. While various components have been illustrated as separate components, it will be appreciated that multiple components can be implemented as a single component, or a single component can be implemented as multiple components, without departing from example embodiments.


Further, the various embodiments can be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media. For example, computer readable storage media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices (e.g., card, stick, key drive). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.


In addition, the words “example” and “exemplary” are used herein to mean serving as an instance or illustration. Any embodiment or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word example or exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. 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 context to be directed to a singular form.


Moreover, terms such as “user equipment,” “mobile station,” “mobile,” “subscriber station,” “access terminal,” “terminal,” “handset,” “mobile device” (and/or terms representing similar terminology) can refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably herein and with reference to the related drawings. Likewise, the terms “access point (AP),” “BS (or BSs),” “Node B,” “evolved Node B (eNode B),” “home Node B (HNB)” and the like, are utilized interchangeably in the application, and refer to a wireless network component or appliance that transmits and/or receives data, control, voice, video, sound, gaming or substantially any data-stream or signaling-stream from one or more subscriber stations. Data and signaling streams can be packetized or frame-based flows.


Furthermore, the terms “user,” “subscriber,” “customer,” “consumer” and the like are employed interchangeably throughout, unless context warrants particular distinctions among the terms. It should be appreciated that such terms can refer to human entities or automated components supported through artificial intelligence (e.g., a capacity to make inference based, at least, on complex mathematical formalisms), which can provide simulated vision, sound recognition and so forth.


Embodiments described herein can be exploited in substantially any wireless communication technology, including, but not limited to, Wireless Fidelity (Wi-Fi), Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), Enhanced General Packet Radio Service (Enhanced GPRS), Third Generation Partnership Project (3GPP) Long Term Evolution (LTE), Third Generation Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA), Zigbee and other 802.XX wireless technologies and/or legacy telecommunication technologies. Further, the term “femto” and “femtocell” are used interchangeably, and the terms “macro” and “macrocell” are used interchangeably.


Various embodiments described herein relate to a system receiving, signal strength information for a plurality of BSs, wherein the signal strength information is measured by a mobile device. The system also determines that the mobile device is within a selected distance from at least one of the BSs in response to detecting that signal strength information for the BS is greater than a predefined value; and determines an area over which to search to perform locating for the mobile device, wherein the determination of the area is based, at least, on not detecting that signal strength information for any of the BSs is greater than the predefined value.


In some embodiments, determining the area over which to search includes: determining, for the BSs, expected downlink signal powers as functions of a plurality of parameters; employing the signal strength information as proxies for distance between the mobile device and the BSs; determining regions around the BSs based, at least on the signal strength information and locations of the BSs; and determining an intersection region over which the regions overlap one another. The mobile locating system can search within the intersection region for the mobile device, as compared with other approaches that employ searching within the entirety of each geographical region covered by each of the BSs.


One or more of the embodiments can enhance mobile device locating relative to the time and processing required to perform mobile device locating based solely on relative timing between transmitting BSs over large geographic areas.



FIG. 1 illustrates an example system in which mobile device locating can be facilitated in accordance with embodiments described herein. FIG. 2 illustrates an example diagram illustrating an intersection region employed by the system of FIG. 1 to facilitate processing for mobile device locating in accordance with embodiments described herein.


Referring to FIG. 1, the system 100 can include a mobile device 102, BSs 104, 106, 108 configured to transmit signals 110, 112, 114 received by and measured at the mobile device 102, and a mobile device locating system 116. In some embodiments, the signals can be pilot signals including information such as transmission frame timing values, signal-to-noise ratio measurements and/or absolute signal strength measurements.


The BSs 104, 106, 108 cover geographical regions with the signals 110, 112, 114. For example, as shown in FIG. 2, BS 104 can cover the geographical region A, BS 106 can cover the geographical region B and BS 108 can cover the geographical region C. To perform mobile device locating and determine the location of the mobile device 102, the mobile device locating system 116 can perform a number of functions to limit the area over which the mobile device locating system 116 searches for the mobile device 102.


For example, in some embodiments, the mobile device locating system 116 can receive information indicative of the signal strengths of the signals 110, 112, 114 measured by the mobile device 102. The mobile device locating system 116 can determine an intersection region, such as shaded region D shown in FIG. 2, over which to search for the mobile device 102. In some embodiments, the mobile device locating system 116 can locate mobile device 102 via analysis of timing offsets observed and reported by the mobile device 102.


The structure and/or functionality of mobile device locating system 116 can be as described in further detail with reference to FIGS. 3-9 in various embodiments.



FIG. 3 illustrates an example mobile device locating system that facilitates mobile device locating in accordance with embodiments described herein. As shown in FIG. 3, mobile device locating system 300 can include a communication component 302, a BS determination component 304, a search area determination component 306, a memory 308, a processor 310 and/or data storage 312. In some embodiments, one or more of the communication component 302, BS determination component 304, search area determination component 306, memory 308, processor 310 and/or data storage 312 can be electrically and/or communicatively coupled to one another to perform one or more functions of the mobile device locating system 300.


The communication component 302 can transmit and/or receive information to and/or from one or more BSs and/or a mobile device. In some embodiments, the communication component 302 can receive signal strength information from a mobile device. The signal strength information can be information about the signal strength of a downlink pilot signal transmitted by a BS and received at the mobile device.


The BS determination component 304 can determine whether the signal strength information indicates that the mobile device is within a particular distance from the BS for which the mobile device reports the signal strength information. For example, in some embodiments, the signal measured for a particular BS by the mobile device can be greater than a predefined value, indicating that the mobile device is fairly close to the BS. In these embodiments, the BS determination component 304 can determine that the mobile device is within a particular distance to a single BS (e.g., within 1 kilometer from the BS). For example, in some embodiments, if the signal measured by the mobile device is particularly high (or greater than the predefined value), the BS determination component can assume that the mobile device is particularly close to the BS. The BS determination component 304 can identify the BS and, in some embodiments, the distance between the BS and the mobile device. In some embodiments, when the BS determination component 304 determines that the mobile device is within a particular distance to a single BS, the operations of the search area determination component 306 need not be performed.


The search area determination component 306 can define a region around each BS for which the mobile device reports the strength of a downlink pilot signal. The search area determination component 306 can then determine an intersection region over which the different regions for the different BS regions overlap. The search area determination component 306 can be described in greater detail with reference to FIG. 5.


The memory 308 can be a computer-readable storage medium storing computer-executable instructions and/or information for performing the functions described herein with reference to the mobile device locating system 300. Processor 310 can perform one or more of the functions described herein with reference to the mobile device locating system 300.


The data storage 312 can be configured to store information transmitted to, received by and/or processed by the mobile device locating system 300. For example, with reference to FIGS. 3 and 4, the data storage 312, 312′ can store information identifying a BS that is particularly close to the mobile device, measured signal strength information 402, distance information 404, region information 406, intersection region information 408 and/or antenna information 410.



FIG. 5 illustrates an example search area determination component that facilitates mobile device locating in accordance with embodiments described herein. The search area determination component 306′ can include the structure and/or functionality of the search area determination component 306 in some embodiments (and vice versa).


In some embodiments, the search area determination component 306 can include a downlink signal power component 502, distance proxy component 504, a region determination component 506, an intersection region component 508, a search component 510, a memory 512, a processor 514 and/or data storage 312″. One or more of the downlink signal power component 502, distance proxy component 504, region determination component 506, intersection region component 508, search component 510, memory 512, processor 514 and/or data storage 312″ can be electrically and/or communicatively coupled to one another to perform one or more functions of the search area determination component 306′.


The downlink signal power component 502 can determine expected downlink signal powers for the information received from the mobile device about the BS pilot signals. In some embodiments, the downlink signal power component 502 can employ a radio propagation model (e.g., Hata-Okumura radio propagation model) to make such determination. In particular, the downlink signal power component 502 can utilize the frequency of a channel over which the signal strength information is received by the mobile device, distances between the mobile device and the BSs, antenna heights of the BSs, antenna height of the mobile device and/or the morphology (e.g., urban, suburban, rural) of the terrain over which the signals are transmitted to determine expected powers for the BS signals.


Employing the radio propagation model, the downlink signal power component 502 can determine the BS signal path loss versus distance between the BS and the mobile device for each BS for which the mobile device reports measured signal strength information. The downlink signal power component 502 can utilize the BS signal path loss (along with the distance between the mobile device and BS) to determine expected downlink signal powers for the signal measured at the mobile device.


The distance proxy component 504 can determine the distance between the mobile device and a BS for which the mobile device reports the signal strength information. For example, the distance proxy component 504 can determine the distance between the mobile device and a BS by determining a maximum distance between the BSs and the mobile device based on the downlink signal strength for the BSs.


For example, in some embodiments, the distance proxy component 504 can determine the maximum distance between the mobile device and the BS by evaluating the reported measured signal strength at the mobile device and the expected signal power output from the downlink signal power component 502. The actual measured signal strength can be compared to the expected signal power to determine the actual distance between the mobile device and the BS.


In some embodiments, the signal strength measurement from the mobile device can be a proxy for distance from a base station if frequency and antenna heights are known.


The region determination component 506 can determine a region around each BS for which signal strength information is received from the mobile device. The region determination component 506 can determine the region by determining the location of the BS (which can be known in some embodiments) and determining the area covered by the pilot signal from the BS based on the strength of the pilot signal received and measured by the mobile device.


In some embodiments, the regions can be circular regions having the BS at the center of the circle and having a radius dictated by the signal strength reported by the mobile device. For example, the radius can be the maximum distance over which the mobile device can receive the signal from the BS, given the strength of the BS pilot signal.


In some embodiments, the regions determined around the BSs can have boundaries that overlap one another. Accordingly, the intersection region component 508 can determine an overlap area for the regions associated with the different BSs.


The intersection region can be polygonal and any number of different shapes, in various embodiments. In some embodiments, the intersection region can be an irregular polygonal region having a perimeter defined by the intersection of the regions. In some embodiments, the intersection region can be approximated as a rectangular region substantially covering the intersection region. In embodiments wherein the intersection region is approximated as a rectangular region, scanning the intersection region can be performed efficiently and with less computation than embodiments wherein scanning is performed for an irregular polygon.


The search component 510 can search the intersection region for the mobile device to perform mobile device locating. In some embodiments, the search component 510 can scan various regions within the intersection region. By way of example, but not limitation, the intersection region can be divided into a number of bins and the search component 510 can scan one or more of the bins to determine whether the mobile device is located in the bins.


As such, the search area determination component 306′ can reduce an area over which searching is performed to locate the mobile device by determining and searching an intersection region (as compared to searching the entirety of each geographical region covered by each of the BSs for which the mobile device reports a pilot signal strength).


In some embodiments, reducing the search area can drastically reduce computation and conserve resource. For example, a mobile device can report signal strength information from a number of BSs within a 1-2 mile area and a number of BSs many miles away. Searching over a ten mile area, for example, may result in searching for the mobile device by scanning 25,000 100 m square bins for a best signal timing match. If the mobile device reports a high signal strength from one of the BSs, the high signal strength can result in searching a maximum distance of 500 m from the BS for which the high signal strength is reported. As such, scanning can be performed in a much smaller area (e.g., an area including only 100 100 meter square bins). Accordingly, the computational effort to perform the scanning is reduced by 100/25,000 of the original effort (i.e., 99.6% reduction in computation).


In some embodiments, computational effort can be reduced by at least 75% in all morphologies (e.g., urban, suburban and rural morphologies). Conversely for a given set of computational system resources, the system can locate at least four times as many mobile devices as compared to systems that search the entirety of the geographical regions covered by each of the BSs reported by the mobile device.


In addition, location determinations based solely on timing information from the mobile device can have the potential to have occasional large locating errors if the BS to BS relative timing calibration is offset and undetected. However, by bounding the search areas initially based on signal strength (as described with reference to the distance proxy component 504), the error introduced can be partially mitigated.


Further, while the Hata-Okumura radio propagation model was noted above, and assumes path loss associated with urban, suburban or rural morphologies, in some embodiments, atypically low path loss parameters (e.g., parameters that occur across lakes or in conditions called atmospheric super-refraction and atmospheric refractive ducting) can be assumed. These conditions cause high temperature gradients. For example, line of sight path loss can be assumed to a distance between 500 meters and 1000 meters and then the model can migrate gradually to the Hata-Okumura radio propagation model assumptions with increasing distance between the BS and the mobile device. At approximately 15 kilometers from the BS, the model can assume 15% line of sight path loss and 85% Hata-Okumura assumptions. This embodiment still gives a presumptive edge to increasing the bounding search to something perhaps 20% larger in area than would otherwise be implied by Hata-Okumura assumptions exclusively.



FIGS. 6-9 illustrate example flowcharts of methods that facilitate mobile device locating in accordance with embodiments described herein. Turning first to FIG. 6, at 602, method 600 can include receiving signal strength information for the BSs. The signal strength information can be measured by a mobile device. In various embodiments, the signal strength information can include or be BS downlink signal strengths as measured at the mobile device.


At 604, method 600 can include determining, by the system, that the mobile device is within a selected distance from at least one of the BSs in response to detecting that signal strength information, measured by the mobile device, for the BS satisfies a pre-defined condition. For example, a maximum distance can be determined between the BS and the mobile device based on the downlink signal strength for the BS, as measured by the mobile device.


The maximum distance can be the distance over which the mobile device can receive the signal from the BS, given the strength of the BS signal. As such, a weaker signal measured at the mobile device can imply a longer distance between the mobile device while a stronger signal measured at the mobile device can imply a shorter distance between the mobile device and a BS.


In some embodiments, the signal measured for a particular BS by the mobile device can be greater than a predefined value, indicating that the mobile device is fairly close to the BS. In these embodiments, the mobile device can be determined to be within a particular distance to the BS (e.g., within 1 kilometer from the BS) and step 606 need not be performed.


At 606, method 600 can include determining, by the system, an area over which to search for the mobile device. Determining the area can be based on detecting that signal strength information for each of the BSs is not greater than the predefined value. Accordingly, in embodiments wherein none of the measured signals from the BSs have strength greater than a predefined value, an area can be determined for searching for the location of the mobile device.


A method for determining the area over which to search can be performed, in some embodiments, as described with reference to FIG. 7.


Turning now to FIG. 7, at 702, method 700 can include determining, for the plurality of base stations, respective expected downlink signal powers according to a plurality of parameters. In some embodiments, the respective expected downlink signal powers can be determined according to a frequency of a channel over which the signal strength information is received by the mobile device, respective distances between the mobile device and the BSs, respective antenna heights of the BSs, antenna height of the mobile device and/or the general morphology of urban, suburban, rural areas over which the BS signals are transmitted.


In some embodiments, to determine the expected downlink signal powers, a radio propagation model (e.g., Hata-Okumura radio propagation model) can be employed utilizing the frequency of a channel over which the signal strength information is received by the mobile device, distances between the mobile device and the plurality of base stations, antenna heights of the BSs and/or an antenna height of the mobile device. Employing the radio propagation model, BS signal path loss versus distance between the BS and the mobile device can be determined. The BS signal path loss can be employed (along with the distance between the mobile device and BS) to determine expected downlink signal powers for the signal measured at the mobile device.


At 704, method 700 can include employing respective signal strength information for the BSs as respective proxies for distance between the mobile device and the BSs. In some embodiments, the signal strength information can be a proxy for determining distance by determining a maximum distance between the BSs and the mobile device based on the downlink signal strength for the BSs, as described with reference to 602. In particular, method 800 includes one such method of employing the signal strength information as a proxy for distance.


Turning now to FIG. 8, at 802, method 800 can include determining signal strength of a BS measured at a mobile device. At 804, method 800 can include determining a maximum distance between the BS and the mobile device based, at least, on the signal strength measured at the mobile device.


Turning back to FIG. 7, at 706, method 700 can include determining respective regions around the BSs based, at least on the signal strength information for the BSs and respective locations of the BSs. In some embodiments, the regions can be circular regions.


The locations of the BSs can be known in some embodiments. Each region can include the BS at an approximate center of the region, in some embodiments. For example, the regions can be circular regions having the BS at the center of the circle and having a radius dictated by the signal strength measured by the mobile device. For example, the radius can be the maximum distance between the BS and the mobile device as described with reference to 704.


At 708, method 700 can include determining an intersection region over which the regions overlap one another. In some embodiments, the regions determined around the BSs can have boundaries that overlap one another. As such, the intersection region can be the intersection, or area, over which each of the regions overlap.


At 710, method 700 can include searching for the mobile device within the intersection region. In various embodiments, scanning techniques can be employed to scan the intersection region. In some embodiments, the scanning for the mobile device can be performed using timing measurements provided by the mobile device.


Accordingly, the region over which the scanning is performed is reduced relative to approaches that scan the entirety of each region covered by the BSs (as opposed to merely scanning the intersection region).


The intersection region can be an irregular polygonal region having a perimeter defined by the intersection of the regions. In some embodiments, the intersection region can be approximated as a rectangular region substantially covering the intersection region. Accordingly, in embodiments wherein the intersection region is approximated as a rectangular region, scanning the intersection region can be performed efficiently and with less computation.


Turning now to FIG. 9, at 902, method 900 can include receiving signal strength information for the BSs, wherein the signal strength information is measured by a mobile device.


At 904, method 900 can include determining an area over which to search for the mobile device, wherein the area comprises an intersection of regions associated with the BSs. Accordingly, in some embodiments, as described with reference to FIG. 6, a determination can be made as to whether a mobile device is within a particular distance to a selected BS and, if so, an intersection region need not be scanned. In some embodiments, however, the intersection region is formed and scanned without resort to a determination as to whether the mobile device is within a particular distance to a selected BS.


Referring now to FIG. 10, there is illustrated a block diagram of a computer operable to facilitate antenna location determination. For example, in some embodiments, the computer can be or be included within the mobile device locating system 116, 300.


In order to provide additional context for various embodiments of the embodiments described herein, FIG. 10 and the following discussion are intended to provide a brief, general description of a suitable computing environment 1000 in which the various embodiments of the embodiment described herein can be implemented. While the embodiments have been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that the embodiments can be also implemented in combination with other program modules and/or as a combination of hardware and software.


Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the inventive methods can be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.


The terms “first,” “second,” “third,” and so forth, as used in the claims, unless otherwise clear by context, is for clarity only and doesn't otherwise indicate or imply any order in time. For instance, “a first determination,” “a second determination,” and “a third determination,” does not indicate or imply that the first determination is to be made before the second determination, or vice versa, etc.


The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.


Computing devices typically include a variety of media, which can include computer-readable storage media and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data. Computer-readable storage media can include, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or other tangible and/or non-transitory media which can be used to store desired information. Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.


Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.


With reference again to FIG. 10, the example environment 1000 for implementing various embodiments of the aspects described herein includes a computer 1002, the computer 1002 including a processing unit 1004, a system memory 1006 and a system bus 1008. The system bus 1008 couples system components including, but not limited to, the system memory 1006 to the processing unit 1004. The processing unit 1004 can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit 1004.


The system bus 1008 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 1006 includes ROM 1010 and RAM 1012. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 1002, such as during startup. The RAM 1012 can also include a high-speed RAM such as static RAM for caching data.


The computer 1002 further includes an internal hard disk drive (HDD) 1014 (e.g., EIDE, SATA), which internal hard disk drive 1014 can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) 1016, (e.g., to read from or write to a removable diskette 1018) and an optical disk drive 1020, (e.g., reading a CD-ROM disk 1022 or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive 1014, magnetic disk drive 1016 and optical disk drive 1020 can be connected to the system bus 1008 by a hard disk drive interface 1024, a magnetic disk drive interface 1026 and an optical drive interface 1028, respectively. The interface 1024 for external drive implementations includes at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1094 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.


The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 1002, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to a hard disk drive (HDD), a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, can also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.


A number of program modules can be stored in the drives and RAM 1012, including an operating system 1030, one or more application programs 1032, other program modules 1034 and program data 1036. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 1012. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.


A user can enter commands and information into the computer 1002 through one or more wired/wireless input devices, e.g., a keyboard 1038 and a pointing device, such as a mouse 1040. Other input devices (not shown) can include a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like. These and other input devices are often connected to the processing unit 1004 through an input device interface 1042 that can be coupled to the system bus 1008, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.


A monitor 1044 or other type of display device can be also connected to the system bus 1008 via an interface, such as a video adapter 1046. In addition to the monitor 1044, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.


The computer 1002 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 1048. The remote computer(s) 1048 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer 1002, although, for purposes of brevity, only a memory/storage device 1050 is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN) 1052 and/or larger networks, e.g., a wide area network (WAN) 1054. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.


When used in a LAN networking environment, the computer 1002 can be connected to the local network 1052 through a wired and/or wireless communication network interface or adapter 1056. The adapter 1056 can facilitate wired or wireless communication to the LAN 1052, which can also include a wireless AP disposed thereon for communicating with the wireless adapter 1056.


When used in a WAN networking environment, the computer 1002 can include a modem 1058 or can be connected to a communications server on the WAN 1054 or has other means for establishing communications over the WAN 1054, such as by way of the Internet. The modem 1058, which can be internal or external and a wired or wireless device, can be connected to the system bus 1008 via the input device interface 1042. In a networked environment, program modules depicted relative to the computer 1002 or portions thereof, can be stored in the remote memory/storage device 1050. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.


The computer 1002 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This can include Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.


Wi-Fi can allow connection to the Internet from a couch at home, a bed in a hotel room or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which can use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10BaseT wired Ethernet networks used in many offices.


The embodiments described herein can employ artificial intelligence (AI) to facilitate automating one or more features described herein. The embodiments (e.g., in connection with automatically identifying acquired cell sites that provide a maximum value/benefit after addition to an existing communication network) can employ various AI-based schemes for carrying out various embodiments thereof. Moreover, the classifier can be employed to determine a ranking or priority of the each cell site of the acquired network. A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, . . . , xn), to a confidence that the input belongs to a class, that is, f(x)=confidence(class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to prognose or infer an action that a user desires to be automatically performed. A support vector machine (SVM) is an example of a classifier that can be employed. The SVM operates by finding a hypersurface in the space of possible inputs, which the hypersurface attempts to split the triggering criteria from the non-triggering events. Intuitively, this makes the classification correct for testing data that is near, but not identical to training data. Other directed and undirected model classification approaches include, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed. Classification as used herein also is inclusive of statistical regression that is utilized to develop models of priority.


As will be readily appreciated, one or more of the embodiments can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing UE behavior, operator preferences, historical information, receiving extrinsic information). For example, SVMs can be configured via a learning or training phase within a classifier constructor and feature selection module. Thus, the classifier(s) can be used to automatically learn and perform a number of functions, including but not limited to determining according to a predetermined criteria which of the acquired cell sites will benefit a maximum number of subscribers and/or which of the acquired cell sites will add minimum value to the existing communication network coverage, etc.


As employed herein, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor can also be implemented as a combination of computing processing units.


As used herein, terms such as “data storage,” “data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components or computer-readable storage media, described herein can be either volatile memory or nonvolatile memory or can include both volatile and nonvolatile memory.


Memory disclosed herein can include 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 static 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 (e.g., data storages, databases) of the embodiments are intended to comprise, without being limited to, these and any other suitable types of memory.


What has been described above includes mere examples of various embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these examples, but one of ordinary skill in the art can recognize that many further combinations and permutations of the present embodiments are possible. Accordingly, the embodiments disclosed and/or claimed herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. 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.

Claims
  • 1. A method, comprising: reducing, by a device comprising a processor, an initial search area associated with base station devices to a search area associated with a base station device of the base station devices determined to be associated with signal strength information that satisfies a condition, wherein the signal strength information is obtained from a mobile device measuring a signal strength of signals generated by the base station device;determining, by the device, a distance from an approximate location of the base station device associated with the signal strength information that satisfies the condition, wherein the distance is based on the signal strength information for the base station device, and wherein the condition being satisfied comprises the signal strength information being determined to represent the signal strength that is greater than a defined threshold signal strength;determining, by the device, that the device is within a defined distance to the base station device; andforgoing, by the device, performing scanning of bin regions representing a search area based on the determining that the device is within the defined distance.
  • 2. The method of claim 1, further comprising: performing, by the device, the scanning of the bin regions representing the search area based on a determination that the device fails to be within the defined distance.
  • 3. The method of claim 1, wherein the search area is a polygonal region.
  • 4. The method of claim 1, further comprising: determining, by the device, an intersection region composed of an area over which respective regions around the base station devices overlap.
  • 5. The method of claim 4, further comprising searching, by the device, for the mobile device, wherein the searching is limited to the intersection region.
  • 6. The method of claim 5, further comprising determining, by the device, respective expected downlink signal power information measured at the mobile device according to respective parameters.
  • 7. The method of claim 4, wherein the determining the intersection region comprises approximating a single rectangular region substantially covering the intersection region.
  • 8. The method of claim 4, wherein the determining the intersection region comprises determining an irregular polygonal region.
  • 9. A non-transitory machine-readable storage medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising: based on a mobile device measuring signal strength information for a base station device of base station devices and determining the signal strength information for the base station device satisfies a condition, decreasing an initial search area associated with a group of the base station devices to a search area associated with the base station device having the signal strength information that satisfies the condition;determining a distance from an approximate location of the base station device associated with the signal strength information that satisfies the condition, wherein the distance is based on the signal strength information for the base station device, and wherein the condition being satisfied comprises the signal strength information being greater than a defined threshold signal strength;measuring signal strength information for the base station device of base station devices; andbased on determining that the signal strength for the base station device is higher than a defined value, searching at least a defined distance from only the base station device for which the signal strength for the base station device is higher than the defined value.
  • 10. The non-transitory machine-readable storage medium of claim 9, wherein the operations further comprise: determining respective regions around the base station devices based on the respective signal strength information for the base station devices.
  • 11. The non-transitory machine-readable storage medium of claim 10, wherein the determining respective regions is also based on respective locations of the base station devices.
  • 12. A system, comprising: a processor; anda memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising: reducing an initial search area associated with a base station device of base station devices to a search area associated with the base station device having signal strength information that satisfies a defined condition; anddetermining a distance from an approximate location of the base station device associated with the signal strength information that satisfies the condition, wherein the distance is based on the signal strength information for the base station device and a defined a path loss model, wherein the condition is that the signal strength information is greater than a defined threshold signal strength, wherein the defined path loss model migrates from a line of sight model to a Hata-Okumura radio propagation model with increasing distance between the base station device and the system.
  • 13. The system of claim 12, wherein, at a defined distance between the base station device and the system, the path loss model assumes a first percentage line of sight path loss and a second percentage Hata-Okumura path loss, and the operations further comprise: receiving downlink signal strengths measured at a mobile device, and wherein the downlink signal strengths are employed to determine the signal strength information.
  • 14. The system of claim 12, wherein the operations further comprise searching the area for a mobile device.
  • 15. The system of claim 12, wherein the operations further comprise: performing a first determination, for the base station devices, of respective expected downlink signal powers measured at the mobile device according to parameters; andutilizing the respective signal strength information for the base station devices, measured by the mobile device, as a proxy for respective distances between the mobile device and the base station devices.
  • 16. The system of claim 15, wherein the operations further comprise: performing a second determination of respective regions associated with the base station devices based on the respective signal strength information for the base station devices and respective locations of the base station devices.
  • 17. The system of claim 16, wherein the operations further comprise: performing a third determination of an intersection of the respective regions.
  • 18. The system of claim 17, wherein the performing the third determination of the intersection of the respective regions comprises generating an approximation of a rectangular region at least substantially covering the intersection of the respective regions.
  • 19. The system of claim 17, wherein the performing the third determination of the intersection of the respective regions comprises generating a definition of an irregular polygonal region having a perimeter defined by the intersection of the respective regions.
  • 20. The system of claim 15, wherein the performing the first determination of the respective expected downlink signal powers is made with respect to respective antenna heights of the base station devices and an antenna height of the mobile device.
CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of, and claims priority to, U.S. patent application Ser. No. 13/526,988, filed Jun. 19, 2012, and entitled “FACILITATION OF TIMED FINGERPRINT MOBILE DEVICE LOCATION,” the entirety of which application is hereby incorporated herein by reference.

US Referenced Citations (377)
Number Name Date Kind
4718081 Brenig Jan 1988 A
5515062 Maine et al. May 1996 A
5724660 Kauser et al. Mar 1998 A
5732354 MacDonald Mar 1998 A
5732383 Foladare et al. Mar 1998 A
5831545 Murray et al. Nov 1998 A
5844521 Stephens et al. Dec 1998 A
5982324 Watters et al. Nov 1999 A
6018312 Haworth et al. Jan 2000 A
6026301 Satarasinghe Feb 2000 A
6058260 Brockel et al. May 2000 A
6108532 Matsuda et al. Aug 2000 A
6108556 Ito Aug 2000 A
6125125 Narasimha et al. Sep 2000 A
6148219 Engelbrecht et al. Nov 2000 A
6216002 Holmring Apr 2001 B1
6230018 Watters et al. May 2001 B1
6256577 Graunke Jul 2001 B1
6263190 Mamori et al. Jul 2001 B1
6292665 Hildebrand et al. Sep 2001 B1
6298233 Souissi et al. Oct 2001 B1
6307503 Liu et al. Oct 2001 B1
6311078 Hardouin et al. Oct 2001 B1
6317686 Ran Nov 2001 B1
6321092 Fitch et al. Nov 2001 B1
6330459 Chrichton et al. Dec 2001 B1
6351235 Stilp Feb 2002 B1
6353778 Brown et al. Mar 2002 B1
6397074 Pihl et al. May 2002 B1
6405047 Moon Jun 2002 B1
6407703 Minter et al. Jun 2002 B1
6429815 Soliman Aug 2002 B1
6434396 Rune Aug 2002 B1
6449486 Rao Sep 2002 B1
6453168 McCrady et al. Sep 2002 B1
6493539 Falco et al. Dec 2002 B1
6515623 Johnson Feb 2003 B2
6522296 Holt Feb 2003 B2
6526335 Treyz et al. Feb 2003 B1
6552682 Fan Apr 2003 B1
6560532 Cayford May 2003 B2
6560567 Yechuri et al. May 2003 B1
6594576 Fan et al. Jul 2003 B2
6604083 Bailey et al. Aug 2003 B1
6668226 Sutanto et al. Dec 2003 B2
6690292 Meadows et al. Feb 2004 B1
6744383 Alfred et al. Jun 2004 B1
6744740 Chen Jun 2004 B2
6757545 Nowak et al. Jun 2004 B2
6801782 McCrady et al. Oct 2004 B2
6801855 Walters et al. Oct 2004 B1
6816782 Walters et al. Nov 2004 B1
6850761 Pallonen Feb 2005 B2
6892054 Belcher et al. May 2005 B2
6915123 Daudelin et al. Jul 2005 B1
6933100 Igawa et al. Aug 2005 B2
6933860 Gehman et al. Aug 2005 B1
7058710 McCall et al. Jun 2006 B2
7065349 Nath et al. Jun 2006 B2
7098805 Meadows et al. Aug 2006 B2
7113793 Veerasamy et al. Sep 2006 B2
7149534 Bloebaum et al. Dec 2006 B2
7181218 Ovesjo et al. Feb 2007 B2
7203752 Rice et al. Apr 2007 B2
7277049 Komeluk et al. Oct 2007 B2
7289039 Kato et al. Oct 2007 B2
7346359 Damarla et al. Mar 2008 B2
7359719 Duffett-Smith et al. Apr 2008 B1
7366492 Ganesh Apr 2008 B1
7375649 Gueziec May 2008 B2
7420464 Fitzgerald et al. Sep 2008 B2
7432829 Poltorak Oct 2008 B2
7436794 Takahashi et al. Oct 2008 B2
7463143 Forr et al. Dec 2008 B2
7508321 Gueziec Mar 2009 B2
7664492 Lee et al. Feb 2010 B1
7696922 Nicholson et al. Apr 2010 B2
7697917 Camp et al. Apr 2010 B2
7706964 Horvitz et al. Apr 2010 B2
7744740 Diehl Jun 2010 B2
7747258 Farmer et al. Jun 2010 B2
7761225 Vaughn Jul 2010 B2
7831380 Chapman et al. Nov 2010 B2
7848880 Cheung Dec 2010 B2
7890299 Fok et al. Feb 2011 B2
7917156 Sheynblat et al. Mar 2011 B2
7945271 Barnes et al. May 2011 B1
7958001 Abbadessa et al. Jun 2011 B2
7962162 McNair Jun 2011 B2
7962280 Kindo et al. Jun 2011 B2
7994981 Farrokhi et al. Aug 2011 B1
7996020 Chhabra Aug 2011 B1
8000726 Altman et al. Aug 2011 B2
8005050 Scheinert et al. Aug 2011 B2
8010164 Sennett et al. Aug 2011 B1
8036822 Ho et al. Oct 2011 B2
8050690 Neeraj Nov 2011 B2
8054802 Burgess et al. Nov 2011 B2
8065185 Foladare et al. Nov 2011 B2
8098152 Zhang et al. Jan 2012 B2
8121604 Schwinghammer Feb 2012 B1
8126479 Morrison Feb 2012 B2
8140079 Olson Mar 2012 B2
8193984 Ward et al. Jun 2012 B2
8194589 Wynn et al. Jun 2012 B2
8195175 Govindan et al. Jun 2012 B2
8224349 Meredith et al. Jul 2012 B2
8253559 Howard et al. Aug 2012 B2
8254959 Fix et al. Aug 2012 B2
8264956 Ramankutty et al. Sep 2012 B2
8270933 Riemer et al. Sep 2012 B2
8280438 Barbera et al. Oct 2012 B2
8295854 Osann et al. Oct 2012 B2
8300663 Chion et al. Oct 2012 B2
8307030 Hu Nov 2012 B1
8326682 Redford et al. Dec 2012 B2
8355364 Vargantwar et al. Jan 2013 B1
8355865 Wagner et al. Jan 2013 B2
8402356 Martinez et al. Mar 2013 B2
8417264 Whitney et al. Apr 2013 B1
8437790 Hassan et al. May 2013 B1
8464164 Hon et al. Jun 2013 B2
8469274 Tseng et al. Jun 2013 B2
8548494 Agarwal et al. Oct 2013 B2
8572198 Jhanji Oct 2013 B2
8594700 Nabbefeld Nov 2013 B2
8611919 Barnes Dec 2013 B2
8612410 Meredith et al. Dec 2013 B2
8666388 Catovic et al. Mar 2014 B2
8666390 Meredith et al. Mar 2014 B2
8761799 Meredith et al. Jun 2014 B2
8768348 Stuempert et al. Jul 2014 B2
8897805 Fix et al. Nov 2014 B2
8909247 Tipton et al. Dec 2014 B2
8923134 Meredith et al. Dec 2014 B2
8929827 Fix et al. Jan 2015 B2
9008684 Tipton et al. Apr 2015 B2
9008698 Meredith et al. Apr 2015 B2
9066227 Spencer et al. Jun 2015 B2
9232399 Tipton et al. Jan 2016 B2
9351111 Kaufman et al. May 2016 B1
9667660 Tipton et al. May 2017 B2
10084824 Tipton et al. Sep 2018 B2
20010047242 Ohta Nov 2001 A1
20020059266 I'anson et al. May 2002 A1
20020069312 Jones Jun 2002 A1
20020077116 Havinis et al. Jun 2002 A1
20020172223 Stilp et al. Nov 2002 A1
20030040323 Pihl et al. Feb 2003 A1
20030092448 Forstrom May 2003 A1
20030095065 Ericson et al. May 2003 A1
20030097330 Hillmer et al. May 2003 A1
20030115228 Horvitz et al. Jun 2003 A1
20030115260 Edge Jun 2003 A1
20030125046 Riley et al. Jul 2003 A1
20030158924 DeLegge Aug 2003 A1
20030222819 Karr et al. Dec 2003 A1
20030225508 Petzld et al. Dec 2003 A9
20040023664 Mirouze et al. Feb 2004 A1
20040024639 Goldman et al. Feb 2004 A1
20040067759 Spirit et al. Apr 2004 A1
20040082338 Norrgard et al. Apr 2004 A1
20040127191 Matsunaga Jul 2004 A1
20040131036 Walsh Jul 2004 A1
20040155814 Bascobert Aug 2004 A1
20040172190 Tsunehara et al. Sep 2004 A1
20040219930 Lin Nov 2004 A1
20040224698 Yi et al. Nov 2004 A1
20040267410 Dud et al. Dec 2004 A1
20040267561 Meshkin et al. Dec 2004 A1
20050007993 Chambers et al. Jan 2005 A1
20050039056 Bagga et al. Feb 2005 A1
20050043037 Ioppe et al. Feb 2005 A1
20050053099 Spear et al. Mar 2005 A1
20050136911 Csapo et al. Jun 2005 A1
20050239410 Rochester Oct 2005 A1
20050272445 Zellner et al. Dec 2005 A1
20050276385 McCormick et al. Dec 2005 A1
20060030333 Ward et al. Feb 2006 A1
20060046744 Dublish et al. Mar 2006 A1
20060075131 Douglas et al. Apr 2006 A1
20060089153 Sheynblat Apr 2006 A1
20060143292 Taubenheim et al. Jun 2006 A1
20060200303 Fuentes et al. Sep 2006 A1
20060233133 Liu et al. Oct 2006 A1
20060240839 Chen et al. Oct 2006 A1
20060240841 Bhattacharya Oct 2006 A1
20060246918 Fok et al. Nov 2006 A1
20060267841 Lee et al. Nov 2006 A1
20060270419 Crowly et al. Nov 2006 A1
20060276168 Fuller, Jr. et al. Dec 2006 A1
20060282660 Varghese et al. Dec 2006 A1
20070001873 Ishikawa et al. Jan 2007 A1
20070049286 Kim et al. Mar 2007 A1
20070060130 Gogic et al. Mar 2007 A1
20070088818 Roberts et al. Apr 2007 A1
20070121560 Edge May 2007 A1
20070149214 Walsh et al. Jun 2007 A1
20070176749 Boyd Aug 2007 A1
20070213074 Fitch et al. Sep 2007 A1
20070217375 Zampiello et al. Sep 2007 A1
20070217379 Fujiwara et al. Sep 2007 A1
20070293157 Haartsen et al. Dec 2007 A1
20070298807 Yarkosky Dec 2007 A1
20080004789 Horvitz et al. Jan 2008 A1
20080010365 Schneider Jan 2008 A1
20080032705 Patel et al. Feb 2008 A1
20080039114 Phatak et al. Feb 2008 A1
20080056193 Bourlas et al. Mar 2008 A1
20080070593 Altman et al. Mar 2008 A1
20080071466 Downs et al. Mar 2008 A1
20080076450 Nanda et al. Mar 2008 A1
20080096566 Brunner et al. Apr 2008 A1
20080127354 Carpenter et al. May 2008 A1
20080133730 Park et al. Jun 2008 A1
20080186234 Alles et al. Aug 2008 A1
20080192682 Matsumoto et al. Aug 2008 A1
20080274750 Carlson et al. Nov 2008 A1
20080299995 Spain Dec 2008 A1
20080305832 Greenberg Dec 2008 A1
20080311923 Petrovic et al. Dec 2008 A1
20090005064 Malik Jan 2009 A1
20090017823 Sachs et al. Jan 2009 A1
20090024546 Ficcaglia et al. Jan 2009 A1
20090028082 Wynn et al. Jan 2009 A1
20090052330 Matsunaga et al. Feb 2009 A1
20090063030 Howarter et al. Mar 2009 A1
20090079622 Seshadri et al. Mar 2009 A1
20090104917 Rached et al. Apr 2009 A1
20090117907 Wigren et al. May 2009 A1
20090125380 Otto et al. May 2009 A1
20090131073 Carlson et al. May 2009 A1
20090161599 Haartsen et al. Jun 2009 A1
20090177382 Alles et al. Jul 2009 A1
20090181695 Wirola et al. Jul 2009 A1
20090227265 Kang et al. Sep 2009 A1
20090234876 Schigel et al. Sep 2009 A1
20090260055 Parmar Oct 2009 A1
20090280828 Wang et al. Nov 2009 A1
20090286510 Huber et al. Nov 2009 A1
20090287922 Herwono et al. Nov 2009 A1
20090299788 Huber et al. Dec 2009 A1
20090310501 Catovic et al. Dec 2009 A1
20090312005 Mukundan et al. Dec 2009 A1
20090327134 Carlson et al. Dec 2009 A1
20100004997 Mehta et al. Jan 2010 A1
20100020776 Youssef et al. Jan 2010 A1
20100054237 Han et al. Mar 2010 A1
20100056179 Gaenger et al. Mar 2010 A1
20100058442 Costa et al. Mar 2010 A1
20100081389 Lawrow et al. Apr 2010 A1
20100094758 Chamberlain et al. Apr 2010 A1
20100100732 Hatakeyama et al. Apr 2010 A1
20100113035 Eskicioglu et al. May 2010 A1
20100120447 Anderson et al. May 2010 A1
20100122314 Zhang et al. May 2010 A1
20100124886 Fordham et al. May 2010 A1
20100124931 Eskicioglu et al. May 2010 A1
20100135178 Aggarwal et al. Jun 2010 A1
20100144368 Sullivan Jun 2010 A1
20100159951 Shkedi et al. Jun 2010 A1
20100163632 Tseng et al. Jul 2010 A1
20100172259 Aggarwal et al. Jul 2010 A1
20100180039 Oh et al. Jul 2010 A1
20100189236 MacDonald et al. Jul 2010 A1
20100190509 Davis et al. Jul 2010 A1
20100195566 Krishnamurthy et al. Aug 2010 A1
20100203903 Dingier et al. Aug 2010 A1
20100207470 Kim et al. Aug 2010 A1
20100220665 Govindan et al. Sep 2010 A1
20100222075 Miura Sep 2010 A1
20100227589 Cook et al. Sep 2010 A1
20100250542 Fujimaki Sep 2010 A1
20100262449 Monteforte et al. Oct 2010 A1
20100273504 Bull et al. Oct 2010 A1
20100313157 Carlsson et al. Oct 2010 A1
20100291907 MacNaughtan et al. Nov 2010 A1
20100296467 Pelletier et al. Nov 2010 A1
20100299060 Snavely et al. Nov 2010 A1
20100311437 Palanki et al. Dec 2010 A1
20100323723 Gerstenberger et al. Dec 2010 A1
20100331013 Zhang Dec 2010 A1
20110009068 Miura Jan 2011 A1
20110010085 Tanaka et al. Jan 2011 A1
20110023129 Vernal Jan 2011 A1
20110026475 Lee et al. Feb 2011 A1
20110026495 Lee et al. Feb 2011 A1
20110028129 Hutchison et al. Feb 2011 A1
20110039593 Lee et al. Feb 2011 A1
20110053609 Grogan et al. Mar 2011 A1
20110060808 Martin et al. Mar 2011 A1
20110065450 Kazmi Mar 2011 A1
20110069668 Chion et al. Mar 2011 A1
20110072034 Sly Mar 2011 A1
20110076975 Kim et al. Mar 2011 A1
20110077030 Wigren et al. Mar 2011 A1
20110077032 Correale et al. Mar 2011 A1
20110099047 Weiss et al. Apr 2011 A1
20110106416 Scofield et al. May 2011 A1
20110130135 Trigui Jun 2011 A1
20110151839 Bolon et al. Jun 2011 A1
20110161261 Wu et al. Jun 2011 A1
20110164596 Montemurro et al. Jul 2011 A1
20110171912 Beck et al. Jul 2011 A1
20110172905 Schroder et al. Jul 2011 A1
20110205964 Fix et al. Aug 2011 A1
20110207470 Meredith Aug 2011 A1
20110210843 Kummetz et al. Sep 2011 A1
20110210849 Howard et al. Sep 2011 A1
20110244879 Siomina et al. Oct 2011 A1
20110256874 Hayama et al. Oct 2011 A1
20110271331 Adams Nov 2011 A1
20110287801 Levin et al. Nov 2011 A1
20110296169 Palmer Dec 2011 A1
20110319098 Potorny et al. Dec 2011 A1
20120016902 Ranjan et al. Jan 2012 A1
20120025976 Richey et al. Feb 2012 A1
20120028650 Cooper et al. Feb 2012 A1
20120030083 Newman et al. Feb 2012 A1
20120032855 Reede et al. Feb 2012 A1
20120052883 Austin et al. Mar 2012 A1
20120052884 Bogatin Mar 2012 A1
20120062415 Hwang et al. Mar 2012 A1
20120069386 St. Laurent et al. Mar 2012 A1
20120087338 Brandt et al. Apr 2012 A1
20120099621 Karlsson et al. Apr 2012 A1
20120115505 Miyake et al. May 2012 A1
20120139782 Gutt et al. Jun 2012 A1
20120144452 Dyor et al. Jun 2012 A1
20120144457 Counterman Jun 2012 A1
20120158289 Brush et al. Jun 2012 A1
20120182180 Wolf et al. Jul 2012 A1
20120182874 Siomina et al. Jul 2012 A1
20120185309 Kakarla et al. Jul 2012 A1
20120214509 Levin et al. Aug 2012 A1
20120221232 Shang et al. Aug 2012 A1
20120253656 Brandt Oct 2012 A1
20120276900 Stephens et al. Nov 2012 A1
20120282924 Tagg et al. Nov 2012 A1
20120286997 Lin et al. Nov 2012 A1
20120287911 Takano et al. Nov 2012 A1
20120302254 Charbit et al. Nov 2012 A1
20120317500 Kosseifi et al. Dec 2012 A1
20120323703 Hillier et al. Dec 2012 A1
20120327869 Wang et al. Dec 2012 A1
20130007058 Meredith et al. Jan 2013 A1
20130023237 Meredith et al. Jan 2013 A1
20130023247 Bolon et al. Jan 2013 A1
20130023274 Meredith et al. Jan 2013 A1
20130023281 Meredith et al. Jan 2013 A1
20130053057 Cansino et al. Feb 2013 A1
20130066748 Long Mar 2013 A1
20130095861 Li et al. Apr 2013 A1
20130096966 Barnes Apr 2013 A1
20130109407 Tipton et al. May 2013 A1
20130114464 Tarraf et al. May 2013 A1
20130122863 Chen et al. May 2013 A1
20130137464 Kramer et al. May 2013 A1
20130150053 Hwang et al. Jun 2013 A1
20130226451 O'Neill et al. Aug 2013 A1
20130267242 Curticapean et al. Oct 2013 A1
20130281111 Syrjarinne et al. Oct 2013 A1
20130288704 Wirola Oct 2013 A1
20130310075 Lim et al. Nov 2013 A1
20130324149 Fix et al. Dec 2013 A1
20130337824 Meredith et al. Dec 2013 A1
20130337826 Fix et al. Dec 2013 A1
20140062782 Abraham Mar 2014 A1
20140106779 Arslan et al. Apr 2014 A1
20140122220 Bradley et al. May 2014 A1
20140171060 Cook et al. Jun 2014 A1
20140278744 Lo Faro et al. Sep 2014 A1
20140295881 Werner et al. Oct 2014 A1
20140365488 Arslan et al. Dec 2014 A1
20150011249 Siliski et al. Jan 2015 A1
20150098712 Li et al. Apr 2015 A1
20170280317 Tagg et al. Sep 2017 A1
Foreign Referenced Citations (6)
Number Date Country
0856746 Aug 1998 EP
1145526 Oct 2001 EP
2004069609 Mar 2004 JP
2005091303 Apr 2005 JP
2007328050 Dec 2007 JP
WO2006031035 Mar 2006 WO
Non-Patent Literature Citations (224)
Entry
Office Action dated Apr. 8, 2014 for U.S. Appl. No. 13/175,199, 52 Pages.
Office Action dated Apr. 23, 2014 for U.S. Appl. No. 13/291,917, 29 Pages.
Office Action dated Apr. 22, 2014 for U.S. Appl. No. 13/447,069, 51 Pages.
Office Action dated Sep. 20, 2012 for U.S. Appl. No. 12/870,254, 29 pages.
Office Action dated May 14, 2014 for U.S. Appl. No. 13/660,689, 62 pages.
Office Action dated May 9, 2014 for U.S. Appl. No. 13/188,136, 33 pages.
Squires, “Practical Physics”, Cambridge University Press, p. 12, 1986, 3 pages.
Represent (2000). In Collins English dictionary. Retrieved on May 9, 2014 from http://search.credoreference.com/content/entry/hcengdict/represent/0, 2 pages.
Represent. (2001). In Chambers 21 st century dictionary. Retrieved on May 9, 2014 from http://search.credoreference.com/content/entry/chambdict/represent/O.
Represent. (2011). In the American heritage dictionary of the English language. Retrieved on May 9, 2014 from http://search.credoreference.com/content/entry/hmdictenglang/represent/0.
Office Action dated May 20, 2014 for U.S. Appl. No. 13/551,369, 29 pages.
Office Action dated May 30, 2014 for U.S. Appl. No. 13/277,595, 49 pages.
Office Action dated Jun. 3, 2014 for U.S. Appl. No. 13/523,770, 53 pages.
Office Action dated Jun. 6, 2014 for U.S. Appl. No. 13/447,072, 25 pages.
Office Action dated Apr. 3, 2014 for U.S. Appl. No. 13/188,295, 37 pages.
Office Action dated Jun. 18, 2014 for U.S. Appl. No. 13/305,276, 26 Pages.
Office Action dated Jun. 26, 2014 for U.S. Appl. No. 13/557,425, 24 Pages.
Office Action dated Jun. 30, 2014 for U.S. Appl. No. 13/305,267, 44 Pages.
Office Action dated Jul. 22, 2014 for U.S. Appl. No. 12/958,146, 38 Pages.
Notice of Allowance dated Jul. 22, 2014 for U.S. Appl. No. 13/525,065, 82 Pages.
Notice of Allowance dated Jul. 7, 2014 for U.S. Appl. No. 13/188,295, 51 pages.
Notice of Allowance dated Jul. 22, 2014 for U.S. Appl. No. 13/188,300, 49 Pages.
Office Action dated Aug. 8, 2014 for U.S. Appl. No. 13/284,497, 48 pages.
Office Action dated Mar. 11, 2016 for U.S. Appl. No. 14/743,076, 86 pages.
Notice of Allowance dated Mar. 16, 2016 for U.S. Appl. No. 14/520,287, 23 pages.
Office Action dated Mar. 18, 2016 for U.S. Appl. No. 13/447,072, 37 pages.
Office Action dated Apr. 5, 2016 for U.S. Appl. No. 13/188,136, 33 pages.
Office Action dated Apr. 13, 2016 for U.S. Appl. No. 14/877,915, 76 pages.
Office Action dated May 17, 2016 for U.S. Appl. No. 15/074,622, 18 pages.
Office Action dated Jun. 10, 2016 for U.S. Appl. No. 14/548,901, 33 pages.
Office Action dated Jun. 22, 2016 for U.S. Appl. No. 14/970,533, 84 pages.
Office Action dated Jun. 28, 2016 for U.S. Appl. No. 15/132,220, 17 pages.
Notice of Allowance dated Jul. 19, 2016 for U.S. Appl. No. 14/952,609, 99 pages.
Office Action dated Aug. 24, 2016 for U.S. Appl. No. 14/676,066, 107 pages.
Office Action dated Aug. 25, 2016 for U.S. Appl. No. 13/447,072, 38 pages.
Office Action dated Sep. 30, 2016 for U.S. Appl. No. 14/957,525, 72 pages.
Notice of Allowance dated Oct. 7, 2016 for U.S. Appl. No. 14/548,901, 45 pages.
Office Action dated Oct. 12, 2016 for U.S. Appl. No. 14/877,915, 34 pages.
Notice of Allowance dated Nov. 16, 2016 for U.S. Appl. No. 15/186,410, 80 pages.
Office Action dated Dec. 28, 2016 for U.S. Appl. No. 13/447,072, 34 pages.
3rd Generation Partnership Project, Technical Specification, “Group GSM/EDGE Radio Access Network, Radio subsystem synchronization (Release 8)”, 3GPP TS 45.010 V8.0.0 (May 2008), last viewed Jul. 1, 2009, 30 pages.
3rd Generation Partnership Project, Technical Specification, “Group Radio Access Network, UTRAN luh interface Home Node B Application Part (HNBAP) signalling (Release 8)”, 3GPP TS 25.469 V8.0.0 (Dec. 2008), last viewed Jul. 1, 2009, 56 pages.
Sullivan, Mark. “Signs and Wonders: Is AT&T Stepping Up Its Game?” PC World, Dec. 10, 2009, 1 page.
ETSI TS 125 215 V6.4.0 (Sep. 2005). Universal Mobile Telecommunications System (UMTS), Physical layer, Measurements (FDD), 3GPP TS 25.215 version 6.4.0 Release 6). Last accessed Jun. 18, 2010, 20 pages.
ETSI TS 125 331 V6.9.0 (2006-03). Universal Mobile Telecommunications System (UMTS), Radio Resource Control (RRC) protocol specification, (3GPP TS 25.331 version 6.9.0 Release 6). Last accessed Jun. 18, 2010, 1211 pages.
New Devices Aim to Disable Cell Phones While Driving. FOXNews.com, Jan. 18, 2009. http://www.foxnews.com/printer_friendly_story/0,3566,480585,00.html. Last accessed Nov. 24, 2010, 2 pages.
Cortes, et al. “Support-Vector Networks”, Machine Learning, 20, 1995. http://www.springerlink.com/content/k238jx04hm87j80g/fulltext.pdf. Last accessed Dec. 24, 2010, 25 pages.
ACM Website, Press release of Mar. 17, 2009. http://www.acm.org/press-room/news-releases/pdfs/awards-08-groupa1.pdf. Last accessed Dec. 24, 2010, 3 pages.
Boser, et al. A training algorithm for optimal margin classifiers. In D. Haussler, editor, 5th Annual ACM Workshop on COLT, pp. 144-152, Pittsburgh, PA, 1992. ACM Press.http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.21.3818. Last accessed Dec. 24, 2010, 9 pages.
Hsu, et al. A Practical Guide to Support Vector Classification. Department of Computer Science National Taiwan University, Last updated: Apr. 15, 2010.http://www.csie.ntu.edu.tw/˜cjlin/papers/guide/guide.pdf. Last accessed Dec. 24, 2010, 16 pages.
Drucker, et al. Support Vector Regression Machines.http://scholar.google.com/scholar?q=%22Support+Vector+Regression+Machines.%22. Last accessed Dec. 24, 2010, 7 pages.
Suykens, et al., “Least squares support vector machine classifiers”, Neural Processing Letters, vol. 9, No. 3, Jun. 1999, pp. 293-300.
Ferris, et al (2002). “Interior-point methods for massive support vector machines”. SIAM Journal on Optimization 13: 783-804. doi:10.1137/S1052623400374379.
Meyer, et al “The support vector machine under test.” Neurocomputing 55(1-2): 169-186, 2003.
International Search Report for PCT Application No. US2011/026122, dated Sep. 10, 2011, 11 pages.
International Search Report for PCT Application No. US2011/026120, dated Sep. 9, 2011, 13 pages.
Charitanetra et al. “Mobile positioning location using E-OTD method for GSM network” Research and Development, 2003. Proceedings Student Conference on Putrajaya, Malaysia Aug. 25-26, 2003, pp. 319-324.
“Location Labs Powers Location-based Fraud Detection”, All Points Blog, http://webcache.googleusercontent.com/search?hl=en&rlz=1R2GFRE_enUS398&q=cache:trsMn9Sin6wJ:http://apb.directionsmag.com/entry/location-labs-powers-location-based-fraud-detection/162802+http%3A//apb.directionsmag.com/entry/location-labs-powers-location-pased-...1&ct=clnk, Oct. 12, 2010.
“Location Based Fraud Detection”, Finsphere Corporation, 2008-2010.
Fleishman. Using the Personal Hotspot on your AT & T iPhone. Published online Mar. 15, 2011. http://www.macworld.com/article/158556/2011/03/personal_hotspot_att . . . , 4 pages.
Fleischfresser. Never Stop at a Red-Light Again. Published online Aug. 30, 2011. http://www.smartplanet.com/plog/ . . . , 2 pages.
Cellphone Networks and the Future of Traffic. Published online Mar. 2, 2011. http://m.wired.com/autopia/2011/03/cell-phone-networks-and-the-future- . . . 15 pages.
Intelligent Transportation System. Published online http://en.wikipedia.org/wiki/Intelligent_transportation_system, retrieved on Aug. 15, 2011, 7 pages.
Koukoumidis Emmanouil, PEH Li-Shiuan, Martonosi Margaret, SignalGuru: Leveraging Mobile Phones for Collaborative Traffic Signal Schedule Advisory, Mobisys'11, Jun. 28-Jul. 1, 2011, Bethesda, Maryland, USA. 14 pages.
Bitcarrier Technology. Published online at http://www.bitcarrier.com/technology, retrieved on Aug. 15, 2011, 1 page.
Hao Peng, Ban Xuegang(Jeff). Estimating Vehicle Position in a Queue at Signalized Intersections Using Simple Travel Times from Mobile Sensors, retrieved Nov. 18, 2011. 6 pages.
Ban Xuegang(Jeff), Gruteser Marco. Mobile Sensor as Traffic Probes: Addressing Transportation Modeling and Privacy Protection in an Integrated Framework, dated Jan. 10, 2010, 17 pages.
Office Action for U.S. Appl. No. 12/836,471 dated Dec. 28, 2011, 34 pages.
Office Action dated Feb. 23, 2012 for U.S. Appl. No. 12/967,747, 31 pages.
Office Action dated Dec. 15, 2011 for U.S. Appl. No. 12/712,424, 34 pages.
Office Action dated Apr. 13, 2012 for U.S. Appl. No. 12/416,853, 36 pages.
Office Action dated Oct. 2, 2012 for U.S. Appl. No. 13/554,285, 19 pages.
Office Action dated Aug. 30, 2012 for U.S. Appl. No. 12/958,146, 40 pages.
MobileLutions Introduces MobiLoc-A Breakthrough Technology to Control Texting in the Mobile Workplace. Press release Oct. 10, 2010 by MobileLutions. 2 pages.
DriveAssist Frequently Ask question by Aegis Mobility, Wayback archive Jul. 12, 2010, 2 pages.
Dffice Action dated Jul. 30, 2012 for U.S. Appl. No. 12/967,747, 28 pages.
Office Action dated Jul. 17, 2012 for U.S. Appl. No. 13/220,083, 57 pages.
Office Action dated Sep. 11, 2012 for U.S. Appl. No. 13/188,345, 44 pages.
Office Action dated Oct. 15, 2012 for U.S. Appl. No. 13/523,778, 21 pages.
Office Action dated Dec. 20, 2012 for U.S. Appl. No. 12/958,146, 23 pages.
Office Action dated Dec. 28, 2012 for U.S. Appl. No. 13/188,295, 37 pages.
Office Action dated Jan. 3, 2013 for U.S. Appl. No. 13/188,300, 36 pages.
Office Action dated Nov. 8, 2012 for U.S. Appl. No. 13/204,535, 30 pages.
Office Action dated Jan. 25, 2013, for U.S. Appl. No. 13/554,285, 20 pgs.
Office Action dated Mar. 19, 2013, for U.S. Appl. No. 13/174,541, 46 pgs.
Office Action dated Feb. 13, 2013, for U.S. Appl. No. 13/220,083, 48 pgs.
Office Action dated Feb. 22, 2013, for U.S. Appl. No. 13/188,345, 45 pgs.
Office Action dated Mar. 15, 2013, for U.S. Appl. No. 13/204,535, 18 pgs.
Office Action dated Mar. 19, 2013, for U.S. Appl. No. 13/284,497, 46 pgs.
Office Action dated Apr. 19, 2013, for U.S. Appl. No. 13/277,595, 58 pages.
Notice of Allowance dated Aug. 12, 2013, for U.S. Appl. No. 13/174,541, 40 pages.
Office Action dated Aug. 2, 2013, for U.S. Appl. No. 13/188,295, 26 pages.
Office Action dated Aug. 2, 2013, for U.S. Appl. No. 13/188,300, 38 pages.
Office Action dated Jun. 20, 2013, for U.S. Appl. No. 13/219,911, 61 pages.
Office Action dated Jul. 17, 2013, for U.S. Appl. No. 13/188,345, 27 pages.
Office Action dated Jun. 20, 2013, for U.S. Appl. No. 13/291,917, 52 pages.
Office Action dated May 31, 2013, for U.S. Appl. No. 13/523,770, 40 pages.
Office Action dated Sep. 19, 2013, for U.S. Appl. No. 13/927,020, 30 pages.
Office Action dated Oct. 2, 2013 for U.S. Appl. No. 12/958,146, 31 pages.
Office Action dated Sep. 26, 2013 for U.S. Appl. No. 13/284,456, 58 pages.
RouteFinder 3.00 for ArGIS Documentation, 2007, Routeware and Higher Mapping Solutions, 71 pages, downloaded from http://www.routeware.dk/download/routefinder_arcgis.pdf.
mySociety (Web page), “More travel-time maps and their uses”, 2007, downloaded from http://www.mySociety.org/2007/more-travel-maps/, 10 pages total (including a single page Examiner's attachment showing the operation of the interactive travel-time map).
Wayback machine archive from Jan. 21, 2009 of the mySociety Web page, “More travel-time maps and their uses”, downloaded from http://web.archive.org/web/20090121193615/http://www.mysociety.org/2007/more-travel-maps/, 11 pages.
Street, Nicholas, “TimeContours: Using isochrone visualisation to describe transport network travel cost”, Final Report, Jun. 14, 2006, Department of Computing Imperial College London, 97 pages. Downloaded from http://www.doc.ic.ac.uk/teaching/projects/Distinguished06/nicholasstreet.pdf.
Office Action dated Nov. 5, 2013 for U.S. Appl. No. 13/188,136, 47 pages.
Office Action dated Sep. 18, 2013, for U.S. Appl. No. 13/284,497, 30 pages.
Office Action dated Aug. 22, 2013, for U.S. Appl. No. 13/277,595, 36 pages.
Office Action dated Oct. 21, 2013, for U.S. Appl. No. 13/523,770, 24 pages.
Office Action dated Nov. 5, 2013 for U.S. Appl. No. 13/188,345, 30 pages.
Office Action dated Dec. 11, 2013, for U.S. Appl. No. 13/188,295, 52 pages.
Office Action dated Dec. 24, 2013, for U.S. Appl. No. 13/188,300, 44 pages.
Office Action dated Dec. 11, 2013, for U.S. Appl. No. 13/291,917, 34 pages.
Office Action dated Jan. 15, 2014 for U.S. Appl. No. 13/219,911, 38 pages.
Office Action dated Jan. 28, 2014, for U.S. Appl. No. 12/958,146, 24 pages.
Notice of Allowance dated Feb. 14, 2014 for U.S. Appl. No. 13/284,456, 30 pages.
Office Action dated Feb. 24, 2014, for U.S. Appl. No. 13/927,020, 18 pages.
Office Action dated May 21, 2013 for U.S. Appl. No. 13/305,276, 28 pages.
Office Action dated Oct. 24, 2012 for U.S. Appl. No. 13/305,276, 37 pages.
“Locate your friends in real time with Google Latitude.” http://googlemobile.blogspot.com/2009/02/locate-your-friends-in-real-time-with.html. Last accessed Mar. 8, 2012, 23 pages.
“Location sharing and updating.” http://support.google.com/mobile/bin/answer.py?hl=en&answer=136647. Last accessed Mar. 8, 2012, 3 pages.
“Privacy Settings.” Ittp://support.google.com/mobile/bin/answer.py?hl=en&answer=136650, Last accessed Mar. 8, 2012, 1 page.
Office Action dated Nov. 25, 2013 for U.S. Appl. No. 13/447,069, 40 pages.
Office Action dated May 9, 2013 for U.S. Appl. No. 13/447,069, 33 pages.
Tsai, et al, “Location-Sharing Technologies: Privacy Risks and Controls.” Feb. 2010. Retrieved on May 10, 2013, 26 pages.
Li et al, “Sharing Location in Online Social Networks”. IEEE Network, Sep./Oct. 2010; 0890-8044/10/$25.00 (c)2010 IEEE. Retrieved on May 10, 2013, 6 pages.
Tsai, et al, “Who's Viewed You? The Impact of Feedback in a Mobile Location-Sharing Application”. CHI 2009—Security and Privacy, Apr. 9, 2009—Boston, MA, USA. Retrieved on May 10, 2013, 10 pages.
Pettersen, et al., “Automatic antenna tilt control for capacity enhancement in UMTS FDD.” Retrieved on Mar. 25, 2012, 5 pages.
Islam, et al., “Self-Optimization of Antenna Tilt and Pilot Power for Dedicated Channels.” Retrieved on Mar. 25, 2012, 8 pages.
Bigham, et al., “Tilting and Beam-shaping for Traffic Load Balancing in WCDMA Network.” Retrieved on Mar. 25, 2012, 4 pages.
3GPP TS 25.215 V6A.0 (Sep. 2005) Physical Layer Measurements, Sep. 2005.
3GPP TS 25.331 V6.9.0 (Mar. 2006) RRC protocol for the UE-UTRAN radio interface, Mar. 2006.
3GPP TS 25A13 V6.9.0 (Mar. 2006) UTRAN lu interface RANAP signalling, Mar. 2006.
Dalabrese, et al., “Real-Time Urban Monitoring Using Cell Phones: A Case Study in Rome”. IEEE Transactions on Intelligent Transportation Systems, 12 pages. (http://senseable.mit.edu/papers/pdf/2010_Calabrese_et_al_Rome_TITS.pdf). Retrieved on Sep. 29, 2012, 11 pages.
Smith, et al., “Airsage Overview”, (http://mikeontraffic.typepad.com/files/raleigh-winter-2011-presentation-v11-final.pdf) Retrieved on Sep. 29, 2012, 39 pages.
Office Action dated Feb. 5, 2014 for U.S. Appl. No. 13/526,988, 56 pages.
Marko Silventoinen, Timo Rantalainen, “Mobile Station Locating in GSM” Helsinki, Finland, Last accessed on Nov. 15, 2011, 7 pages.
Office Action dated Dec. 30, 2013 for U.S. Appl. No. 13/305,267, 10 pages.
Office Action dated Mar. 25, 2014 for U.S. Appl. No. 13/488,144, 60 Pages.
Interview Summary dated Feb. 3, 2014 for U.S. Appl. No. 13/188,136, 10 pages.
Binowitz, et al., A new positioning system using television synchronization signals, IEEE Transactions on Broadcasting, vol. 51(1), p. 51-61, Mar. 2005.
Notice of Allowance dated Aug. 21, 2014 for U.S. Appl. No. 13/447,069, 78 pages.
Office Action dated Aug. 28, 2014 for U.S. Appl. No. 13/526,988, 83 pages.
Office Action dated Sep. 22, 2014 for U.S. Appl. No. 13/175,199, 62 pages.
Office Action dated Oct. 17, 2014 for U.S. Appl. No. 13/204,535, 47 pages.
Office Action dated Oct. 20, 2014 for U.S. Appl. No. 13/494,959, 64 pages.
Office Action dated Oct. 22, 2014 for U.S. Appl. No. 13/557,425, 59 pages.
Office Action dated Aug. 11, 2014 for U.S. Appl. No. 14/279,176, 22 pages.
Office Action dated Nov. 14, 2014 for U.S. Appl. No. 13/277,595, 74 pages.
Notice of Allowance dated Nov. 20, 2014 for U.S. Appl. No. 13/866,909, 27 pages.
Notice of Allowance dated Dec. 9, 2014 for U.S. Appl. No. 12/958146, 48 pages.
Office Action dated Dec. 11, 2014 for U.S. Appl. No. 13/447,072, 28 pages.
Office Action dated Dec. 1, 2014 for U.S. Appl. No. 13/495,756, 76 pages.
Office Action dated Jan. 7, 2015 for U.S. Appl. No. 13/557,425, 30 pages.
Notice of Allowance dated Jan. 21, 2015 for U.S. Appl. No. 13/495,391, 98 pages.
Notice of Allowance dated Feb. 6, 2015 for U.S. Appl. No. 13/204,535, 20 pages.
Office Action dated Feb. 13, 2015 for U.S. Appl. No. 14/516,286, 62 pages.
Sirardin, et al., “Digital footprinting: Uncovering tourists with user generated content.” Pervasive Computing, IEEE 7.4, Oct.-Nov. 2008. 8 pages.
Steinfield, “The development of location based services in mobile commerce.” ELife after the Dot Corn Bust. PhysicaVerlagHD, 2004. 15 pages.
Sevtsuk, et al., “Does urban mobility have a daily routine? Learning from the aggregate data of mobile networks.” Journal of Urban Technology, vol. 17, No. 1, Apr. 2010: 20 pages.
Buhalis, et al., “Information communication technology revolutionizing tourism.” Tourism Recreation Research, vol. 30, No. 3, 2005. 10 pages.
Ratti, et al. “Mobile Landscapes: using location data from cell phones for urban analysis.” Environment and Planning 8: Planning and Design, vol. 33, 2006, 23 pages.
Office Action dated Sep. 14, 2015 for U.S. Appl. No. 13/557,425, 32 pages.
Office Action dated Apr. 16, 2015 for U.S. Appl. No. 14/521,431, 82 pages.
Notice of Allowance dated Mar. 19, 2015 for U.S. Appl. No. 13/494,959, 41 Pages.
Notice of Allowance dated Mar. 26, 2015 for U.S. Appl. No. 14/276,688, 75 pages.
Office Action dated May 1, 2015 for U.S. Appl. No. 13/557,425, 33 pages.
Office Action dated May 14, 2015 for U.S. Appl. No. 14/530,605, 72 pages.
Office Action dated Jun. 1, 2015 for U.S. Appl. No. 13/447,072, 38 pages.
Office Action dated Jun. 2, 2015 for U.S. Appl. No. 14/516,286, 20 pages.
Office Action dated May 20, 2015 for U.S. Appl. No. 13/526,988, 52 pages.
Office Action dated Jun. 9, 2015 for U.S. Appl. No. 13/495,756, 35 pages.
Notice of Allowance dated Jul. 8, 2015 for U.S. Appl. No. 14/548,901, 125 pages.
Buford, et al, “Location Privacy Enforcement in a Location-Based Services Platform,” IEEE, 2009, 5 pages.
Phillips, Jr., et al., “Information Sharing and Security in Dynamic Coalitions,” ACM, 2002, pp. 87-96, 10 pages.
Moniruzzaman, et al., “A Study of Privacy Policy Enforcement in Access Control Models”, Proceedings of 13th International Conference on Computer and Information Technology IEEE, 2010, pp. 352-357, 6 pages.
Office Action dated Jul. 22, 2015 for U.S. Appl. No. 13/188,136, 31 Pages.
“Cell DCH”, in INACON Glossary, published online at [http://www.inacon.de/glossary/CELL_DCH.php] retrieved on Jul. 22, 2015, 1 page.
Office Action dated Sep. 17, 2015 for U.S. Appl. No. 13/495,756, 23 Pages.
Office Action dated Sep. 18, 2015 for U.S. Appl. No. 14/641,247, 69 Pages.
Notice of Allowance dated Aug. 27, 2015 for U.S. Appl. No. 14/521,431, 39 Pages.
Office Action dated Nov. 16, 2015 for U.S. Appl. No. 13/188,136, 31 pages.
“Error”, The American Heritage(R) Dictionary of the English Language, 2011, Houghton Mifflin Company, Boston, Ma, 2 pages. Retrieved from [http://search.credoreference.com/contentientry/hmdictenglang/error/O] on Nov. 16, 2015.
Office Action dated Nov. 23, 2015 for U.S. Appl. No. 14/520,287, 80 pages.
Office Action dated Nov. 16, 2015 for U.S. Appl. No. 14/566,657, 87 pages.
Office Action dated Dec. 18, 2015 for U.S. Appl. No. 14/548,901, 35 pages.
Office Action dated Dec. 31, 2015 for U.S. Appl. No. 14/952,609, 32 pages.
Office Action dated Dec. 1, 2015 for U.S. Appl. No. 13/526,988, 43 pages.
Office Action dated Nov. 30, 2015 for U.S. Appl. No. 13/447,072, 45 pages.
Office Action dated Jan. 11, 2016 for U.S. Appl. No. 13/175,199, 29 pages.
Notice of Allowance dated Apr. 10, 2017 for U.S. Appl. No. 14/676,066, 33 pages.
Office Action dated Jan. 13, 2017 for U.S. Appl. No. 14/601,800, 95 pages.
Office Action dated Jan. 26, 2017 for U.S. Appl. No. 14/877,915, 30 pages.
Office Action dated Feb. 14, 2017 for U.S. Appl. No. 14/641,242, 120 pages.
Office Action dated Feb. 27, 2017 for U.S. Appl. No. 15/132,220, 91 pages.
Office Action dated Jun. 12, 2017 for U.S. Appl. No. 15/132,220, 25 pages.
Notice of Allowance dated May 8, 2017 for U.S. Appl. No. 15/466,853, 18 pages.
Notice of Allowance dated May 19, 2017 for U.S. Appl. No. 15/261,841, 83 pages.
Office Action dated Jun. 19, 2017 for U.S. Appl. No. 13/447,072, 47 pages.
Office Action dated Jul. 25, 2017 for U.S. Appl. No. 15/422,147, 86 pages.
Office Action dated Aug. 24, 2017 for U.S. Appl. No. 14/881,335, 125 pages.
Notice of Allowance dated Aug. 16, 2017 for U.S. Appl. No. 14/877,915, 63 pages.
Office Action dated Jan. 8, 2018 for U.S. Appl. No. 15/132,220, 30 pages.
Office Action dated Jan. 24, 2018 for U.S. Appl. No. 15/603,416, 99 pages.
Office Action dated Feb. 13, 2018 for U.S. Appl. No. 14/881,335, 54 pages.
Dffice Action dated Mar. 30, 2018 for U.S. Appl. No. 15/235,502, 14 pages.
Office Action dated Mar. 27, 2018 for U.S. Appl. No. 15/629,366, 23 pages.
Office Action dated May 2, 2018 for U.S. Appl. No. 14/704,949, 95 pages.
Office Action dated May 11, 2018 for U.S. Appl. No. 15/132,220, 29 pages.
Office Action dated Oct. 4, 2017 for U.S. Appl. No. 15/235,502, 80 pages.
Office Action dated Sep. 28, 2017 for U.S. Appl. No. 15/344,468, 107 pages.
Office Action dated Sep. 28, 2017 for U.S. Appl. No. 15/132,220, 29 pages.
Office Action dated Oct. 18, 2017 for U.S. Appl. No. 15/629,366, 131 pages.
Office Action dated Oct. 16, 2017 for U.S. Appl. No. 15/131,793, 84 pages.
Office Action dated May 30, 2018 for U.S. Appl. No. 15/629,366, 30 pages.
Office Action dated May 31, 2018 for U.S. Appl. No. 15/603,421, 91 pages.
Office Action dated May 29, 2018 for U.S. Appl. No. 14/881,335, 63 pages.
Notice of Allowance dated May 21, 2018 for U.S. Appl. No. 15/344,468, 21 pages.
Office Action dated Aug. 27, 2018 for U.S. Appl. No. 16/006,942, 24 pages.
Notice of Allowance dated Oct. 19, 2018 for U.S. Appl. No. 14/704,949, 24 pages.
Ouyang, Y. & Fallah, M. H., “The Impact of Cell Site Re-homing on the Performance of UMTS Core Networks”, International Journal of Next Generation Network (IJ NGN), vol. 2, No. 1, Mar. 2010.
Office Action dated Nov. 8, 2018 for U.S. Appl. No. 14/881,335, 68 pages.
Office Action dated Nov. 19, 2018 for U.S. Appl. No. 16/108,060, 27 pages.
Office Action dated Nov. 27, 2018 for U.S. Appl. No. 15/629,366, 35 pages.
Office Action dated Sep. 24, 2018 for U.S. Appl. No. 15/996,203, 21 pages.
Related Publications (1)
Number Date Country
20160309441 A1 Oct 2016 US
Continuations (1)
Number Date Country
Parent 13526988 Jun 2012 US
Child 15191877 US