Aggregate location dynometer (ALD)

Information

  • Patent Grant
  • 9402158
  • Patent Number
    9,402,158
  • Date Filed
    Friday, October 16, 2015
    9 years ago
  • Date Issued
    Tuesday, July 26, 2016
    8 years ago
Abstract
An Aggregate Location Dynometer (ALD) in a physical wireless network alerts to a problematic crowd risk using location based services (LBS). An Aggregate Location Dynometer (ALD) comprises a Network Monitor, a Crowd Risk Determinant and an Alert Module. The Network Monitor monitors wireless traffic for a potential viral event, associated with a formation of a plurality of wireless devices. The Crowd Risk Determinant requests location information associated with a plurality of wireless devices in a given area regarding a respective viral event. The Crowd Risk Determinant determines if the viral event also indicates a crowd safety risk, based on the shape and movement of observed wireless devices. The Alert Module triggers an alert of an impending crowd problem when crowd risk is above a given threshold. Historical databases are empirically determined and maintained in the Aggregate Location Dynometer (ALD) for use in viral event and crowd risk assessment.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to wireless telecommunications. More particularly, it relates to cell location services, cell network trafficking and analysis of location information.


2. Background of Related Art


Location based applications obtain a geographic position of a particular wireless device and provide services accordingly. Location based services (LBS) prevail in today's market due to an incorporation of tracking technology in handheld devices.


Location based pull services allow a wireless device user to locate another wireless device. Current location services are generally focused on individual wireless device user applications.


SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a method of alerting to a problematic crowd risk in a given geographical location, comprises an Aggregate Location Dynometer (ALD). The Aggregate Location Dynometer (ALD) utilizes location based services (LBS) to analyze aggregate location information pertaining to a multitude of wireless devices, to detect potential crowd risks.


An Aggregate Location Dynometer (ALD) resides in a physical network server, in accordance with the present invention, and comprises three main components: a Network Monitor, a Crowd Risk Determinant, and an Alert Module.


The Network Monitor monitors a wireless network for indication of a possible impending viral event, in accordance with the principles of the present invention. In particular, the Network Monitor utilizes location based services (LBS) to monitor the formation of a plurality of wireless devices at a given point in a wireless network, e.g., a given base station (BS). The Network Monitor compares obtained traffic parameters pertaining to monitored wireless traffic, with historical traffic parameters having to do with crowd risk determination, to determine if a viral event may be occurring or impending. A snapshot look at current location data collected by the Network Monitor is subsequently logged in an appropriate historical database.


In accordance with the principles of the present invention, the Crowd Risk Determinant analyzes location information to determine if a viral event triggered by the Network Monitor, also indicates a crowd safety risk. In particular, the Crowd Risk Determinant initiates a location request to obtain location information pertaining to a multitude of wireless devices in a given area, regarding a viral event that has been triggered by the Network Monitor. The Crowd Risk Determinant compares the viral pattern formed by the shape and movement of wireless devices in locations observed, with predetermined risk rules to determine if the viral event is also a crowd safety risk. The observed viral pattern is subsequently logged in an appropriate historical database.


The Alert Module, in accordance with the principles of the present invention, alerts proper authorities in an event of a crowd safety risk. The Crowd Risk Determinant triggers the Alert Module to alert of an impending crowd problem when crowd risk has exceeded a given threshold.


The Aggregate Location Dynometer (ALD) utilizes historical databases, in accordance with the present invention, to maintain location-based information indicating possible viral events associated with a plurality of wireless devices. Historical databases include an Acceptable/Non-Acceptable Crowd Shape database, a Configurable Parameter Threshold database, a Historical Wireless Device Location Trends database, and a Risk Rules database.





BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which:



FIG. 1 depicts an exemplary Aggregate Location Dynometer (ALD), in accordance with the principles of the present invention.



FIG. 2 depicts the flow of an exemplary Network Monitor of the Aggregate Location Dynometer (ALD), in accordance with the principles of the present invention.



FIG. 3 depicts the flow of an exemplary Crowd Risk Determinant of the Aggregate Location Dynometer (ALD), in accordance with the principles of the present invention.



FIG. 4 depicts the flow of an exemplary Alert Module of the Aggregate Location Dynometer (ALD), in accordance with the principles of the present invention.



FIG. 5 denotes first exemplary Aggregate Location Dynometer (ALD) location results, in accordance with the principles of the present invention.



FIG. 6 denotes second exemplary Aggregate Location Dynometer (ALD) location results, in accordance with the principles of the present invention.



FIG. 7 denotes third exemplary Aggregate Location Dynometer (ALD) location results, in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Thus far, location capabilities have been concerned with locating an individual wireless device. Yet, there is such a vast abundance of individuals populating the nation's major cities. The present inventor has appreciated the benefits of using location based services (LBS) to obtain sets of aggregate location data corresponding to a number and pattern of wireless devices within an area, region, city, etc. of interest.


The present invention introduces an Aggregate Location Dynometer (ALD), an analytical server utilizing location based services (LBS) on a network to predict public safety risks, e.g., the unexpected impending formation of a flash mob, or a riot, etc.


The Aggregate Location Dynometer (ALD) analyzes a bird's-eye view of people formation, presuming those individuals possess respective handheld wireless devices that permit collection of current location information, whether that current location information be obtained from the wireless devices themselves, and/or from a network-based location server.


In accordance with the principles of the present invention, the Aggregate Location Dynometer (ALD) predicts public safety risk in a given geographical area through evaluation of the positioning and movement of wireless devices. The Aggregate Location Dynometer (ALD) monitors wireless device network traffic to predict an impending viral event. If a possible impending viral event is sensed from a general monitoring of wireless traffic, the Aggregate Location Dynometer (ALD) may request impending viral location information pertaining to clusters of wireless devices in a vicinity of the possible event, to more accurately assess crowd risk.


Crowd risk is assessed based upon given wireless network traffic parameters such as the number of wireless devices in communication with a given base station (e.g., a density), the shape formed by representations of the individual locations of the densest areas where active wireless devices are currently located, and/or the movement of the wireless devices within the region as defined.


Markers, each representing a wireless device at a given location at a given time, may be displayed on a display of the Aggregate Location Dynometer (ALD). The markers may represent wireless devices served within the given region, whether actively communicating with another wireless device, or merely sensed as present.


The present invention preferably provides an alert of a possible impending crowd related public safety risk in real time, as the crowd risk arises, informing emergency personnel as early as possible, even before such event is consummated.



FIG. 1 depicts an exemplary Aggregate Location Dynometer (ALD) 400, in accordance with the principles of the present invention.


In particular, an Aggregate Location Dynometer (ALD) 400 determines crowd safety risk with the help of location based services (LBS) 318, as depicted in FIG. 1.


The Aggregate Location Dynometer (ALD) 400 is generally based in a server in a wireless network 322. Three main components form the Aggregate Location Dynometer (ALD) 400: a Network Monitor 302, a Crowd Risk Determinant 304, and an Alert Module 306.


The Network Monitor 302 begins the risk determination process of the Aggregate Location Dynometer (ALD) 400 by monitoring the network for indication of a possible viral event, in accordance with the principles of the present invention. Determination of a viral event is the first step in the escalation-based response of the Aggregate Location Dynometer (ALD) 400.


The Crowd Risk Determinant 304 assesses location information pertaining to a possible viral event triggered by the Network Monitor 302. The Crowd Risk Determinant 304 determines if a viral event also indicates a public safety risk.


The Alert Module 306 performs predetermined responsive measures to alert appropriate public safety personnel 320 in the event of a possible or probable or current public safety risk.


Historical databases are empirically determined and maintained in the Aggregate Location Dynometer (ALD) 400 for use in crowd risk assessment. The historical databases preferably store sets of aggregate current location information pertaining to trackable wireless devices. Exemplary historical databases accessible by the Aggregate Location Dynometer (ALD) 400 include but are not limited to a Historical Wireless Device Location Trends and Statistics database 312, a Configurable Parameter Threshold database 310, a Risk Rules database 314, and an Acceptable/Non-Acceptable Crowd Shape database 308.


The Historical Wireless Device Location Trends and Statistics database 312, as shown in FIG. 1, preferably stores sets of instantaneous aggregate location information obtained over a period of time. Data stored in the Historical Wireless Device Location Trends and Statistics database 312 provides empirical evaluation of crowd activities used to detect a crowd trend. The Aggregate Location Dynometer (ALD) 400 preferably uses data stored in the Historical Wireless Device Location Trends and Statistics database 312 to determine if a current situation is considered to be ‘normal’ to the monitored area, or abnormal, triggering a viral event. The data maintained in the Historical Wireless Device Location Trends and Statistics database 312 is preferably refreshed over time.


The Configurable Parameter Threshold database 310, as depicted in FIG. 1, preferably comprises a set of configurable location-based parameters and thresholds including density, clustering, spread, geographical boundary, motion trends, and/or special events occurring in particular areas. The Configurable Parameter Threshold database 310 can also include non-location based parameters such as time of day and/or message content. The parameters stored in the Configurable Parameter Threshold database 310 are accessed by the Network Monitor 302 to assist in detecting a viral event.


The Risk Rules database 314, as shown in FIG. 1, preferably comprises a set of configurable location-based parameters and thresholds including density, clustering, spread, geographical boundary, motion trends, and/or special events occurring in particular areas. The Risk Rules database 314 can also include non-location based parameters such as time of day and/or message content. The parameters stored in the Risk Rules database 314 are accessed by the Crowd Risk Determinant 304 to assist in determining if a viral event also indicates a public safety risk.


The Acceptable/Non-Acceptable Crowd Shape database 308, as shown in FIG. 1, holds empirically determined past, historical cluster information regarding acceptable and/or non-acceptable past shape formations of clustered wireless devices. Specific shape parameters stored in the Acceptable/Non-Acceptable Crowd Shape database 308 are accessed by the Crowd Risk Determinant 304 to assist in determining if a viral event also indicates a public safety risk.


A viral event is the first state of alarm in the multi-state risk determination process of the Aggregate Location Dynometer (ALD) 400. A viral event is defined as occurring when one or more predefined parameter thresholds have been surpassed, as determined in the exemplary embodiment in the Network Monitor 302. The occurrence of a viral event does not necessarily infer a definite public safety risk. Instead, a viral event triggers the Crowd Risk Determinant 304 to further analyze a potentially malignant event more closely. For example, the Crowd Risk Determinant 304 provides a closer inspection of aggregate current location information, e.g., via use of a location-based push/pull service. A match of more detailed location information to a historical pattern leading to crowd risk may determine that a particular viral event also indicates a likely public safety risk.


A public safety risk confirms a compromise in crowd safety, e.g., the impending formation of a flash mob, or a riot, etc. Determination of a public safety risk triggers the Alert Module 306 to implement proper public safety response services.


The Network Monitor 302 begins the risk determination process of the Aggregate Location Dynometer (ALD) 400, by monitoring the network for indication of a possible viral event, in accordance with the principles of the present invention.


Moreover, the Network Monitor 302 retrieves subsequent sets of instantaneous aggregate location information. Location information triggered by the Network Monitor 302 may be portrayed in the form of snapshots displayed on a display of the Aggregate Location Dynometer (ALD) 400. Snapshots by the Network Monitor 302 comprise markers, each representing the location of individual wireless devices within a given region being monitored.


The Network Monitor 302 preferably obtains information regarding the number of wireless devices in a geographical area, at a given time, supported by a particular wireless network carrier (e.g., the number of wireless devices sending messages over a wireless network via a particular base station (BS) 324). The Network Monitor 302 uses predefined parameters and thresholds to determine if the monitored network indicates that a viral event may be occurring or impending (e.g., surpassed parameter thresholds possibly indicative of an excessive number and/or use of wireless devices for a given area, cell tower, etc.).


For instance, a Maximum Number of Devices parameter may indicate the maximum number of wireless devices that may be present within range of a particular base station (BS) 324 at a given time before a possible viral event is triggered. The Maximum Number of Devices parameter may be set manually, or empirically determined (e.g., the average number of devices present at a particular base station (BS) 324 over a course of time, as determined by historical data stored in the Historical Wireless Device Location Trends and Statistics database 312).


The Network Monitor 302 triggers a possible viral event if a predefined parameter threshold has been surpassed (e.g., a given density of current location markers each representing a separate wireless device, or a directed convergence of at least two highly dense clusters of markers toward each other at a significant rate of speed is or has occurred, etc.).


The Network Monitor 302 preferably tallies the number of wireless devices in each instantaneous aggregate location snapshot that is captured. Predetermined parameters and thresholds are used to assess the number (e.g., the density) of wireless devices in a particular area to determine whether or not a possible viral event is occurring.


The Maximum Number of Devices parameter may alternatively be set to indicate the maximum number of wireless devices that may be present in an instantaneous aggregate location snapshot before a possible viral event is triggered. If the number of devices present in a given snapshot exceeds the Maximum Value of Devices parameter established for the respective location, a viral event may be triggered.


The Network Monitor 302 also preferably tallies the difference in the number of wireless devices in a given area, from one consecutive instantaneous aggregate location snapshot to the next. If the difference in the number of wireless devices from snapshot to snapshot exceeds a predefined value in a number of consecutive snapshots for a given area, base station, etc., then a viral event may be triggered. Thresholds for such a predefined Maximum Difference in Number of Wireless Devices parameter and a predefined Interval of Consecutive Snapshots parameter may be set manually, or empirically determined (e.g., the average difference in number of devices in consecutive instantaneous aggregate location snapshots capturing a particular area, e.g., a number of square feet, a particular base station (BS), etc., over a course of time, supported by a particular network carrier, as recorded in the Historical Wireless Device Location Trends and Statistics database 312).



FIG. 2 depicts the flow of an exemplary Network Monitor 302 of the Aggregate Location Dynometer (ALD) 400, in accordance with the principles of the present invention.


In particular, as shown in step 500 of FIG. 2, the Network Monitor 302 preferably continuously, or at least periodically or intermittently, monitors network traffic.


In step 510, monitored wireless data traffic is inspected for the presence of abnormal events, e.g., excessive volume for the time of day, etc. Configurable thresholds for the monitored parameters may be dynamic over the course of the day and even for traffic for any given tower or base station. The configurable thresholds for monitored parameters may be stored in the Configurable Parameter Threshold database 310.


As shown in step 520, if one or more parameter thresholds are exceeded, a viral event may be triggered. In response, the Network Monitor 302 triggers the Crowd Risk Determinant 304 to perform a location-based push/pull service to determine the location of each trackable wireless device within a particular geographic area (e.g., communicating through given base stations or antennas).


When parameter thresholds are not surpassed, indicating that a viral event is not occurring, location data may be logged in the Historical Wireless Device Location Trends and Statistics database 312, as depicted in step 530. Location data logged in the Historical Wireless Device Location Trends and Statistics database 312 may be used by the Crowd Risk Determinant 304 for future analyses of crowd risk.



FIG. 3 depicts the flow of an exemplary Crowd Risk Determinant 304 of the Aggregate Location Dynometer (ALD) 400, in accordance with the principles of the present invention.


In particular, the Crowd Risk Determinant 304 performs a location-based push/pull service to obtain location information pertaining to trackable wireless devices in a given area regarding a respective viral event triggered by the Network Monitor 302, as shown in step 540 of FIG. 3.


In step 550, collected location data is analyzed to assess the viral event that is occurring. The Crowd Risk Determinant 304 uses bounds and priorities set forth in the Risk Rules database 314 to determine if a possible viral event indicates a public safety risk. A viral pattern may or may not imply public safety risk. In step 560, if a public safety risk is determined, the Crowd Risk Determinant 304 triggers the Alert Module 306 to take responsive public safety measures. Location data associated with a public safety risk is logged 530 in the Historical Wireless Device Location Trends and Statistics database 312.


If the Crowd Risk Determinant 304 confirms that a particular viral event does not indicate a public safety risk, the Aggregate Location Dynometer (ALD) 400 is triggered to routinely log location data 530 in the Historical Wireless Device Location Trends and Statistics database 312 for potential future analyses.


Determination of a public safety risk in the Crowd Risk Determinant 304 triggers the Alert Module 306 to implement proper public safety response services. An Alert Module 306 is the final step in the risk determination process of the Aggregate Location Dynometer (ALD) 400.



FIG. 4 depicts the flow of an exemplary Alert Module 306 of the Aggregate Location Dynometer (ALD) 400, in accordance with the principles of the present invention.


In particular, as shown in step 700 of FIG. 4, the Alert Module 306 is triggered by the Crowd Risk Determinant 304 and supplied the predetermined conditions constituting how to handle a determined public safety risk.


The Alert Module 306 immediately alerts the proper authorities 320 in the presence of a public safety risk, as depicted in step 710.


Subsequent aggregate data collections may be made by the Alert Module 306 in step 720. A particular public safety event may be programmed to result in multiple aggregate location data collections, set to occur at specific intervals. Moreover, a particular risk determination result may be configured to act as a triggered push/pull service 540 to acquire additional location data. Subsequent location information is routinely logged in the Historical Wireless Devices Location Trends and Statistics database 530.


Configurable parameters are maintained in the Risk Rules database 314 to assist the Crowd Risk Determinant 304 in determining if location information pertaining to a viral event indicates a likely public safety risk. Factors for risk determination include but are not limited to the shape a cluster of location markers representing individual wireless devices of given density is forming, whether or not markers are spreading out or coming together, and/or at what rate of change a cluster of wireless devices is moving. Factors for risk determination also include the behavior of collective XY location coordinates of the most dense clusters of wireless devices, to where the most dense clusters of wireless devices of concern are moving, and/or whether or not a cluster of wireless devices in a particular location makes sense given the time of day.


For instance, empirical data may indicate that it is unusual for there to be a large number of wireless devices present downtown after business hours, or after a time when local bars and clubs have closed for the night. In this case, a configurable threshold may be set for a combination of location and time of day parameters (e.g., to articulate the number of wireless devices that must be present within a defined downtown region, after a given hour) to trigger a public safety risk. A configurable parameter threshold (e.g., specifying the number of wireless devices capable of inhabiting a particular geographic expanse or particular shape of device formation, or a given density within that region) may manually or empirically be set. If a parameter threshold is surpassed, the Crowd Risk Determinant 304 informs the Alert Module 306 of the development of a public safety risk.


The shape of a cluster of wireless devices may often offer significant clues to crowd risk potential. When location information is collected, the best-fit shape of dense clusters formed by accumulation of wireless devices in a given area may be determined. The best-fit shape of a cluster of wireless devices may be compared against data contained in the historical Acceptable/Non-Acceptable Crowd Shape database 308 to determine danger potential. Different thresholds may be set for like parameters based on varying location.



FIG. 5 denotes first exemplary Aggregate Location Dynometer (ALD) 400 location results, in accordance with the principles of the present invention.


In particular, the large oval shape 101 formed by markers representing individual wireless devices in the given geographical area 200 shown in FIG. 5, may be interpreted as a group of individuals enjoying a sporting event in a stadium. Factors to consider are time of day and scheduled events. The example in FIG. 5 uses precise location.



FIG. 6 denotes second exemplary Aggregate Location Dynometer (ALD) 400 location results, in accordance with the principles of the present invention.


In particular, the pattern 102 in the geographical area 200 shown in FIG. 6 may be interpreted as cell sites pertaining to trackable individuals, assuming most individuals carry wireless devices. The same pattern may mean different things at different hours of the day. The exemplary location result shown in FIG. 6 uses coarse location.



FIG. 7 denotes third exemplary Aggregate Location Dynometer (ALD) 400 location results, in accordance with the principles of the present invention.


In particular, the crescent shape 103 in the geographical area 200 shown in FIG. 7 is recognized as a pattern to be wary of. This crescent shape may represent a variety of different occurrences (e.g., a protest in front of a given location such as a court house, a famous author at a bookstore, etc.). The exemplary location result shown in FIG. 7 uses precise location.


A rate-based parameter threshold may also or alternatively be set to define an acceptable rate at which wireless devices would otherwise normally inhabit a geographic area. For instance, if over a certain number of wireless devices enter an area in under a given amount of time (e.g., if three hundred wireless devices rush into a central pre-defined location in under ten minutes) then a public safety risk may be triggered.


Message content may be analyzed as an attribute for risk determination in response to a viral traffic event. For instance, a determination of the most frequent phrases may be matched against a database of suspected terms (e.g., “meet at the Lincoln Memorial”, etc.).


Motion trends are also analyzed to assess crowd risk. The Crowd Risk Determinant 304 preferably determines whether the accumulation of wireless devices is becoming more or less dense about a central location and whether or not this behavior is expected based on trends and configured thresholds established for particular locations.


Precise accuracy of each individual device location is not extremely important in the present invention. Instead, focus lies in the volume, density, shape and movement of data points collected. Serving cell tower locations for each wireless device may be sufficient to satisfy initial triggering requirements for a possible viral event. The Aggregate Location Dynometer (ALD) 400 is concerned with aggregate location data as opposed to data involving individual device locations. Data regarding parameters such as special events, geographical boundaries, motion trends, density, clustering, spread, time of day and/or message content relating to trackable wireless devices are recorded in the Historical Wireless Device Location Trends and Statistics database 312, as opposed to exact locations of specific wireless devices. Anonymity regarding precise locations of specific wireless devices alleviates some concern surrounding the privacy of individuals during location based services (LBS), as used within the present invention.


An Aggregate Location Dynometer (ALD) 400 has benefit to entities other than emergency management and crowd risk assessment parties. For instance, the present invention may also be used to estimate location trends in cities, to rank areas such as parks and beaches by volume of visitors, and even to peg traffic patterns. Historical crowd data need not represent a public safety issue, e.g., it may merely relate to city planning or disaster recovery. Thus, data collected while scanning for crowd risk provides cities, states and government with valuable information.


Though, preferably all wireless devices in a given area would be monitored for crowd gathering tendencies, it is also within the principles of the present invention to monitor only those devices by the relevant wireless carrier providing Location Dynometer (ALD) 400 services.


The present invention greatly benefits police, fire and general emergency response personnel 320 desiring early warning about possible crowd related risks, e.g., riots. Moreover, the present invention is intended to combat nefarious cell technology to spawn mobs and riots without resorting to network restrictions.


While the invention makes use of the current location data of preferably all wireless devices within a given region, area, etc., the invention also preferably makes distinction between the current mode of operation of the wireless devices being analyzed for a possible public safety risk. For instance, analysis of the density, shape, movement, etc. in determining a possible public safety risk may analyze only wireless devices in active mode.


While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims
  • 1. An aggregate location dynometer in a physical wireless network server, said aggregate location dynometer comprising: a network monitor to monitor a wireless network for an indication of a potential viral event indicated by an aggregation of current locations of a plurality of physical wireless devices associated with said potential viral event; anda crowd risk determinant to assess said aggregation of said current locations of said plurality of physical wireless devices pertaining to said potential viral event triggered by said network monitor.
  • 2. The aggregate location dynometer in a physical wireless network server, said aggregate location dynometer according to claim 1, further comprising: an alert module to initiate an alert message relating to a public safety risk determined from said potential viral event.
  • 3. The aggregate location dynometer in a physical wireless network server, said aggregate location dynometer according to claim 1, further comprising: an historical database maintaining a geographic region associated with said potential viral event.
  • 4. The aggregate location dynometer in a physical wireless network server, said aggregate location dynometer according to claim 1, further comprising: an historical database maintaining a plurality of acceptable crowd shapes, a crowd shape being defined by a past aggregation of said current locations of said plurality of physical wireless devices associated with a known acceptable viral event.
  • 5. The aggregate location dynometer in a physical wireless network server, said aggregate location dynometer according to claim 1, further comprising: an historical database maintaining a plurality of unacceptable crowd shapes, a crowd shape being defined by a past aggregation of said current locations of said plurality of physical wireless devices associated with a known unacceptable viral event.
  • 6. The aggregate location dynometer in a physical wireless network server, said aggregate location dynometer according to claim 1, further comprising: a configurable parameter defining a threshold of a crowd shape becoming unacceptable and thus initiating said crowd risk.
  • 7. The aggregate location dynometer in a physical wireless network server, said aggregate location dynometer according to claim 1, further comprising: an historical database maintaining a plurality of crowd shape trends based on historical locations of physical wireless devices during previous known viral events.
  • 8. A method of alerting to a problematic crowd risk based on location based services (LBS), comprising: monitoring wireless traffic for a potential impending viral event associated with a formation by an aggregation of current locations of a plurality of physical wireless devices within a given region;requesting location information associated with said plurality of physical wireless devices; anddetermining a crowd risk of said aggregation of said current locations of said plurality of physical wireless devices based on a crowd shape of said aggregation of said current locations of said plurality of physical wireless devices.
  • 9. The method of alerting to a problematic crowd risk based on location based services (LBS) according to claim 8, further comprising: triggering a crowd alert message when said determined crowd risk is above a given threshold.
  • 10. The method of alerting to a problematic crowd risk with location based services (LBS) according to claim 8, wherein: said crowd risk of said aggregation of said plurality of physical wireless devices is further determined based on a movement of said aggregation of said plurality of physical wireless devices.
  • 11. The method of alerting to a problematic crowd risk with location based services (LBS) according to claim 10, wherein said monitoring wireless traffic comprises: monitoring wireless traffic at a given point in a wireless network; andcomparing a given traffic parameter associated with said aggregation of said current locations of said plurality of physical wireless devices, with an historical traffic parameter associated with a previous problematic crowd formation.
  • 12. The method of alerting to a problematic crowd risk with location based services (LBS) according to claim 11, wherein: said given point is at a given base station in said wireless network.
  • 13. The method of alerting to a problematic crowd risk with location based services (LBS) according to claim 10, further comprising: logging a snapshot formation created by said aggregation of said current locations of said plurality of physical wireless devices.
  • 14. The method of alerting to a problematic crowd risk with location based services (LBS) according to claim 10, further comprising: initiating a location request for each of said plurality of physical wireless devices.
  • 15. The method of alerting to a problematic crowd risk with location based services (LBS) according to claim 9, further comprising: comparing a viral pattern formed by said aggregation of said current locations of said plurality of wireless devices to predetermined risk rules.
  • 16. The method of alerting to a problematic crowd risk with location based services (LBS) according to claim 15, further comprising: logging said viral pattern.
Parent Case Info

The present application is a continuation of U.S. application Ser. No. 14/176,691, entitled “Aggregate Location Dynometer (ALD)”, filed on Feb. 10, 2014; which is a continuation of U.S. application Ser. No. 13/317,996 entitled “Aggregate Location Dynometer (ALD)”, filed on Nov. 2, 2011, now U.S. Pat. No. 8,649,806; which claims priority from U.S. Provisional Application No. 61/573,112, entitled “Aggregate Location Dynometer (ALD)”, filed Sep. 2, 2011, the entirety of all three of which are expressly incorporated herein by reference.

US Referenced Citations (379)
Number Name Date Kind
4445118 Taylor Apr 1984 A
4928107 Kuroda May 1990 A
4972484 Theile Nov 1990 A
5126722 Kamis Jun 1992 A
5283570 DeLuca Feb 1994 A
5301354 Schwendeman Apr 1994 A
5311516 Kuznicki May 1994 A
5327529 Fults Jul 1994 A
5335246 Yokev Aug 1994 A
5351235 Lahtinen Sep 1994 A
5365451 Wang Nov 1994 A
5418537 Bird May 1995 A
5422813 Schuchman Jun 1995 A
5479408 Will Dec 1995 A
5485163 Singer Jan 1996 A
5504491 Chapman Apr 1996 A
5506886 Maine Apr 1996 A
5517199 DiMattei May 1996 A
5530655 Lokhoff Jun 1996 A
5530914 McPheters Jun 1996 A
5539395 Buss Jul 1996 A
5539829 Lokhoff Jul 1996 A
5546445 Dennison Aug 1996 A
5568153 Beliveau Oct 1996 A
5583774 Diesel Dec 1996 A
5594780 Wiedeman Jan 1997 A
5606618 Lokhoff Feb 1997 A
5629693 Janky May 1997 A
5633630 Park May 1997 A
5636276 Brugger Jun 1997 A
5661652 Sprague Aug 1997 A
5661755 Van de Kerkhof Aug 1997 A
5689245 Noreen Nov 1997 A
5699053 Jonsson Dec 1997 A
5704029 Wright, Jr. Dec 1997 A
5721781 Deo Feb 1998 A
5727057 Emery Mar 1998 A
5731785 Lemelson Mar 1998 A
5765152 Erickson Jun 1998 A
5771353 Eggleston Jun 1998 A
5774670 Montulli Jun 1998 A
5809415 Rossmann Sep 1998 A
5812086 Bertiger Sep 1998 A
5812087 Krasner Sep 1998 A
5841396 Krasner Nov 1998 A
5857201 Wright, Jr. Jan 1999 A
5864667 Barkan Jan 1999 A
5874914 Krasner Feb 1999 A
5896369 Warsta Apr 1999 A
5922074 Richard Jul 1999 A
5930250 Klok Jul 1999 A
5945944 Krasner Aug 1999 A
5946629 Sawyer Aug 1999 A
5950137 Kim Sep 1999 A
5960362 Grob Sep 1999 A
5983099 Yao Nov 1999 A
5999124 Sheynblat Dec 1999 A
6032051 Hall Feb 2000 A
6049718 Stewart Apr 2000 A
6052081 Krasner Apr 2000 A
6058338 Agashe May 2000 A
6061018 Sheynblat May 2000 A
6064336 Krasner May 2000 A
6067045 Castelloe May 2000 A
6081229 Soliman Jun 2000 A
6085320 Kaliski, Jr. Jul 2000 A
6118403 Lang Sep 2000 A
6121923 King Sep 2000 A
6124810 Segal Sep 2000 A
6131067 Girerd Oct 2000 A
6133874 Krasner Oct 2000 A
6134483 Vayanos Oct 2000 A
6147598 Murphy Nov 2000 A
6150980 Krasner Nov 2000 A
6154172 Piccionelli Nov 2000 A
6169901 Boucher Jan 2001 B1
6169902 Kawamoto Jan 2001 B1
6178506 Quick, Jr. Jan 2001 B1
6185427 Krasner Feb 2001 B1
6188354 Soliman Feb 2001 B1
6188909 Alanara Feb 2001 B1
6189098 Kaliski, Jr. Feb 2001 B1
6195557 Havinis Feb 2001 B1
6204798 Fleming Mar 2001 B1
6205330 Winbladh Mar 2001 B1
6208290 Krasner Mar 2001 B1
6215441 Moeglein Apr 2001 B1
6239742 Krasner May 2001 B1
6247135 Feague Jun 2001 B1
6249873 Richard Jun 2001 B1
6253203 O'Flaherty Jun 2001 B1
6260147 Quick, Jr. Jul 2001 B1
6275692 Skog Aug 2001 B1
6275849 Ludwig Aug 2001 B1
6297768 Allen, Jr. Oct 2001 B1
6307504 Sheynblat Oct 2001 B1
6308269 Proidl Oct 2001 B2
6313786 Sheynblat Nov 2001 B1
6321257 Kotola Nov 2001 B1
6324542 Wright, Jr. et al. Nov 2001 B1
6327473 Soliman Dec 2001 B1
6333919 Gaffney Dec 2001 B2
6360093 Ross Mar 2002 B1
6360102 Havinis Mar 2002 B1
6363254 Jones Mar 2002 B1
6367019 Ansell Apr 2002 B1
6370389 Isomursu Apr 2002 B1
6377209 Krasner Apr 2002 B1
6400314 Krasner Jun 2002 B1
6400958 Isomursu Jun 2002 B1
6411254 Moeglein Jun 2002 B1
6421002 Krasner Jul 2002 B2
6430504 Gilbert Aug 2002 B1
6433734 Krasner Aug 2002 B1
6442391 Johansson Aug 2002 B1
6449473 Raivisto Sep 2002 B1
6449476 Hutchison, IV Sep 2002 B1
6456852 Bar Sep 2002 B2
6463272 Wallace Oct 2002 B1
6477150 Maggenti Nov 2002 B1
6505049 Dorenbosch Jan 2003 B1
6510387 Fuchs Jan 2003 B2
6512922 Burg Jan 2003 B1
6512930 Sandegren Jan 2003 B2
6515623 Johnson Feb 2003 B2
6519466 Pande Feb 2003 B2
6522682 Kohli Feb 2003 B1
6525687 Roy Feb 2003 B2
6525688 Chou Feb 2003 B2
6529829 Turetzky Mar 2003 B2
6531982 White Mar 2003 B1
6538757 Sansone Mar 2003 B1
6539200 Schiff Mar 2003 B1
6539304 Chansarkar Mar 2003 B1
6542464 Takeda Apr 2003 B1
6542734 Abrol Apr 2003 B1
6542743 Soliman Apr 2003 B1
6549776 Joong Apr 2003 B1
6549844 Egberts Apr 2003 B1
6556832 Soliman Apr 2003 B1
6560461 Fomukong May 2003 B1
6560534 Abraham May 2003 B2
6567035 Elliott May 2003 B1
6570530 Gaal May 2003 B2
6574558 Kohli Jun 2003 B2
6580390 Hay Jun 2003 B1
6584552 Kuno Jun 2003 B1
6594500 Bender Jul 2003 B2
6597311 Sheynblat Jul 2003 B2
6603973 Foladare Aug 2003 B1
6606495 Korpi Aug 2003 B1
6606554 Edge Aug 2003 B2
6609004 Morse Aug 2003 B1
6611757 Brodie Aug 2003 B2
6618670 Chansarkar Sep 2003 B1
6621452 Knockheart Sep 2003 B2
6628233 Knockheart Sep 2003 B2
6633255 Krasner Oct 2003 B2
6640184 Rabe Oct 2003 B1
6650288 Pitt et al. Nov 2003 B1
6661372 Girerd Dec 2003 B1
6665539 Sih Dec 2003 B2
6665541 Krasner Dec 2003 B1
6671620 Garin Dec 2003 B1
6677894 Sheynblat Jan 2004 B2
6680694 Knockheart Jan 2004 B1
6680695 Turetzky Jan 2004 B2
6691019 Seeley Feb 2004 B2
6694258 Johnson Feb 2004 B2
6697629 Grilli Feb 2004 B1
6698195 Hellinger Mar 2004 B1
6701144 Kirbas Mar 2004 B2
6703971 Pande Mar 2004 B2
6703972 van Diggelen Mar 2004 B2
6704651 van Diggelen Mar 2004 B2
6707421 Drury Mar 2004 B1
6714793 Carey Mar 2004 B1
6721871 Piispanen Apr 2004 B2
6724342 Bloebaum Apr 2004 B2
6725159 Krasner Apr 2004 B2
6731940 Nagendran May 2004 B1
6734821 Van Diggelen May 2004 B2
6738013 Orler May 2004 B2
6738800 Aquilon May 2004 B1
6741842 Goldberg May 2004 B2
6745038 Callaway, Jr. Jun 2004 B2
6747596 Orler Jun 2004 B2
6748195 Phillips Jun 2004 B1
6751464 Burg Jun 2004 B1
6756938 Zhao Jun 2004 B2
6757544 Rangarajan Jun 2004 B2
6772340 Peinado Aug 2004 B1
6775655 Peinado Aug 2004 B1
6775802 Gaal Aug 2004 B2
6778136 Gronemeyer Aug 2004 B2
6778885 Agashe Aug 2004 B2
6781963 Crockett Aug 2004 B2
6788249 Farmer Sep 2004 B1
6795699 McCraw Sep 2004 B1
6799050 Krasner Sep 2004 B1
6801124 Naitou Oct 2004 B2
6801159 Swope Oct 2004 B2
6804524 Vandermeijden Oct 2004 B1
6807534 Erickson Oct 2004 B1
6810323 Bullock Oct 2004 B1
6813560 van Diggelen Nov 2004 B2
6816111 Krasner Nov 2004 B2
6816710 Krasner Nov 2004 B2
6816719 Heinonen Nov 2004 B1
6816734 Wong Nov 2004 B2
6820269 Baucke et al. Nov 2004 B2
6829475 Lee Dec 2004 B1
6832373 O'Neill Dec 2004 B2
6833785 Brown Dec 2004 B2
6839020 Geier Jan 2005 B2
6839021 Sheynblat Jan 2005 B2
6842715 Gaal Jan 2005 B1
6853849 Tognazzini Feb 2005 B1
6853916 Fuchs Feb 2005 B2
6856282 Mauro Feb 2005 B2
6861980 Rowitch Mar 2005 B1
6865171 Nilsson Mar 2005 B1
6865395 Riley Mar 2005 B2
6867734 Voor Mar 2005 B2
6873854 Crockett Mar 2005 B2
6885940 Brodie Apr 2005 B2
6888497 King May 2005 B2
6888932 Snip May 2005 B2
6895238 Newell May 2005 B2
6895249 Gaal May 2005 B2
6895324 Straub May 2005 B2
6900758 Mann May 2005 B1
6903684 Simic Jun 2005 B1
6904029 Fors Jun 2005 B2
6907224 Younis Jun 2005 B2
6907238 Leung Jun 2005 B2
6912395 Benes Jun 2005 B2
6915208 Garin Jul 2005 B2
6917331 Gronemeyer Jul 2005 B2
6930634 Peng Aug 2005 B2
6937187 Van Diggelen Aug 2005 B2
6937872 Krasner Aug 2005 B2
6941144 Stein Sep 2005 B2
6944540 King Sep 2005 B2
6947772 Minear Sep 2005 B2
6950058 Davis Sep 2005 B1
6956467 Mercado, Jr. Oct 2005 B1
6957073 Bye Oct 2005 B2
6961562 Ross Nov 2005 B2
6965754 King Nov 2005 B2
6965767 Maggenti Nov 2005 B2
6970917 Kushwaha Nov 2005 B1
6973166 Tsumpes Dec 2005 B1
6973320 Brown Dec 2005 B2
6975266 Abraham Dec 2005 B2
6978453 Rao Dec 2005 B2
6980816 Rohles Dec 2005 B2
6985105 Pitt et al. Jan 2006 B1
6996720 DeMello Feb 2006 B1
6998985 Reisman Feb 2006 B2
6999782 Shaughnessy Feb 2006 B2
7020440 Watanabe Mar 2006 B2
7024321 Deninger Apr 2006 B1
7024393 Peinado Apr 2006 B1
7047411 DeMello May 2006 B1
7064656 Belcher et al. Jun 2006 B2
7065351 Carter Jun 2006 B2
7065507 Mohammed Jun 2006 B2
7071814 Schorman Jul 2006 B1
7079857 Maggenti Jul 2006 B2
7103018 Hansen Sep 2006 B1
7103574 Peinado Sep 2006 B1
7106717 Rousseau Sep 2006 B2
7136838 Peinado Nov 2006 B1
7151946 Maggenti Dec 2006 B2
7177623 Baldwin Feb 2007 B2
7203752 Rice Apr 2007 B2
7209969 Lahti Apr 2007 B2
7218940 Niemenmaa May 2007 B2
7221959 Lindquist May 2007 B2
7269413 Kraft Sep 2007 B2
7301494 Waters Nov 2007 B2
7324823 Rosen Jan 2008 B1
RE42927 Want Nov 2011 E
8190169 Shim May 2012 B2
8314683 Pfeffer Nov 2012 B2
8442807 Ramachandran May 2013 B2
8649806 Cuff Feb 2014 B2
20010011247 O'Flaherty Aug 2001 A1
20020037735 Maggenti Mar 2002 A1
20020052214 Maggenti May 2002 A1
20020061760 Maggenti May 2002 A1
20020069529 Wieres Jun 2002 A1
20020102999 Maggenti Aug 2002 A1
20020112047 Kushwaha Aug 2002 A1
20020135504 Singer Sep 2002 A1
20020173317 Nykanen Nov 2002 A1
20020198632 Breed Dec 2002 A1
20030009602 Jacobs Jan 2003 A1
20030037163 Kitada Feb 2003 A1
20030065788 Salomaki Apr 2003 A1
20030078064 Chan Apr 2003 A1
20030081557 Mettala May 2003 A1
20030101329 Lahti May 2003 A1
20030101341 Kettler May 2003 A1
20030103484 Oommen Jun 2003 A1
20030112941 Brown Jun 2003 A1
20030114157 Spitz Jun 2003 A1
20030119528 Pew Jun 2003 A1
20030131023 Bassett Jul 2003 A1
20030153340 Crockett Aug 2003 A1
20030153341 Crockett Aug 2003 A1
20030153342 Crockett Aug 2003 A1
20030153343 Crockett Aug 2003 A1
20030161298 Bergman Aug 2003 A1
20030204640 Sahinoja et al. Oct 2003 A1
20030223381 Schroderus Dec 2003 A1
20040002326 Maher Jan 2004 A1
20040044623 Wake Mar 2004 A1
20040046667 Copley Mar 2004 A1
20040064550 Sakata Apr 2004 A1
20040068724 Gardner Apr 2004 A1
20040090121 Simonds May 2004 A1
20040204806 Chen Oct 2004 A1
20040205151 Sprigg Oct 2004 A1
20040229632 Flynn Nov 2004 A1
20040257273 Benco Dec 2004 A1
20050003797 Baldwin Jan 2005 A1
20050028034 Gantman Feb 2005 A1
20050039178 Marolia Feb 2005 A1
20050041578 Huotari Feb 2005 A1
20050086340 Kang Apr 2005 A1
20050086467 Asokan Apr 2005 A1
20050112030 Gauss May 2005 A1
20050136895 Thenthiruperai Jun 2005 A1
20050170856 Keyani Aug 2005 A1
20050172217 Leung Aug 2005 A1
20050174987 Raghav Aug 2005 A1
20050209995 Aksu Sep 2005 A1
20050233735 Karaoguz Oct 2005 A1
20050246217 Horn Nov 2005 A1
20050259675 Tuohino Nov 2005 A1
20060053225 Poikselka Mar 2006 A1
20060058045 Nilsen Mar 2006 A1
20060073810 Pyhalammi Apr 2006 A1
20060074618 Miller Apr 2006 A1
20060090136 Miller Apr 2006 A1
20060097866 Adamczyk May 2006 A1
20060212558 Sahinoja Sep 2006 A1
20060212562 Kushwaha Sep 2006 A1
20060234639 Kushwaha Oct 2006 A1
20060234698 Fok et al. Oct 2006 A1
20060246920 Shim Nov 2006 A1
20070026854 Nath Feb 2007 A1
20070030116 Feher Feb 2007 A1
20070030539 Nath Feb 2007 A1
20070030973 Mikan Feb 2007 A1
20070049287 Dunn Mar 2007 A1
20070186105 Bailey Aug 2007 A1
20070191025 McBrierty Aug 2007 A1
20070271596 Boubion Nov 2007 A1
20080026723 Han Jan 2008 A1
20080160980 Harris Jul 2008 A1
20080198989 Contractor Aug 2008 A1
20080318591 Oliver Dec 2008 A1
20090058830 Herz Mar 2009 A1
20090140851 Graves Jun 2009 A1
20090204815 Dennis Aug 2009 A1
20090222388 Hua Sep 2009 A1
20090271486 Ligh Oct 2009 A1
20090311992 Jagetiya Dec 2009 A1
20090328135 Szabo Dec 2009 A1
20100024045 Sastry Jan 2010 A1
20100050251 Speyer Feb 2010 A1
20100197318 Petersen Aug 2010 A1
20100205542 Walman Aug 2010 A1
20100285763 Ingrassia Nov 2010 A1
20100285814 Price Nov 2010 A1
20100308993 Ma Dec 2010 A1
Non-Patent Literature Citations (10)
Entry
Internal Search Report received in PCT/US2009/05575 dated Jan. 14, 2011.
Internal Search Report received in PCT/US2009/05575 dated Dec. 3, 2009.
International Search Report received in PCT/US2011/01198 dated Aug. 6, 2012.
Internal Search Report received in PCT/US2011/000671 dated Jul. 27, 2011.
Internal Search Report received in PCT/US2011/000671 dated Apr. 25, 2012.
International Search Report in PCT/US2010/001134 dated Oct. 31, 2011.
Internal Search Report received in PCT/US2011/00950 dated Sep. 16, 2011.
International Search Report in PCT/US2011/00950 dated Apr. 30, 2012.
International Search Report received in PCT/US2012/000374 dated Nov. 20, 2012.
International Report on Patentability received in PCT/US2012/000374 dated Sep. 5, 2013.
Related Publications (1)
Number Date Country
20160044461 A1 Feb 2016 US
Provisional Applications (1)
Number Date Country
61573112 Sep 2011 US
Continuations (2)
Number Date Country
Parent 14176691 Feb 2014 US
Child 14885136 US
Parent 13317996 Nov 2011 US
Child 14176691 US