US7783303B1 - Systems and methods for locating device activity in a wireless network - Google Patents
Systems and methods for locating device activity in a wireless network Download PDFInfo
- Publication number
- US7783303B1 US7783303B1 US11/777,942 US77794207A US7783303B1 US 7783303 B1 US7783303 B1 US 7783303B1 US 77794207 A US77794207 A US 77794207A US 7783303 B1 US7783303 B1 US 7783303B1
- Authority
- US
- United States
- Prior art keywords
- sector
- location
- sectors
- data
- bins
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
- G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
- G01S5/0205—Details
- G01S5/021—Calibration, monitoring or correction
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
Definitions
- Embodiments of the invention relates to wireless communications networks and related systems and devices. More particularly, embodiments of the invention relate to systems and methods for identifying locations of device activity in a wireless network.
- Embodiments of the invention relate to systems and methods for generating location based diagnostics and more particularly to determining a location of a device in a wireless network.
- Embodiments of the invention generate diagnostic data that represents or includes an approximation of the location of a device in the network.
- the location information included in the diagnostic data may be used to generate statistical information about the geographic area within the network where the device was operating when the location data was generated.
- this type of information can be used to characterize the performance of the network in specific geographic areas as well as improve the accuracy of dependent measurements.
- location data can be generated at any time regardless of whether a problem has occurred.
- location can be generated and collected for multiple reasons in addition to when a user experiences an issue such as a dropped call.
- location data may be collected from multiple devices, a holistic view of the network can be generated and the performance of the network as a whole can be characterized.
- wireless devices communicate using towers that are located in the wireless network.
- Towers typically have more than one sector and a wireless device typically communicates with a particular sector, but can be aware of multiple sectors on various towers.
- a diagnostic client operating on a wireless device can collect diagnostic data that is used to determine the location of the device.
- the diagnostic data may include timing information from the sectors in communication with the wireless device. Often the timing information includes an absolute clock value from the sector the device is locked onto and a timing offset representing timing from other sectors the device can decode.
- the timing information including the timing offset can be used to generate hyperbolas or paths that indicate where a wireless device is expected to be located.
- the path is expanded in width to become a probability band that approximates the expected location of the device.
- the width of the probability band can account for potential errors that may include, but are not limited to, multi-path reflections, incorrect clock values, and inaccurate tower locations.
- the location of the device can be identified as the area where the probability bands overlap. If the probability bands overlap more than once, some of the overlapping areas can be clearly discarded.
- the broadcast regions of the various sectors can also be analyzed to determine an approximate location of a wireless device.
- a broadcast region can be determined for a sector or an antenna of a tower with associated expected signal strength/quality.
- the approximate location can be identified by determining where the broadcast regions overlap.
- the overlap of the broadcast regions can also be referred to as a probability band. Further, the overlap region can be further refined using at least one probability band that is generated using hyperbolas as described above, for example.
- the approximate location can still be estimated as being close to the tower or based on the overlap of the broadcast regions for the adjacent sectors.
- the overlap of the broadcast regions is another example of a probability band.
- the device itself can store the information that may be used to determine or approximate the device's location.
- the device can store the timing information from the various sectors, the identity of the sectors communicating with the device, global positioning data (GPS data), and the like or any combination thereof.
- GPS data global positioning data
- This stored information can also be associated with events that occur at the device.
- a dropped call can be associated with information that enables the location of the device to be identified or approximated when the call was dropped.
- the stored information can be uploaded for analysis.
- this enables the location data to be considered when evaluating the network at a later time.
- the ability to consider location data sometime after an event occurs provides several advantages.
- the approximate location of a given event may be known, for example.
- the location data from multiple devices can be analyzed to detect patterns or to more accurately identify network issues.
- the location data can be used to provide a holistic view of the network that is based on locations where actual device usage occurred. As indicated previously, the location data can be reported independently of problems.
- the holistic view includes location data from, for example, successfully completed calls, etc., as well as location data associated with issues such as dropped calls, etc. As a result, the holistic view can identify areas of a network where the network is operating successfully as well as areas where problems may be experienced.
- FIG. 1 illustrates one embodiment of a wireless communications network that can be represented by grid that includes grid locations or bins;
- FIG. 2 illustrates one embodiment of probability bands that identify an approximate location of a device in a wireless network
- FIG. 3 illustrates the use of the broadcast regions associated with sectors of a tower to approximate a location of a device in a wireless network
- FIG. 4 illustrates another embodiment of using broadcast regions and/or probability bands to approximate the location of a device in a wireless network
- FIG. 5 illustrates a grid that corresponds to a wireless network and that location data can be pre-computed and used to identify the location of a device based on a best fit
- FIG. 6 illustrates one embodiment of a system for collecting diagnostic data including location data from devices operating in a network and for storing the diagnostic data according to location;
- FIG. 7 illustrates one embodiment of a method for identifying or of approximating a location of a device in a network.
- Embodiments of the invention relate to wireless communications networks and more particularly to the performance of wireless networks. Embodiments of the invention further relate to systems and methods for locating devices in wireless communications networks.
- the location of a device can then be used to provide or generate diagnostic data about a geographical area or relating to the performance of an RF network with respect to the location of the device.
- the diagnostic data collected by a wireless device, including the location data can be transmitted in real-time or stored on the device for some period of time before being forwarded to a server for analysis. Diagnostic data, by way of example only, can be used to improve network performance, respond to user issues, identify causes of network problems, characterize the performance of the network at various levels of granularity, and the like.
- the location data is approximated.
- embodiments of the invention can generate diagnostic data using relatively inaccurate location data.
- the diagnostic data from multiple devices can be collected and organized according to the location data received or collected from the devices.
- the location specific diagnostic data can be binned according to location or to approximate location, thereby enabling the use of statistical analysis on the binned data to improve the accuracy of dependent measurements.
- diagnostic data can be provided or generated using poor resolution location data.
- the usefulness of diagnostic data is often related to the ability to associate the diagnostic data with the locations of the devices operating in the RF networks.
- Embodiments of the invention use probabilistic analysis to identify a location of a device.
- the location data enables the performance of an RF network to be characterized at the location or at the approximate location of the device.
- the location data and the associated location data generated by multiple devices can, for example, enable decisions to be made regarding whether a device is working properly, identify and rectify problem areas in networks, and specifically identify the problems or issues of the networks and/or the devices operating therein.
- the network and/or devices operating therein can be characterized in terms of ratings that reflect confidence in specific grid locations, confidence in the device, and confidence in the accuracy of the device.
- the information collected by a device and used to generate the diagnostic data can be temporarily stored on the device.
- Embodiments of the invention are described in the context of cellular telephones, but one of skill in the art can appreciate that other devices including pagers, laptop computers, personal digital assistants, or other devices that utilize wireless networks will also benefit from a characterization of the respective wireless network and from having their location in a wireless network identified or approximated.
- Embodiments of the invention can be applied to multiple types of wireless networks that may include, by way of example and not limitation, networks such as EVDO (Evolution Data Optimized) over 1x, WCDMA (Wideband Code Division Multiple Access) over GSM (Global System for Mobile Communications), 802.11, and the like or any combination thereof.
- networks such as EVDO (Evolution Data Optimized) over 1x, WCDMA (Wideband Code Division Multiple Access) over GSM (Global System for Mobile Communications), 802.11, and the like or any combination thereof.
- FIG. 1 illustrates an exemplary environment for implementing embodiments of the invention.
- FIG. 1 illustrates a wireless network 100 .
- the wireless network 100 may also include an interface to other networks including computer networks such as the Internet.
- the diagnostic data collected from devices operating in the wireless network 100 is often transmitted to a server computer or server system for analysis.
- the wireless network 100 includes multiple towers 102 , 103 , 104 , 106 and 108 that are positioned in the network 100 .
- the towers 102 , 103 , 104 , 106 , and 108 typically have more than one sector.
- a tower for example, may have three sectors that are configured to provide wireless coverage to certain areas.
- Wireless devices communicate with other devices in the network 100 and with devices in other networks through the sectors of the towers 102 .
- the tower 103 is an example of a tower that includes the antennas 112 , 114 , and 116 , each of which is associated with a corresponding sector.
- the towers 102 , 104 , 106 , and 108 may be similarly configured.
- the database may include, by way of example, the location of the tower (e.g., latitude and longitude), the azimuth of each antenna or sector, the down tilt of each antenna in each sector, and the type of antenna.
- a device such as the wireless device 110
- uses the wireless network 100 it typically communicates with one or more of the sectors on one or more towers.
- the device 110 may communicate or be detected by one or more antennas of one or more towers.
- the device 110 may communicate with sectors of the towers 104 , 106 , and 108 during use.
- the device 110 includes a diagnostic client that collects information related to the call made by the device 110 or related to the usage of the network 100 . This information may include, but is not limited to, RSSI (Received Signal Strength Indicator), which sectors of the network 100 were used for the device usage, EC/IO, noise margin, the fact that a call was made, whether the call was dropped and what type of call drop occurred.
- RSSI Receiveived Signal Strength Indicator
- the information provided or collected by the diagnostic client may also include timing or clock information from each or some of the sectors of the towers 104 , 106 , and 108 .
- the timing or clock information can be used to identify the location of the device 110 .
- the timing information from the device can include, by way of example, a timestamp from a sector of the tower 104 and a delta with respect to this timestamp from sectors of the towers 112 , and/or 114 based on the perceived differences between the clocks of the towers 104 , 112 , and 114 .
- the timestamp information can be used to locate the device 110 within the network 100 .
- FIG. 1 also illustrates that the network 100 may be represented by a grid 118 .
- Each location or bin 120 in the grid 118 corresponds to a physical or geographic area.
- each grid location or bin may correspond to 100 square meters or any other size.
- the information provided by the device 110 can be analyzed and associated with the grid locations or bins that correspond to the location and/or user of the device 110 .
- the diagnostic data collected from the devices operating in the network 100 can be collected according to device location.
- the diagnostic data collected from the devices is analyzed and contributed to the grid.
- the location data from device 110 determines which bins of the grid 118 receive the benefit of the data collected for or by the use of the device 110 . Because a cellular telephone is mobile, it is likely that the data from another use of the device will be contributed to different bins in the grid 118 . Further, the same device is likely to contribute to different bins over time as the device is used in different locations.
- the diagnostic data is contributed to the grid in a location based manner.
- location based diagnostic data is collected from multiple devices operating in the network 100 over time, the diagnostic data can provide a holistic, location based view of the performance of the network 100 .
- Embodiments of the invention use at least a part of the diagnostic data received from the device to generate an approximate location of the device in the network based on probabilities derived from the diagnostic information received from the devices operating in the wireless networks.
- FIG. 2 illustrates one example of locating a device in a wireless network using probabilities.
- the portion of the network 200 illustrated in FIG. 2 includes the towers 202 , 204 , and 206 .
- the towers 202 , 204 , and 206 generate timing data that can be received by the device 214 .
- the device 214 locks onto a sector of the tower 204
- the timing data received from the towers 202 and 206 may be described with reference to the timing data received from the tower 204 .
- the timing information generated by the device 214 may describe the timing data from the towers 202 and 206 in terms of offset from the tower 204 .
- the probability band 210 is defined by the path 209 , which can be drawn using the timing data between the towers 204 and 202 , for example.
- the probability band 212 is defined by the path 211 , which can be drawn using the timing data between the towers 204 and 206 , for example.
- the width of the probability bands can vary, but can be set to account for certain errors that may be represented in the timing data or in the data used to interpret the timing data. Multi-path reflections in the signal from a particular tower to the device 210 , inaccuracies in tower locations, an incorrect clock on the tower, and the like are examples of errors.
- the probability bands can account for these and other errors when determining the location of the device 214 .
- the probability bands 210 and 212 define a general area where the device 210 is presumed to be located.
- the probability bands are typically based on probabilities and may not rely on a precise measurement of the device's location.
- the probability band 210 overlaps with the probability band 212 to identify areas 208 and 216 in this example.
- the areas 216 (and other overlap areas of the probability bands, if any) can be ignored based on which sectors are in communication with the device 214 . For example, it is unlikely that a device in the area 216 is communicating with the tower 202 .
- the area 208 defines an approximate area or location of the device 214 in the network 200 . In this manner, the appropriate overlap area of the probability bands can be selected and used as the location or approximate location of the device.
- the area 208 is a probabilistic approximation of the location of the device 214 in the network 200 .
- the area 208 may be expressed as an ellipse in order to facilitate the representation of an approximate area in a concise form.
- the area 208 corresponds to one or more bins of a grid that represents the network 200 .
- the diagnostic location obtained from the device 214 can be contributed to the bins or grid locations that correspond to the area 208 .
- FIG. 3 illustrates a tower 302 in a wireless network 300 .
- the tower 302 includes, as previously indicated, three sectors associated with antenna 304 , 306 , and 308 , respectively.
- the location of the tower 302 is usually defined in terms of latitude and longitude.
- the sectors of the tower 302 may be identified using an azimuth, type, and/or a particular orientation (e.g., downtilt).
- the information that describes the characteristics or locations of a tower or sector may be provided in a database.
- the database may describe the latitude, longitude, azimuth, type, orientation, and the like or any combination thereof.
- the database can be accessed, for example, based on a sector identifier, etc. Thus, the location of the tower can be determined by accessing the database.
- a server When a server receives data such as timing data from a device, the server can access the database to obtain information about the towers or sectors included in the received data. The information about the towers or sectors and the data received from the device can be used to generate the approximate location of a device. The results of the location analysis can be used to resolve network issues if the diagnostic information indicates a certain problem. For example, the antenna downtilt can be altered or the antenna type changed.
- the general broadcast region of the antenna can be determined.
- the broadcast region 316 corresponds to the antenna 306 .
- a device operating in the network 300 can identify other parameters that can be used to identify its location within a broadcast region 316 .
- the received signal strength indicator (RSSI) and the signal to noise ratio are examples of information that can be used to identify a broadcast region.
- RSSI received signal strength indicator
- a strong RSSI suggests that the device is near the tower while a weak RSSI suggests that the device is further away from the tower.
- the device 310 is located within the broadcast region 316 .
- the device 310 likely has a strong RSSI with respect to the antenna 306 , but not with respect to the antennas 304 and 308 . This information can be included in diagnostic data and used in identifying the probable location of the device 310 .
- the device 312 in contrast, is near a virtual border 314 between the sector of the antenna 308 and the sector of the antenna 306 . It is likely that the device 312 communicates with both the antenna 306 and the antenna 308 . Because the device 312 is communicating with two antennas of the tower 302 , this information can be used to identify the location of the device as being near the border 314 .
- FIG. 3 illustrates that the broadcast region 316 of an antenna can be used alone or in conjunction with the broadcast regions of other antennas on the same tower to approximately identify a location of a device. In other words, it is likely that the broadcast regions of the antennas in a given tower have some overlap. When a device is communicating with more than one antenna or sector of the same tower, it is more likely than not that the device is located near the virtual border 314 . Once the location is approximated, the corresponding diagnostic data can be contributed or binned as described previously.
- FIG. 4 illustrates another example of approximating the location of a device in a wireless network using various combinations of probability bands and broadcast regions.
- FIG. 4 illustrates a portion of a network 400 that includes towers 402 and 406 in communication with a device 414 .
- the timing information collected by the device 414 can be used to generate the probability band 410 .
- the probability band 410 does not intersect with another probability band to determine an approximate location of the device 414 .
- the probability band 410 by itself defines a rather large area.
- one sector of the tower 402 has a broadcast region 406 that can be determined based on the tower's location, which sector the device 414 is communication with, and the azimuth of that sector.
- the broadcast region 408 of a particular sector in the tower 404 can also be determined.
- the intersection of the broadcast regions 406 and 408 can be used to approximate the location of the device 414 .
- the probability band 410 can also be included to further identify the location of the device 414 .
- the area 412 is defined by the intersection of the broadcast regions 406 , 408 and the probability band 410 .
- the device 414 is communicating with or aware of sectors from both towers 402 and 404 , it is likely that the device is located in the overlap of the corresponding broadcast regions. This area can be further refined by using the intersection of the probability band 410 and the broadcast regions 406 and 408 .
- FIG. 4 also illustrates the device 416 .
- the device 416 is located close to the tower 406 .
- the device 416 may not be able to communicate with other towers or sectors because the signal from sectors on tower 406 drown out other more distant sectors.
- the best location estimate for the device is one very close to tower 406 .
- This information in combination with the determination of the broadcast region 408 , can be used to determine that the device 416 is in the area 418 .
- the area 418 can be further determined, for example, using other information provided by the diagnostic client on the device 416 such as the RSSI, signal to noise ration, and the like.
- a device can be expected to be in communication with multiple sectors or towers—a high tower density.
- the tower density is low.
- the same device readings e.g., only having a single sector visible—are indicative the device can only communicate with a single sector or a single tower.
- Other towers or sectors are not visible to the device.
- One estimate of the device location when only a single sector or tower is visible is someplace near the center of the tower or sector broadcast region.
- the center point or other point of the sector can be selected as the approximate location of the device. Because of the lower tower density, the estimation of the accuracy of the location may also be low.
- the density of towers or of sectors is another example of input used to approximate the location of a device in a network.
- the tower 402 has the broadcast region 406 for one sector and the broadcast region 424 for another sector.
- a device 422 that communicates with the sectors associated with the broadcast regions 406 and 424 can be located by the area 420 that defines the overlap between the broadcast region 406 and the broadcast region 424 .
- the process of approximating the location of a device can be reversed.
- the location data or probabilities can be pre-computed and compared with data received from devices.
- a bin in the grid or a group of bins can have expected data or probabilities pre-computed with regard at least to location.
- a bin or group of bins for example, may have pre-computed probability bands, broadcast regions, RSSI, signal to noise ration, etc.
- a best fit analysis can be applied to the diagnostic data to identify the location of a device in a network.
- the location can be immediately narrowed to the areas surrounding using the towers or sectors that are in communication with the device or that the device is aware of.
- FIG. 5 illustrates a grid that corresponds to a wireless network.
- the locations of the towers 502 are indicated on the grid 500 .
- a device 504 is located within the network represented by the grid 500 .
- the probabilistic data described above can be pre-computed for each bin or at least for some of the bins in the grid 500 .
- the server would expect to receive certain diagnostic data from the device 504 .
- the expected data can be pre-computed based on tower locations, sector azimuth, antenna tilt, expected RSSI or signal to noise ration based on location of bin with respect to the towers 502 , and the like or any combination thereof.
- the expected diagnostic data could include the timing information from the relevant towers 502 , RSSI and the like.
- the diagnostic data actually received from the device 504 is compared with the expected diagnostic data until a best fit is achieved. When the best fit is achieved, the location of the device can then be determined or approximated based on the location of the bins that fit the diagnostic data provided by the device.
- inaccuracies in the network can be determined. For example, if the diagnostic data from multiple devices consistently fits with two out of three towers, it may be an indication that the presumed location or other aspect of the third tower is incorrect. It could also suggest that maintenance may be required for the third tower. It could also be an indication that the information describing the location or other aspect of the third tower is incorrect. This information can then be used to improve the grid performance as well as improve the performance of the wireless network.
- information describing towers is often stored externally in a database. If the diagnostic data indicates that the location of the tower is incorrect, it is possible that the information in the database describing the location is incorrect. Thus, it may be that the database is the source of errors. A correction to the database can then be made.
- the information may also indicate that an antenna has become disoriented and may require correction.
- the database may reflect the appropriate azimuth or downtilt of a particular antenna. However, the location data suggests another azimuth or downtilt. This antenna could then be adjusted accordingly to correct any resulting errors in the approximation of the location data.
- the diagnostic data can reflect clutter in the wireless network.
- the actual data that is binned is representative of multi-path reflections, the presence of buildings or other things that can interfere with a wireless signal, and the like.
- this information can be used for planning purposes and the like. This type of information can be used to prioritize issues in the network that may need to be resolved.
- the binned diagnostic data can be used for other purposes as well. For instance, many simulations are typically performed before a wireless network is deployed. Unfortunately, these simulations often do not have an accurate representation of the clutter that may be present in a given network.
- the data collected and/or produced by embodiments of the invention can be used in the simulations to account for clutter.
- the results of the network simulations can be improved because real location based diagnostic data is used to simulate clutter. As a result, the locations of new towers or the adjustment of existing towers can be made to improve the wireless network based on these simulations.
- the probability bands identify an area where the device is presumed to be located.
- the probability band may encompass more than one bin as described in FIG. 1 .
- the diagnostic data can be contributed to more than one bin or more particularly, to each of the bins that correspond to the approximated area.
- the contribution to the various bins can be weighted as well based on the location of the bins within the approximated area. As noted above, the device is less likely to be located at the perimeter of the approximated area. Thus, bins that are located in these areas receive less of a contribution from a particular user.
- FIG. 6 illustrates another aspect of using location data in conjunction with diagnostic data.
- certain data used to generate the location of the device 602 can be collected by a device 602 and stored in the memory 604 of the device 602 .
- This data may include clock data from multiple sectors, RSSI data, noise margin, and the like.
- GPS data may also be collected by the device.
- Some of the information (tower/sector location, etc.) used to compute the location of the device can be stored remotely or transmitted to the device.
- FIG. 6 illustrates a database 612 that can be used by the server to store information or from which the server 610 may access information.
- the database 612 is intended to represent one or more databases. Further, the databases may be independent of each other and may be maintained by different entities.
- the device 602 can collect pertinent information and store the collected information in the memory 604 .
- the collected information, or the diagnostic data can then be transmitted to the server 610 or other system at any time.
- the device 602 can store and forward the diagnostic data at any time. This enables the device 602 to transmit at off-peak times or to transmit a batch of data at the same time, and the like.
- the device 606 which represents other devices operating in the wireless network, can also store and forward diagnostic data to the server 610 .
- the device may store the diagnostic data until it is requested by the server 610 , at which point the data is forwarded to the server 610 .
- the server 610 can then compute the location of the device 602 and add the collected data to the database 612 according to the computed location as described herein.
- the database 612 can represent an overview of the performance of the network from specific locations within the network. This information has many advantages from being able to identify the cause of an event, identify problem areas of a network, model clutter of a geographic area, identify ideal locations for new towers, and the like or any combination thereof.
- the output 614 of the server 610 represents the content of the database 612 as applied to various problems.
- the database 612 can provide information that indicates whether the location of the device 602 has a history of dropped calls. This may suggest that the network has poor coverage in this location.
- the content of the database 612 can be used to evaluate the performance of the wireless network or of devices operating in the wireless network.
- the content of the database 612 can also be used to prioritize network improvements, the deployment of new or replacement towers, and the like.
- the database 612 stores information describing factors or characteristics of towers and sectors of a wireless network.
- the server 610 can use the information to access the database 612 and obtain information describing the towers or sectors that were in communication with the device.
- the information may include, but is not limited to, location (e.g., latitude, longitude, and/or elevation), azimuth, antenna type, sectors, number of sectors, orientation, manufacturer, and the like or any combination thereof. This information can be used in generating the output 614 as described herein.
- the database 612 or other external database can provide information that is useful in identifying a location of a device or an approximate location of the device.
- accessing the database for this type of information is not always straight forward because the information needed to properly identify a particular sector or tower may be missing, truncated, corrupt, and the like.
- a database which may be an external database
- wireless protocols frequently use identification information for different sectors that is significantly truncated to minimize the amount of data transferred over the air.
- some carriers do not consistently populate data fields that are intended to uniquely identify radio sectors. As a result, it is sometimes necessary to find a closest match within the database to the information provided by the device.
- sectors broadcast their latitude and longitude, which when combined with their frequency and other identifying information provides a unique match in the database.
- the sector broadcasts a unique identification number or code, which can also be used to associate information from the database with the information received from devices operating in the network.
- PN Code defines the pseudo random noise code utilized to encode the data transmitted by the sector. This value is locally unique (only one sector in a give region can use this value).
- the PN Code is another example of information that can be collected by a device and received by a server when identifying or approximating the location of a device.
- the PN Code can be the data used to help associate the information received from the device with proper records in a database to retrieve additional information about the sector(s) communicating with the device.
- a unique match can frequently be determined.
- the relevant information can be used by the server to identify or approximate the location of the device.
- a partial match can still be used.
- the server typically analyzes the resulting location data to make sure that it makes sense in the context of the other information collected by the device. For instance, if the retrieved location associated with a partial match is too far away from the device to be a primary sector, then the partial match is discarded.
- FIG. 7 illustrates an example of a method for identifying or for approximating the location of a device or of multiple devices in a network.
- a server operating in a network receives 702 diagnostic data from at least one device operating in the network.
- the diagnostic data received from the device includes information that describes or identifies aspects of the device and/or of the network in which the device operates.
- the diagnostic data can include information that is received from radio elements such as towers or sectors that communicate with the device at any given time or during a particular event.
- the information may include sector identifiers or partial sector identifiers, latitude, longitude, PN Codes, and the like. This information is typically provided at least for the primary sector as well as for other sectors visible to the device.
- the diagnostic data can also include information describing or related to the device as described herein.
- the server may access a database to retrieve additional information related to the sectors or other radio elements in the network that may have communicated with the device.
- the server ensures that the information accessed from the database is correct and is a match for the diagnostic data received from the device. Proper identification of the sectors ensures that the approximated location of the device is accurate and useful, for example, when contributing the device's data to bins of a grid.
- accessing the database includes associating the diagnostic data with correct sector information. Accessing the database may also include performing steps to insure that the match is correct. This can be done by comparing latitude and/or longitude information, PN codes, and the like.
- the server is able to generate one or more probability bands. These probability bands may include broadcast regions. A particular area is then identified as the location or approximate location of the device. Typically, the area identified is where the probability bands overlap. If more than one overlap is present, one of them is usually discarded. Next, the diagnostic data can be processed and contributed to the bins associated with the identified area.
- inventions described herein may include the use of a special purpose or general-purpose computer including various computer hardware or software modules, as discussed in greater detail below.
- Embodiments within the scope of the present invention also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon.
- Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer.
- Such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
- Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
- module can refer to software objects or routines that execute on the computing system.
- the different components, modules, engines, and services described herein may be implemented as objects or processes that execute on the computing system (e.g., as separate threads). While the system and methods described herein are preferably implemented in software, implementations in hardware or a combination of software and hardware are also possible and contemplated.
- a “computing entity” may be any computing system as previously defined herein, or any module or combination of modulates running on a computing system.
Abstract
Description
Claims (33)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/777,942 US7783303B1 (en) | 2006-07-14 | 2007-07-13 | Systems and methods for locating device activity in a wireless network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US80743506P | 2006-07-14 | 2006-07-14 | |
US11/777,942 US7783303B1 (en) | 2006-07-14 | 2007-07-13 | Systems and methods for locating device activity in a wireless network |
Publications (1)
Publication Number | Publication Date |
---|---|
US7783303B1 true US7783303B1 (en) | 2010-08-24 |
Family
ID=42583389
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/777,942 Active 2029-05-06 US7783303B1 (en) | 2006-07-14 | 2007-07-13 | Systems and methods for locating device activity in a wireless network |
Country Status (1)
Country | Link |
---|---|
US (1) | US7783303B1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100085893A1 (en) * | 2008-07-10 | 2010-04-08 | Electronics And Telecommunications Research Institute | Sensor nodes in multiple sensor network, method for creating grid-based tree of sensor nodes and spatial query processing system using grid-based tree |
US20100223283A1 (en) * | 2007-11-09 | 2010-09-02 | Electronics And Telecommunications Research Institute | Apparatus and method for processing query |
US20110153808A1 (en) * | 2009-12-22 | 2011-06-23 | Jungsub Byun | Method and system for providing a performance report in a wireless network |
US20110319093A1 (en) * | 2009-01-13 | 2011-12-29 | Michael Joseph Flanagan | Geo-location in a wireless communication network |
WO2012121632A1 (en) * | 2011-03-07 | 2012-09-13 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and arrangements for handling positioning in a radio communication system |
US20140171105A1 (en) * | 2012-12-14 | 2014-06-19 | Andrew, Llc | Enhanced Cell ID Location Method Using Non Uniform Subsectors and Neighboring Cell Centroid |
US9119034B2 (en) | 2013-11-21 | 2015-08-25 | At&T Mobility Ii Llc | Method and apparatus for determining a probability for a geo-fence |
US9674656B2 (en) | 2014-02-20 | 2017-06-06 | Microsoft Technology Licensing, Llc | Wireless-based localization using a zonal framework |
US9998876B2 (en) * | 2016-07-27 | 2018-06-12 | At&T Intellectual Property I, L.P. | Inferring user equipment location data based on sector transition |
US10219115B2 (en) | 2015-11-20 | 2019-02-26 | At&T Intellectual Property I, L.P. | Facilitation of mobile device geolocation |
Citations (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5889474A (en) | 1992-05-18 | 1999-03-30 | Aeris Communications, Inc. | Method and apparatus for transmitting subject status information over a wireless communications network |
US6052598A (en) * | 1997-09-30 | 2000-04-18 | At&T Corp | Method for predicting the location of a mobile station in a mobile communications network |
US6097336A (en) | 1999-01-08 | 2000-08-01 | Trueposition, Inc. | Method for improving the accuracy of a wireless location system |
US6167358A (en) | 1997-12-19 | 2000-12-26 | Nowonder, Inc. | System and method for remotely monitoring a plurality of computer-based systems |
US6205326B1 (en) | 1998-06-10 | 2001-03-20 | Motorola, Inc. | Method for determining when a communication unit is located within a preferred zone |
US6263208B1 (en) * | 1999-05-28 | 2001-07-17 | Lucent Technologies Inc. | Geolocation estimation method for CDMA terminals based on pilot strength measurements |
US6266788B1 (en) | 1998-07-01 | 2001-07-24 | Support.Com, Inc. | System and method for automatically categorizing and characterizing data derived from a computer-based system |
US20020072359A1 (en) | 2000-12-08 | 2002-06-13 | Moles Bryan J. | System and method for performing diagnostics on a mobile station using over-the-air transfer of interpreted byte-code program |
US6516198B1 (en) | 1999-12-06 | 2003-02-04 | Tendler Cellular Inc | System for location reporting |
US6529136B2 (en) | 2001-02-28 | 2003-03-04 | International Business Machines Corporation | Group notification system and method for implementing and indicating the proximity of individuals or groups to other individuals or groups |
US20030054813A1 (en) * | 2001-09-10 | 2003-03-20 | Wyatt Riley | System and method for identification of transmitters with limited information |
US20030159088A1 (en) | 2002-02-20 | 2003-08-21 | Microsoft Corporation | System and method for gathering and automatically processing user and debug data for mobile devices |
US6745011B1 (en) | 2000-09-01 | 2004-06-01 | Telephia, Inc. | System and method for measuring wireless device and network usage and performance metrics |
US6754470B2 (en) | 2000-09-01 | 2004-06-22 | Telephia, Inc. | System and method for measuring wireless device and network usage and performance metrics |
US20050020278A1 (en) * | 2003-07-22 | 2005-01-27 | Krumm John C. | Methods for determining the approximate location of a device from ambient signals |
US6889053B1 (en) * | 1999-07-26 | 2005-05-03 | Lucent Technologies Inc. | Likelihood-based geolocation prediction algorithms for CDMA systems using pilot strength measurements |
US20050246334A1 (en) * | 2004-04-30 | 2005-11-03 | Hong Kong Applied Science And Technology Research Institute Co., Ltd. | Location determination and location tracking in wireless networks |
US20060007901A1 (en) | 2004-07-08 | 2006-01-12 | Steve Roskowski | Rule based data collection and management in a wireless communications network |
US20060007870A1 (en) | 2004-07-08 | 2006-01-12 | Steve Roskowski | Collection of data at target wireless devices using data collection profiles |
US20060023642A1 (en) | 2004-07-08 | 2006-02-02 | Steve Roskowski | Data collection associated with components and services of a wireless communication network |
US7006988B2 (en) * | 2000-12-18 | 2006-02-28 | Mitac International Corp. | Method of collaboration commerce |
US20070270160A1 (en) * | 2006-05-19 | 2007-11-22 | Karl Georg Hampel | Traffic-synchronized location measurement |
US20080191844A1 (en) * | 2003-12-10 | 2008-08-14 | Barry Allen | Method and apparatus for resolving RFID-based object traffic transactions to a single object in the presence of a plurality of objects |
US20090300763A1 (en) * | 2003-04-03 | 2009-12-03 | Network Security Technologies, Inc. | Method and system for detecting characteristics of a wireless network |
-
2007
- 2007-07-13 US US11/777,942 patent/US7783303B1/en active Active
Patent Citations (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5889474A (en) | 1992-05-18 | 1999-03-30 | Aeris Communications, Inc. | Method and apparatus for transmitting subject status information over a wireless communications network |
US6052598A (en) * | 1997-09-30 | 2000-04-18 | At&T Corp | Method for predicting the location of a mobile station in a mobile communications network |
US6167358A (en) | 1997-12-19 | 2000-12-26 | Nowonder, Inc. | System and method for remotely monitoring a plurality of computer-based systems |
US6205326B1 (en) | 1998-06-10 | 2001-03-20 | Motorola, Inc. | Method for determining when a communication unit is located within a preferred zone |
US6266788B1 (en) | 1998-07-01 | 2001-07-24 | Support.Com, Inc. | System and method for automatically categorizing and characterizing data derived from a computer-based system |
US6097336A (en) | 1999-01-08 | 2000-08-01 | Trueposition, Inc. | Method for improving the accuracy of a wireless location system |
US6263208B1 (en) * | 1999-05-28 | 2001-07-17 | Lucent Technologies Inc. | Geolocation estimation method for CDMA terminals based on pilot strength measurements |
US6889053B1 (en) * | 1999-07-26 | 2005-05-03 | Lucent Technologies Inc. | Likelihood-based geolocation prediction algorithms for CDMA systems using pilot strength measurements |
US6516198B1 (en) | 1999-12-06 | 2003-02-04 | Tendler Cellular Inc | System for location reporting |
US6745011B1 (en) | 2000-09-01 | 2004-06-01 | Telephia, Inc. | System and method for measuring wireless device and network usage and performance metrics |
US6754470B2 (en) | 2000-09-01 | 2004-06-22 | Telephia, Inc. | System and method for measuring wireless device and network usage and performance metrics |
US20020072359A1 (en) | 2000-12-08 | 2002-06-13 | Moles Bryan J. | System and method for performing diagnostics on a mobile station using over-the-air transfer of interpreted byte-code program |
US7006988B2 (en) * | 2000-12-18 | 2006-02-28 | Mitac International Corp. | Method of collaboration commerce |
US6529136B2 (en) | 2001-02-28 | 2003-03-04 | International Business Machines Corporation | Group notification system and method for implementing and indicating the proximity of individuals or groups to other individuals or groups |
US20030054813A1 (en) * | 2001-09-10 | 2003-03-20 | Wyatt Riley | System and method for identification of transmitters with limited information |
US20030159088A1 (en) | 2002-02-20 | 2003-08-21 | Microsoft Corporation | System and method for gathering and automatically processing user and debug data for mobile devices |
US20090300763A1 (en) * | 2003-04-03 | 2009-12-03 | Network Security Technologies, Inc. | Method and system for detecting characteristics of a wireless network |
US20050020278A1 (en) * | 2003-07-22 | 2005-01-27 | Krumm John C. | Methods for determining the approximate location of a device from ambient signals |
US20080191844A1 (en) * | 2003-12-10 | 2008-08-14 | Barry Allen | Method and apparatus for resolving RFID-based object traffic transactions to a single object in the presence of a plurality of objects |
US20050246334A1 (en) * | 2004-04-30 | 2005-11-03 | Hong Kong Applied Science And Technology Research Institute Co., Ltd. | Location determination and location tracking in wireless networks |
US20060023642A1 (en) | 2004-07-08 | 2006-02-02 | Steve Roskowski | Data collection associated with components and services of a wireless communication network |
US20060007870A1 (en) | 2004-07-08 | 2006-01-12 | Steve Roskowski | Collection of data at target wireless devices using data collection profiles |
US20060007901A1 (en) | 2004-07-08 | 2006-01-12 | Steve Roskowski | Rule based data collection and management in a wireless communications network |
US20070270160A1 (en) * | 2006-05-19 | 2007-11-22 | Karl Georg Hampel | Traffic-synchronized location measurement |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100223283A1 (en) * | 2007-11-09 | 2010-09-02 | Electronics And Telecommunications Research Institute | Apparatus and method for processing query |
US20100085893A1 (en) * | 2008-07-10 | 2010-04-08 | Electronics And Telecommunications Research Institute | Sensor nodes in multiple sensor network, method for creating grid-based tree of sensor nodes and spatial query processing system using grid-based tree |
US9900784B2 (en) | 2009-01-13 | 2018-02-20 | Viavi Solutions Uk Limited | Geo-location in a wireless communication network |
US20110319093A1 (en) * | 2009-01-13 | 2011-12-29 | Michael Joseph Flanagan | Geo-location in a wireless communication network |
US9462482B2 (en) * | 2009-01-13 | 2016-10-04 | Viavi Solutions Uk Limited | Geo-location in a wireless communication network |
US20110153808A1 (en) * | 2009-12-22 | 2011-06-23 | Jungsub Byun | Method and system for providing a performance report in a wireless network |
WO2012121632A1 (en) * | 2011-03-07 | 2012-09-13 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and arrangements for handling positioning in a radio communication system |
US20140171105A1 (en) * | 2012-12-14 | 2014-06-19 | Andrew, Llc | Enhanced Cell ID Location Method Using Non Uniform Subsectors and Neighboring Cell Centroid |
US9176216B2 (en) * | 2012-12-14 | 2015-11-03 | Maple Acquisition Llc | Enhanced cell ID location method using non uniform subsectors and neighboring cell centroid |
US9119034B2 (en) | 2013-11-21 | 2015-08-25 | At&T Mobility Ii Llc | Method and apparatus for determining a probability for a geo-fence |
US9473889B2 (en) | 2013-11-21 | 2016-10-18 | At&T Mobility Ii Llc | Method and apparatus for determining a probability for a geo-fence |
US9674656B2 (en) | 2014-02-20 | 2017-06-06 | Microsoft Technology Licensing, Llc | Wireless-based localization using a zonal framework |
US10219115B2 (en) | 2015-11-20 | 2019-02-26 | At&T Intellectual Property I, L.P. | Facilitation of mobile device geolocation |
US9998876B2 (en) * | 2016-07-27 | 2018-06-12 | At&T Intellectual Property I, L.P. | Inferring user equipment location data based on sector transition |
US10595164B2 (en) | 2016-07-27 | 2020-03-17 | At&T Intellectual Property I, L.P. | Inferring user equipment location data based on sector transition |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7783303B1 (en) | Systems and methods for locating device activity in a wireless network | |
EP2118810B1 (en) | System and method for optimizing location estimate of mobile unit | |
CN1751248B (en) | Use of mobile stations for determination of base station location parameters in a wireless mobile communication system | |
US7715849B2 (en) | User positioning | |
US7663540B2 (en) | Server device, mobile terminal and positioning mode selecting method | |
EP2553990B1 (en) | Method and apparatus for use of performance history data in positioning method selection | |
US9369845B2 (en) | Methods and systems of assigning estimated positions and attributes to wireless access points in a positioning system | |
US8364164B2 (en) | Cell ID based positioning from cell intersections | |
US7865194B2 (en) | Systems and methods for characterizing the performance of a wireless network | |
US20030125045A1 (en) | Creating and using base station almanac information in a wireless communication system having a position location capability | |
US9402188B2 (en) | Geo-location error correction for small cell placement | |
CN109471134B (en) | Automatic calibration of geolocation analysis system and operator network equipment parameters | |
WO2007121375A2 (en) | Systems and methods for characterizing the performance of a wireless network | |
CN109803273A (en) | Antenna-feeder system method of adjustment, device, electronic equipment and storage medium | |
JP2012029053A (en) | Measurement control device, measurement system, measurement control method, and program | |
KR101495503B1 (en) | Method for Estimating Azimuth, Apparatus And Computer-Readable Recording Medium with Program Therefor | |
CN106796277B (en) | Location adjustment in a mobile communication network | |
CN116801378A (en) | User resident location mining method and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CARRIER IQ, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LERNER, YISHAI;ROSKOWSKI, STEVE;REEL/FRAME:019559/0913 Effective date: 20070711 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: AT&T MOBILITY IP, LLC, GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CARRIER IQ, INC.;REEL/FRAME:037576/0085 Effective date: 20151118 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |