iALERT enhanced alert manager

Information

  • Patent Grant
  • 8942743
  • Patent Number
    8,942,743
  • Date Filed
    Wednesday, December 28, 2011
    12 years ago
  • Date Issued
    Tuesday, January 27, 2015
    9 years ago
Abstract
iAlert_Enhanced_Alert_Manager enables a user to register an interest in their current location, as well as persons, places and/or things in which the user holds some regard. The iAlert_Enhanced_Alert_Manager provides notification and clarifying information to user's devices concerning events/happenstance that have occurred or are likely to occur within a proximity of registered persons, places, and/or things. The iAlert_Enhanced_Alert_Manager comprises data structures (e.g. an Affinity Table, a SPIN table, a SPIN-List Table, an Affinity-List Table, and a Keyword-List Table) to manage affinities, Spheres of Influence (SPINs), and relationships therebetween that may positively or negatively induce a person. Timely notification of events/happenstance to a user comprises the computation of iEvent-vectors and iAlert-vectors. An iEvent-vector contains fields pertaining to events/happenstance whereas an iAlert-vector comprises information pertaining to notifications. Transmission of a notification is determined as a function of the magnitude of an event/happenstance and the proximity of an event/happenstance to registered objects of interest.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to telecommunications. More particularly, it relates to wireless based technologies.


2. Background of Related Art


The present inventors have appreciated that there are a wide variety of events and happenstance that a person might benefit from knowing about, either before the event happens or very shortly after the event happens. For instance, persons near significant events (e.g. vehicle collisions, natural catastrophes, fires, etc.) may otherwise have no direct need to be notified of the simple occurrence of the event, but may very much like to get clarification of the nature of the event. Persons near less obvious events and happenstance (e.g. one's neighbor just dialed 9-1-1) may want to receive both notification of the event/happenstance as well as information clarifying the nature of the event/happenstance.


There is a need for persons to receive notification and clarifying information about events and happenstance that occur at a distance from a person if the event has significant enough area of effect (e.g. volcanic eruption), and/or if the event is within close enough proximity to someone about whom the person cares, and/or if the event is within close enough proximity to something about which the person holds some regard.


SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a method of providing notification to a wireless device regarding an event with an area of effect that encompasses said wireless device, or a list of alternate wireless devices pre-designated by the subscriber to whom said wireless device belongs, or a list of places (i.e. locations) pre-designated by the subscriber to whom said wireless device belongs; said list of wireless device and alternate wireless devices and locations constituting an affinity group. A sphere of influence (SPIN) is defined around each wireless device. Every event constitutes a plane of interaction that may or may not intersect these SPINs; said intersection depending on the event's area of effect. An affinity confluence is recognized between each and every event that intersects (i.e. encompasses) one or more constituent components of an affinity group (i.e. location of an identified wireless device or location of a designated place). Affinity confluence is evaluated and recognized for every affinity group. Recognition of affinity confluence stimulates a relevant notification to be initiated to the subscriber's wireless device.





BRIEF DESCRIPTION OF THE DRAWINGS

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



FIG. 1 depicts the function of an exemplary sentinel service provided by the iAlert_Enhanced_Alert_Manager, in accordance with the principles of the present invention.



FIG. 2 depicts five (5) exemplary data structures with which to manage affinities, SPINs, and the identification of relationships therebetween.



FIG. 3 depicts two (2) exemplary data structures with which to manage iAlert-vectors and the notifications that are the ultimate purpose of the iAlert-vector, in accordance with the principles of the present invention.



FIG. 4 depicts one (1) exemplary data structure with which to manage iEvent-vectors, in accordance with the principles of the present invention.



FIG. 5 depicts a wireless device user's location, in accordance with the principles of the present invention.



FIG. 6 shows an exemplary location (LOC) table, in accordance with the principles of the present invention.



FIG. 7 shows an exemplary primary matrix, in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

In accordance with the principles of the present invention, a method and system is provided to notify a wireless device about events/happenstance that have occurred within proximity of persons, places, and/or things in which a user has registered an interest. The system comprises a sentinel service provided by a suitable alert manager, e.g., an iAlert_Enhanced_Alert_Manager in a physical server device in communication with the wireless device.


A person with a mobile device may define a Sphere of Influence (SPIN) through which a multitude of planes of interaction pass and occasionally intersect. The intersection of planes of affinity within that person's Sphere of


Influence (SPIN) constitutes a confluence of affinity that may either positively induce a person (attractive inducement) or negatively induce a person (repulsive inducement).


In accordance with the principles of the present invention, the sentinel service provided by the iAlert_Enhanced_Alert_Manager comprises data structures to manage affinities, Spheres of Influence (SPINS), and the identification of relationships therebetween. Five exemplary data structures maintained in the sentinel service include an Affinity Table, a Keyword-List Table, a SPIN Table, a SPIN-List Table, and an Affinity-List Table. Transmission of a notification to an iAlert user's device concerning a particular event/happenstance, in accordance with the principles of the present invention, is determined as a function of both the magnitude of the event/happenstance and the proximity of the event/happenstance to persons, places and/or things that an iAlert user has pre-designated as “important.”


Timely notification of events/happenstance to a user's mobile device comprises the computation of a multitude of iEvent-vectors and iAlert-vectors, in accordance with the principles of the present invention. An iEvent-vector comprises information pertaining to a particular event/happenstance whereas an iAlert-vector comprises information pertaining to notifications regarding events/happenstance.


In accordance with another aspect of the present invention, a method and system enables a user to query the iAlert_Enhanced_Alert_Manager regarding the current state of a wireless device associated with a person, place, or thing in which the user has registered an interest. The current state of one to many vectors is assessed of either positive (i.e. attractive inducement) or negative (i.e. repulsive inducement) affinity.


The sentinel service may also notify a user's wireless device regarding events/happenstance that have not yet occurred but are deemed likely to occur within a parametrically defined proximity of persons, places, and/or things associated with respective wireless devices, and in which the user has identified an interest, in accordance with yet another aspect of the present invention.


In yet another embodiment of the present invention, timely evaluation of notifications to a user's wireless device is accomplished with a geographically defined nexus (“GeoNEXUS”) and a four (4) tier data structure representing the location of iAlert-vectors and iEvent-vectors. GeoNEXUS rapidly identifies all iAlert-vectors within a predefined/preconfigured close proximity to an iEvent-vector, to assist in the timely transmission of notifications to users, regarding relevant events and happenstance.


The present invention describes a method and system that notifies one or more wireless devices, hereafter referred to as party-A, about events and happenstance that a user has registered an interest in. The present invention also describes a method and system to warn wireless devices of events that are likely to occur. The need for notification is determined as a function of both the magnitude of the event/happenstance and the proximity of the event/happenstance to wireless devices associated with persons, places, and/or things pre-designated by party-A as “important”.


The present invention additionally describes a method and system by which wireless devices such as Party-A can query the iAlert_Enhanced_Alert Manager to assess the current state of one to many vectors of either positive (i.e. attractive inducement) or negative (i.e. repulsive inducement) affinity pertaining to pre-designated wireless devices associated with persons, places, and/or things.


First, the present invention allows Party-A to define persons, places, and/or things about which Party-A has a vested interest. Designation of persons, places, and/or things can be accomplished via various methods, including, but not limited to, calling a service center represented by either a human call-taker or an Interactive Voice Response (IVR) system, sending an activation SMS short message, sending an activation Email, or interacting with a full featured Internet web site.


Persons are identified by a mobile identification number corresponding to a phone that the person of interest is likely carrying. Mobile identification numbers used to identify individuals include, but are not limited to, cellular phone numbers, LTE phone numbers, and nomadic/mobile Voice over IP (VoIP) phone numbers. A list of examples of mobile identification numbers would include, but not be limited to, Radio Frequency Identifier [RFID], Electronic Serial Number [ESN], Mobile Identification Number [MIN], Mobile Directory Number [MDN], International Mobile Subscriber Identity [IMSI], International Mobile Equipment Identity [IMEI], Mobile Equipment Identifier [MEID], and Mobile Subscriber ISDN Number [MSISDN].


Places are identified by location, including, but not limited to, a valid postal address, a Master Street Address Guide (MSAG) record, or a latitude/longitude pair.


Things are identified by Radio Frequency Identifier (RFID) (e.g. LoJack Tag Number) or by location, including, but not limited to, a valid postal address, a Master Street Address Guide (MSAG) record, or a latitude/longitude pair. A latitude/longitude pair for an object may be attained using built-in GPS/GLONASS/GALILEO/GNSS receiver technology. Alternatively, if a mobile device is used to activate the sentinel service, then a latitude/longitude pair identifying an object may be recorded during activation.



FIG. 1 depicts the function of an exemplary sentinel service provided by the iAlert_Enhanced_Alert_Manager, in accordance with the principles of the present invention.


In particular, FIG. 1 illustrates nine (9) different persons, places, or things in which one iAlert subscribing wireless device has advertised an interest, as well as three (3) different events about which the iAlert subscribing wireless device may want to be notified.


In the example depicted in FIG. 1, the iAlert subscribing wireless device has registered an interest in their own wireless device 100, their spouse's wireless device 101, their son's wireless device 102, their daughter's wireless device 103, their mother's wireless device 104, their home's location 105, their parents' home's location 106, their children's school's location 107, and their car wireless device 108.


Moreover, the example in FIG. 1 also depicts three (3) exemplary events the iAlert subscribing wireless device may be notified about. Exemplary potential events of interest include a train derailment 110 with a declared 3-square block evacuation area 120, a vehicle fire 111 with a 200 foot area of effect 121, and a 9-1-1 call in-progress with a declared 200 foot area of potential influence 122, inside which a medical first responder or good Samaritan could provide timely cardio-pulmonary resuscitation (CPR) to the heart attack victim who has dialed 9-1-1.


In the example depicted in FIG. 1, the magnitude of the train derailment 120 is not big enough to encompass any of the nine (9) persons/places/things in which the iAlert subscribing wireless device has registered an interest. Thus, the train derailment is not considered a threat and a notification is not sent to the iAlert subscribing wireless device.


The area of potential influence 122 associated with the 9-1-1 call in-progress, in the example depicted in FIG. 1, is big enough to encompass the iAlert subscribing wireless device's current location 100. Though, the subscriber who owns the iAlert registered wireless device has declared neither an affinity for “medical first responder” nor an affinity for “good samaritanism” so a notification is not sent to the iAlert registered wireless device.


The area of effect associated with the vehicle fire 111, in the example depicted in FIG. 1, encompasses the location that the iAlert subscriber has recorded for their car 108. The iAlert subscriber would certainly like to be made aware of this event, so a notification is sent to the iAlert subscribing wireless device.


Facilitation of the type of notification sent to an iAlert subscriber regarding a particular event/happenstance depends upon whether the iAlert sentinel pertains to a person, place, or thing.


In a somewhat inverted view of the universe, a mobile device defines a Sphere of Influence (SPIN) through which a multitude of planes of interaction pass and occasionally intersect. The intersection of planes of interaction within a wireless device's sphere of influence constitutes a confluence of affinity that may either positively induce a person (attractive inducement) or negatively induce a person (repulsive inducement).


Due to the varied nature of inducements, in accordance with the present invention, sentinels for persons depend upon a Sphere of Influence (SPIN) table, an AffinityList table, and an Affinity table to determine the precise nature of any notifications to be sent.



FIG. 2 depicts five (5) exemplary data structures with which to manage affinities, SPINs, and the identification of relationships therebetween.


In the example illustrated in FIG. 2, all affinities are maintained using two (2) specific data structures: an Affinity Table 130, and a Keyword-List Table 134.


All participating SPINs are maintained using one (1) primary data structure: a SPIN Table 132.


The relationship between affinities and SPINs is managed using, e.g., two (2) additional data structures: a SPIN-List Table 136, and an Affinity-List Table 138.


Each record or row in the Affinity Table 130 includes, but is not limited to, an Affinity ID (i.e. the primary key), a Keyword-List Link, and a SPIN-List Link. In the given example, every defined Affinity must have at least one Keyword-List entry (i.e. at least one keyword) with which to uniquely identify the Affinity. Keyword-List Link fields are preferably not allowed to be set to a TERMINATOR value. Affinities that are defined but have zero (0) associated SPINs must set the SPIN-List Link for the Affinity to a TERMINATOR value 131.


Note that in this description the word “Link” is used to denote any reference/dereference mechanism used to access information from a data structure other than the data structure in which the Link resides.


Each record or row in the Keyword-List Table 134 includes, but is not limited to, a Keyword-List ID (i.e. the primary key), a Keyword, an Affinity Link, and two (2) Keyword-List Link values, PRECEDE and SUCCEED. PRECEDE and SUCCEED are two (2) Keyword-List Link values used to create a doubly-linked list of the keywords that serve to uniquely identify an Affinity.


The Keyword field of a Keyword-List entry may be set to any representation of a keyword except the null or empty set. The Affinity Link field of a Keyword-List entry must refer back to one and only one associated Affinity Table entry. Affinity Link fields are not allowed to be set to a TERMINATOR value. The PRECEDE and SUCCEED fields of a Keyword-List entry are also not to be set to a TERMINATOR value. The PRECEDE and SUCCEED fields must always refer to an entry in the Keyword-List Table. Keyword-Lists that are comprised of one and only one (1) keyword will set the values of both PRECEDE and SUCCEED to refer to the sole Keyword-List entry in the table. Thus, in a Keyword-List Table comprising of only one entry, PRECEDE and SUCCEED values refer to or point to one another 135.


Every participating SPhere of INfluence (SPIN) in the present invention is represented by one (1) and only one entry in the SPIN Table 132. Each record or row in the SPIN Table 132 includes, but is not limited to, a SPIN ID (i.e. the primary key), miscellaneous SPIN information, and an Affinity-List Link. Miscellaneous SPIN information may be a multitude of sub-fields, some of which may actually refer to other data structures or other data sources entirely. Participating SPINs for which zero (0) affinities have been identified, must set the Affinity-List Link value for the SPIN to a TERMINATOR value 133.


Relationship or association between Affinities and SPINs is managed using both the SPIN-List Table 136 and the Affinity-List Table 138. The SPIN-List Table 136 is intended to permit a device to start with one (1) entry in the Affinity Table and find all SPINs associated with that Affinity. Alternatively, the Affinity-List Table is intended to permit a device to start with one (1) entry in the SPIN Table and find all Affinities associated with that SPIN.


Each record or row in the SPIN-List Table 136 includes, but is not limited to, a SPIN-List ID (i.e. the primary key), an Affinity Link, a SPIN Link, and two (2) SPIN-List link values, PRECEDE and SUCCEED. PRECEDE and SUCCEED are two (2) SPIN-List link values used to create a doubly-linked list of SPINs associated with an Affinity. The Affinity Link and SPIN Link fields are not allowed to be set to a TERMINATOR value. Entries in the SPIN-List Table are only created when a relationship between an Affinity and a SPIN is created. Thus, there is always both a reference to an Affinity as well as a reference to a SPIN in the SPIN-List Table. PRECEDE and SUCCEED fields must always refer to an entry in the SPIN-List Table. SPIN-Lists that are comprised of one and only one (1) SPIN, set the values of both PRECEDE and SUCCEED to refer to the sole entry in the SPIN-List table. Thus, in a SPIN-List Table comprising of only one entry, PRECEDE and SUCCEED values refer to or point to one another 137.


Each record or row in the Affinity-List Table 138 includes, but is not limited to, an Affinity-List ID (i.e. the primary key), an Affinity Link, a SPIN Link, and two (2) Affinity-List link values, SUCCEED and PRECEDE. Affinity-List link values SUCCEED and PRECEDE are used to create a doubly-linked list of the


Affinities associated with a particular SPIN. The Affinity Link and SPIN Link fields are preferably not allowed to be set to a TERMINATOR value. Entries in the Affinity-List Table are only created when a relationship between an Affinity and a SPIN is created. Thus, there is always both a reference to an Affinity as well as a reference to a SPIN in an Affinity-List table. PRECEDE and SUCCEED fields must always refer to an entry in the Affinity-List Table. Affinity-Lists that are comprised of one and only one (1) Affinity, set the values of both PRECEDE and SUCCEED to refer to the sole entry in the Affinity-List table. Thus, in an Affinity-List Table comprised of only one entry, PRECEDE and SUCCEED values refer to or point to one another 139.


Definition and activation of the sentinel service provided by the iAlert_Enhanced_Alert_Manager, on a person, place, or thing, initiates the computation of two (2) or more vectors. Such vectors, for the purposes of this invention, shall hereafter be referred to as iEvent-vectors and iAlert-vectors. iEvent-vectors and iAlert-vectors are specifically meant to provide the basis for timely notification of relevant events and happenstance.


Facilitation of the type of notification sent when an iEvent-vector exceeds the threshold setting of an iAlert-vector depends upon whether the iAlert sentinel pertains to a person, place, or thing. Sentinels set on places and things will only generate notifications pertaining to threat events (i.e. repulsive inducements). Sentinels set on persons are more dynamic and might actually result in notifications intended to direct a person toward an event rather than away from it.



FIG. 3 depicts two (2) exemplary data structures with which to manage iAlert-vectors and the notifications that are the ultimate purpose of the iAlert-vector.


In the example illustrated in FIG. 3, all iAlert-vectors are maintained using data in two (2) tables: an iAlert Table 140 and a Notification Table 141.


Each row in the iAlert table 140 includes, but is not limited to, the following fields: iAlert_ID (i.e. the primary key), iAlert_initiated_by, Sentinel Type, Latitude, Longitude, iAlertThreshold, iAlert_Hysteresis, and Notification_Link. The iAlert_initiated_by field is a SPIN_ID value with which an entire row in the SPIN table 132 may be isolated. The iAlert_initiated_by field records the device that established the iAlert sentinel. A Sentinel Type field records whether the relevant iAlert pertains to a PERSON, PLACE, or THING. An iAlert_Threshold value denotes the base iEvent MAGNITUDE required to stimulate transmission of a notification. Additionally, an iAlert_Hysteresis value is used to prevent notification stutter pertaining to a particular event/happenstance. Once notification of an event has been transmitted, an “Event Concluded” notification, indicating the conclusion of an event, is not transmitted until the iEvent MAGNITUDE has been reduced to a value less than the difference between the iAlert_Threshold value and the iAlert_Hysteresis value (i.e. “iAlert_Threshold iAlert_Hysteresis”). Thus, use of the iAlert_Hysteresis value prevents a barrage of event notifications and “Event Concluded” transmissions, should the event MAGNITUDE flutter, slightly above and below the iAlert_Threshold value. Notification_Link fields are not allowed to be set to a TERMINATOR value, considering the primary reason to activate an iAlert sentinel is to receive some sort of notification, stimulated by an iEvent. Hence, there must always be at least one record in the Notification Table 141 for every record present in the iAlert Table 140. There may, however, be more than one record in the Notification Table 141 associated with a single record in the iAlert Table 140.


Each row in the Notification Table 141 includes, but is not limited to, a Notification_ID (i.e. the primary key), a SPIN_ID, and a Notification_Next Link. The SPIN ID field represents the device to which notifications shall be transmitted. The Notification_Next link value is used to identify the next device to which to transmit a notification. This linked list structure in the Notification Table allows a single sentinel detection to result in notification transmissions to multiple recipients. There will always be at least one row in the Notification Table for every row in the iAlert Table. The last row in a linked list of notification records associated with a single iAlert record will set the Notification_Next link value to a TERMINATOR value 142 to represent the end of the linked list.


This invention presumes that iAlert sentinels established for PLACEs and/or THINGs are intended to provide repulsive inducement. Repulsive inducements are transmitted to issue a warning on a wireless device that has activated a sentinel, so that the user of this wireless device may attempt to prevent or avoid negative effect to the PLACE or the THING that a notification is referring to, including but not limited to theft and/or damage.


This invention further presumes that iAlert sentinels established for PERSONs are intended to take full advantage of all facets of the Affinity Table (see FIG. 2) including, but not limited to, all attractive and repulsive inducements identified via the Affinity List and uniquely associated with the device that activated the iAlert sentinel upon the PERSON (i.e. iAlert_initiated_by).


In the example depicted in FIG. 3, an iAlert-vector is comprised of a single iAlert Table record, which is linked to three (3) Notification Table records. The device that activated the sentinel for the iAlert-vector in the example depicted in FIG. 3, is named as one of the three notification recipients. Therefore, the iAlert_initiated_by field in the iAlert Table record and the first Notification record in the notification linked list both link to the same SPIN Table record. The second and third Notification records in the notification linked list, link to different SPIN Table records.


Were the sentinel in the iAlert-vector providing overwatch for a PERSON, then the AffinityList indicated in the SPIN table would be dereferenced for all SPINs referenced by the notification linked list, such that any and all iEvents associated with the list of affinities for each SPIN would be evaluated for possible transmission of notification(s).



FIG. 4 depicts one (1) exemplary data structure with which to manage iEvent-vectors, in accordance with the principles of the present invention.


Each row in an iEvent-vector table is used to assess a particular event of interest and includes, but is not limited to, the following fields: iEvent_ID (i.e. the primary key), Event Type, Magnitude, Centroid X, Centroid_Y, Centroid_Z, Area_of Effect Radius, Shape_Type, Angle_of Rotation, Angular_Extent, Dist2Foci-A, Dist2Foci-B, Primary_Length and Secondary_Length. The Event_Type and Magnitude fields are both used to assess and determine notifications that are relevant to a particular iEvent. Centroid_X, Centroid_Y, and Centroid_Z fields encompass three (3) coordinates used to record the center of an event. The Area of Effect Radius is a radius value that indicates the general area of effect and provides very rapid assessment as to whether further analysis of the event is necessary. If the central point and radius of the iEvent-vector does not encompass the location of an iAlert-vector, then notification is not merited. The Shape_Type enumerated field includes but is not limited to the following values: POINT, CIRCLE, ELLIPSE, ARC, and ARC_BAND. The Angle_of_Rotation value is measured from true North. The Angular_Extent field is used to assess ARCs and ARC_BANDs. The Distance to Foci A (i.e. Dist2Foci-A) and Distance to Foci B (i.e. Dist2Foci-B) values designate the Foci of an ellipse measured from the Centroid. The Primary_Length and Secondary_Length values represent either the Major and Minor Axes lengths for an ellipse or the inner and outer radius values for ARCs and ARC_BANDs.


The present invention includes but is not limited to three (3) different action types for iEvent-vectors: INITIATE, UPDATE, and CLEAR.


The INITIATE action causes a new row to be allocated to an iEvent-vector table. A new row in an iEvent-vector table preferably must include Event_Type, Magnitude, Centroid location, estimated Area_of_Effect_Radius, Shape_Type, and measurements necessary to define the shape indicated in the Shape_Type field. Declaration of an INITIATE action will stimulate the evaluation of iAlert-vectors within the area of effect for potential transmission of notifications.


An UPDATE action preferably must designate the iEvent_ID of the specific iEvent-vector being updated and then may include some subset of the following parameters: Magnitude, Centroid location, Area_of_Effect_Radius, Shape_Type and all measurements necessary to define the particular shape indicated in the Shape_Type field. UPDATE actions may not change Event_Type. Declaration of an UPDATE action will stimulate evaluation of all iAlert-vectors within the area of effect as well as all iAlert-vectors that have previously resulted in the transmission of a notification. iAlert-vectors for which notifications were previously sent, but are no longer within the area of effect, will receive an “Event Concluded” notification. A CLEAR action must designate the iEvent_ID of the specific iEvent-vector being canceled and will force “Event Concluded” notifications to be sent to all recipients of iAlert-vector notifications. The CLEAR action will delete the iEvent-vector row associated with the designated iEvent ID value.


Another embodiment of the present invention uses a GeoNEXUS. When an iEvent-vector is INITIATED, UPDATED, or CLEARED, the GeoNEXUS determines which iAlert-vectors are within close enough proximity to the iEvent-vector to be evaluated for possible notification. For the purposes of this embodiment the proximity evaluation is designed for speed of performance during proximity evaluation processing.



FIG. 5 depicts a wireless device user's location, in accordance with the principles of the present invention.


In particular, as shown in FIG. 5, the present invention reduces the location of an iAlert-vector or iEvent-vector, represented, e.g., in decimal degrees of latitude and longitude, into indices of latitude and indices of longitude within four (4) layers: 1) Primary 150: tens of degrees (˜700 statute mile resolution); 2) Secondary 151: degrees (˜70 statute mile resolution); 3) Tertiary 152: minutes (6000 foot resolution); and 4) Quaternary 153: seconds (˜100 foot resolution). This implementation figuratively covers the Earth's surface with successively finer grained gridlines. Seconds of latitude and longitude yield a grid whose vertices are approximately 100 feet apart at the equator and somewhat closer together the farther away from the equator (North or South) the device is located.


Should the need arise to attain even finer granularity than seconds, a fifth (Quinary) and even sixth (Senary) layer may be added to represent 10ths of seconds (˜10 feet) and 100ths of seconds (˜12 inches).


Every time a location is registered, the GeoNEXUS will save the associated identifier, location (latitude and longitude), and optimization indices in a LOC table.



FIG. 6 shows an exemplary location (LOC) table, in accordance with the principles of the present invention.


In particular, as shown in FIG. 6, the Lat and Lon values are normalized to be decimal degrees in the range −90.0 through +90.0 for Latitude and −180.0 through +180.0 for Longitude. The indices are computed thusly:

PrimaryX=int(round((Lon/10.0)−0.5))
PrimaryY=int(round((Lat/10.0)−0.5))
PrimaryZ=Altitude modulo 700 statute miles
SecondaryX=int(truncate(Lon−(PrimaryX*10.0)))
SecondaryY=int(truncate(Lat−(PrimaryY*10.0)))
SecondaryZ=Altitude modulo 70 statute miles
TertiaryX=int(truncate((Lon−((PrimaryX*10.0)+SecondaryX))*60.0))
TertiaryY=int(truncate((Lat −((PrimaryY*10.0)+SecondaryY))*60.0))
TertiaryZ=Altitude modulo 6000 feet
QuaternaryX=int(truncate((Lon−((PrimaryX*10.0)+SecondaryX+(TertiaryX/60.0)))*3600.0))
QuaternaryY=int(truncate((Lat−((PrimaryY*10.0)+SecondaryY+(TertiaryY/60.0)))*3600.0))
QuaternaryZ=Altitude modulo 100 feet


Note that these equations presume that the round ( ) function always rounds an “n.5” value up so that 0.5 becomes 1.0, 2.5 becomes 3.0, −3.5 becomes −3.0, etc. Some adjustments may be necessary to accommodate specific hardware architectures, operating systems, and compilers, as will be appreciated by those of skill in the art.


The intent, though, is to compute an index based on the lower left corner of the square in which the iAlert-vector/iEvent-vector is located. The Primary square (See ‘Q’ in FIG. 5) is a 10 degree by 10 degree square. The Secondary square (See ‘R’ in FIG. 5) is a one degree by one degree square located within the Primary. The Tertiary square (See ‘S’ in FIG. 5) is a one minute by one minute square located within the Secondary. The Quaternary square (See ‘T’ in FIG. 5) is a one second by one second square located within the Tertiary.


These computations produce values in the following ranges: −18<=PrimaryX<=18 −9<=PrimaryY<=9 −1<=PrimaryZ<=36 0<=SecondaryX<=9 0<=SecondaryY<=9 −1<=SecondaryZ<=357 0<=TertiaryX<=60 0<=TertiaryY<=60 −1<=TertiaryZ<=22,000 0<=QuaternaryX<=60 0<=QuaternaryY<=60 −3<=QuaternaryZ<=1.32e06



FIG. 7 shows an exemplary primary matrix, in accordance with the principles of the present invention.


In particular, as shown in the primary matrix of FIG. 7, the GeoNEXUS maintains a collection of matrices. This collection of matrices always includes a matrix for the Primary indices (i.e. a “Primary Matrix”).


The primary matrix is accompanied by a PrimaryCount indicating how many iAlert-vectors/iEvent-vectors are present.


The Primary Matrix is also accompanied by an array or list of the primary matrix elements in which iAlert-vectors/iEvent-vectors can be found. (The list is empty if PrimaryCount is zero.)


Each element in the 36×18 Primary matrix contains: (1) a count of how many iAlert-vectors/iEvent-vectors are present in the corresponding 10 deg X 10 deg area; and (2) a reference to a Secondary Matrix. (The reference is NULL if count is zero). Secondary (10×10 matrix), Tertiary (60×60), and Quaternary (60×60) matrices are allocated, maintained, and eliminated as needed to manage GeoNEXUS memory use.


Each Secondary Matrix is accompanied by a SecondaryCount indicating how many iAlert-vectors/iEvent-vectors are present in the corresponding 10 deg×10 deg area.


Each Secondary Matrix is also accompanied by an array or list of the secondary matrix elements in which iAlert-vectors/iEvent-vectors can be found. (The list is empty if its SecondaryCount is zero.)


Each element in a 10×10 Secondary matrix contains: (1) a count of how many iAlert-vectors/iEvent-vectors are present in that particular 1 deg×1 deg area; and (2) a reference to a Tertiary Matrix. (The reference will be NULL if the count is zero.)


Each Tertiary Matrix is accompanied by a TertiaryCount indicating how many iAlert-vectors/iEvent-vectors are present in the corresponding 1 deg×1 deg area.


Each Tertiary Matrix is also accompanied by an array or list of the tertiary matrix elements in which iAlert-vectors/iEvent-vectors can be found. (The list is empty if its TertiaryCount is zero.)


Each element in a 60×60 Tertiary matrix contains: (1) a count of how many iAlert-vectors/iEvent-vectors are present in that particular 1minute X 1minute area; and (2) a reference to a Quaternary Matrix. (The reference is NULL if count is zero.)


Each Quaternary Matrix is accompanied by a QuaternaryCount indicating how many iAlert-vectors/iEvent-vectors are present in the corresponding 1min×1min area.


Each Quaternary Matrix is also accompanied by an array or list of the quaternary elements in which iAlert-vectors/iEvent-vectors can be found. (The list is empty if QuaternaryCount is zero.)


Each element in a 60×60 Quaternary matrix contains: (1) a count of how many iAlert-vectors/iEvent-vectors are present in that particular 1second×1second area; and (2) an array or list of iAlert-vectors/iEvent-vectors Identifiers that are present in the corresponding 1sec×1sec area. (The list is empty if count is zero.)


The evaluation of ‘Z’ axis differences are preferably not managed in a matrix structure but rather are evaluated in near real-time as a simple difference of like Z values (i.e. primary, secondary, tertiary, etc.). If the absolute value of the computed Z-difference (i.e. delta Z) is within the defined vertical bounds of proximity, then proximity has been successfully established.


Maintenance of this four (4) tier structure is complex but considered obvious to those skilled in data structures and is not described further in this disclosure.


This four (4) tier data structure makes it possible for the GeoNEXUS to rapidly identify all of the iAlert-vectors in a predefined or preconfigured close proximity to an iEvent-vector so that evaluation of notifications can be resolved in a timely manner.


Once the proximity of iEvent-vectors to iAlert-vectors has been established, it is a simple matter to evaluate the Magnitude value in the iEvent-vector versus the Alert_Threshold value in the iAlert-vector. Evaluation of the iAlert-vector versus the iEvent-vector determines whether or not it is necessary to cycle through Notification records associated with the iAlert-vector to transmit the appropriate form of notification to the intended recipient.


The iAlert-Hysteresis value of the iAlert-vector is used with both the Magnitude of the iEvent-vector and the juxtaposition of location between the iEvent-vector and the iAlert-vector (i.e. proximity). Use of the iAlert_Hysteresis value prevents small fluxuations in the parameters of the iEvent-vector from pummeling recipients with a barrage of notifications. The value for the iAlert_Hysteresis is chosen by the user who established the iAlert sentinel, however, so the frequency of notification to the intended recipients varies from iAlert-vector to iAlert-vector.


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. A method of providing notification to a wireless device regarding an effect from an event distant from said wireless device but having an area of effect about which a user of said wireless device has interest, comprising: obtaining at least one affinity established for notification to a given wireless device;defining a sphere of influence (SPIN) about a given event distant from said wireless device;recognizing a relationship between said at least one affinity and said sphere of influence with a match between said at least one affinity and said sphere of influence; andinitiating a relevant notification to said given wireless device.
  • 2. The method of providing notification to said wireless device regarding an effect from an event distant from said wireless device but having an area of effect about which a user of said wireless device has interest according to claim 1, further comprising: providing clarifying information to said wireless device relating to circumstances about said event distant from said wireless device.
  • 3. The method of providing notification to said wireless device regarding an effect from an event distant from said wireless device but having an area of effect about which a user of said wireless device has interest according to claim 1, wherein: an effect on said user of said wireless device is indirect to effects due to said given event.
  • 4. The method of providing notification to said wireless device regarding an effect from an event distant from said wireless device but having an area of effect about which a user of said wireless device has interest according to claim 1, wherein: said given event is distant to said wireless device but proximate to a wireless device relating to another whom said user of said wireless device has a predefined interest.
  • 5. The method of providing notification to said wireless device regarding an effect from an event distant from said wireless device but having an area of effect about which a user of said wireless device has interest according to claim 1, wherein: said given event is proximate to a distant location about which said user of said wireless device has a predefined interest.
  • 6. The method of providing notification to said wireless device regarding an effect from an event distant from said wireless device but having an area of effect about which a user of said wireless device has interest according to claim 1, wherein: said relationship between said at least one affinity and said sphere of influence is determined using a keyword-list database.
  • 7. The method of providing notification to said wireless device regarding an effect from an event distant from said wireless device but having an area of effect about which a user of said wireless device has interest according to claim 1, wherein: said relationship between said at least one affinity and said sphere of influence is determined using an affinity-list database.
  • 8. The method of providing notification to said wireless device regarding an effect from an event distant from said wireless device but having an area of effect about which a user of said wireless device has interest according to claim 1, wherein: said relationship between said at least one affinity and said sphere of influence is determined using a spin-list database.
Parent Case Info

The present application claims priority from U.S. Provisional 61/457,744, entitled “iALERT ENHANCED ALERT MANAGER” to Pitt, Ginter, Aryana, and Mitchell, filed May 25, 2011; and is a continuation-in-part of U.S. application Ser. No. 13/064,796, entitled “N-Dimensional Affinity Confluencer” to Pitt, Ginter, Hines, Burton and Ramberg, filed Apr. 15, 2011, the entirety of both of which are explicitly incorporated herein by reference.

US Referenced Citations (742)
Number Name Date Kind
1103073 O'Connell Jul 1914 A
4445118 Taylor Apr 1984 A
4494119 Wimbush Jan 1985 A
4651156 Martinez Mar 1987 A
4706275 Kamil Nov 1987 A
4868570 Davis Sep 1989 A
4891638 Davis Jan 1990 A
4891650 Sheffer Jan 1990 A
4910767 Brugliera et al. Mar 1990 A
4952928 Carroll Aug 1990 A
4972484 Theile Nov 1990 A
5014206 Scribner May 1991 A
5043736 Darnell Aug 1991 A
5055851 Sheffer Oct 1991 A
5068656 Sutherland Nov 1991 A
5068891 Marshall Nov 1991 A
5070329 Jasimaki Dec 1991 A
5081667 Drori Jan 1992 A
5119104 Heller Jun 1992 A
5126722 Kamis Jun 1992 A
5144283 Arens Sep 1992 A
5161180 Chavous Nov 1992 A
5166972 Smith Nov 1992 A
5177478 Wagai Jan 1993 A
5193215 Olmer Mar 1993 A
5208756 Song May 1993 A
5214789 George May 1993 A
5218367 Scheffer Jun 1993 A
5223844 Mansell Jun 1993 A
5239570 Koster Aug 1993 A
5265630 Hartmann Nov 1993 A
5266944 Carroll Nov 1993 A
5283570 DeLuca Feb 1994 A
5289527 Tiedemann Feb 1994 A
5293642 Lo Mar 1994 A
5299132 Wortham Mar 1994 A
5301354 Schwendeman Apr 1994 A
5311516 Kuznicke May 1994 A
5325302 Izidon Jun 1994 A
5327529 Fults Jul 1994 A
5334974 Simms Aug 1994 A
5335246 Yokev Aug 1994 A
5343493 Karimulah Aug 1994 A
5347568 Moody Sep 1994 A
5351235 Lahtinen Sep 1994 A
5361212 Class Nov 1994 A
5363425 Mufti Nov 1994 A
5365451 Wang Nov 1994 A
5374936 Feng Dec 1994 A
5379451 Nakagoshi Jan 1995 A
5381338 Wysocki Jan 1995 A
5387993 Heller Feb 1995 A
5388147 Grimes Feb 1995 A
5390339 Bruckery Feb 1995 A
5394158 Chia Feb 1995 A
5396227 Carroll Mar 1995 A
5398190 Wortham Mar 1995 A
5406614 Hara Apr 1995 A
5418537 Bird May 1995 A
5422813 Schuchman Jun 1995 A
5423076 Westergren Jun 1995 A
5432841 Rimer Jul 1995 A
5434789 Fraker Jul 1995 A
5454024 Lebowitz Sep 1995 A
5461390 Hosher Oct 1995 A
5470233 Fruchterman Nov 1995 A
5479408 Will Dec 1995 A
5479482 Grimes Dec 1995 A
5485161 Vaughn Jan 1996 A
5485163 Singer Jan 1996 A
5488563 Chazelle Jan 1996 A
5494091 Freeman Feb 1996 A
5497149 Fast Mar 1996 A
5506886 Maine Apr 1996 A
5508931 Snider Apr 1996 A
5513243 Kage Apr 1996 A
5515287 Hakoyama May 1996 A
5517199 DiMattei May 1996 A
5519403 Bickley May 1996 A
5530655 Lokhoff Jun 1996 A
5530914 McPheters Jun 1996 A
5532690 Hertel Jul 1996 A
5535434 Siddoway Jul 1996 A
5539395 Buss Jul 1996 A
5539398 Hall Jul 1996 A
5539829 Lokhoff Jul 1996 A
5543776 L'Esperance Aug 1996 A
5546445 Dennison Aug 1996 A
5552772 Janky Sep 1996 A
5555286 Tendler Sep 1996 A
5568119 Schipper Oct 1996 A
5568153 Beliveau Oct 1996 A
5574648 Pilley Nov 1996 A
5579372 Angstrom Nov 1996 A
5588009 Will Dec 1996 A
5592535 Klotz Jan 1997 A
5594780 Wiedeman Jan 1997 A
5604486 Lauro Feb 1997 A
5606313 Allen Feb 1997 A
5606618 Lokhoff Feb 1997 A
5606850 Nakamura Mar 1997 A
5610815 Gudat Mar 1997 A
5611050 Theimer Mar 1997 A
5614890 Fox Mar 1997 A
5615116 Gudat Mar 1997 A
5621793 Bednarek Apr 1997 A
5628051 Salin May 1997 A
5629693 Janky May 1997 A
5633912 Tsoi May 1997 A
5636276 Brugger Jun 1997 A
5661652 Sprague Aug 1997 A
5661755 Van De Kerkhof Aug 1997 A
5682600 Salin Oct 1997 A
5689245 Noreen Nov 1997 A
5699053 Jonsson Dec 1997 A
5704029 Wright, Jr. Dec 1997 A
5721781 Deo Feb 1998 A
5731785 Lemelson Mar 1998 A
5740534 Ayerst Apr 1998 A
5761618 Lynch Jun 1998 A
5765152 Erickson Jun 1998 A
5767795 Schaphorst Jun 1998 A
5768509 Gunluk Jun 1998 A
5771353 Eggleston Jun 1998 A
5774533 Patel Jun 1998 A
5774670 Montulli Jun 1998 A
5787357 Salin Jul 1998 A
5794142 Vanttila Aug 1998 A
5797094 Houde Aug 1998 A
5797096 Lupien Aug 1998 A
5802492 DeLorrme Sep 1998 A
5806000 Vo Sep 1998 A
5809415 Rossmann Sep 1998 A
5812086 Bertiger Sep 1998 A
5812087 Krasner Sep 1998 A
5822700 Hult Oct 1998 A
5828740 Khue Oct 1998 A
5835907 Newman Nov 1998 A
5841396 Krasner Nov 1998 A
5857201 Wright, Jr. Jan 1999 A
5864667 Barkam Jan 1999 A
5874914 Krasner Feb 1999 A
5896369 Warsta Apr 1999 A
5920821 Seazholtz Jul 1999 A
5922074 Richard Jul 1999 A
5930250 Klok Jul 1999 A
5930701 Skog Jul 1999 A
5943399 Banister Aug 1999 A
5945944 Krasner Aug 1999 A
5946629 Sawyer Aug 1999 A
5946630 Willars Aug 1999 A
5950130 Coursey Sep 1999 A
5950137 Kim Sep 1999 A
5953398 Hill Sep 1999 A
5960362 Grob Sep 1999 A
5974054 Couts Oct 1999 A
5978685 Laiho Nov 1999 A
5983099 Yao Nov 1999 A
5987323 Huotari Nov 1999 A
5998111 Abe Dec 1999 A
5999124 Sheynblat Dec 1999 A
6014602 Kithol Jan 2000 A
6032051 Hall Feb 2000 A
6035025 Hanson Mar 2000 A
6049710 Nilsson Apr 2000 A
6052081 Krasner Apr 2000 A
6058300 Hanson May 2000 A
6061018 Sheynblat May 2000 A
6061346 Nordman May 2000 A
6064336 Krasner May 2000 A
6064875 Morgan May 2000 A
6067045 Castelloe May 2000 A
6070067 Nguyen May 2000 A
6075982 Donovan Jun 2000 A
6081229 Soliman Jun 2000 A
6081508 West Jun 2000 A
6085320 Kaliski, Jr. Jul 2000 A
6101378 Barabash Aug 2000 A
6104931 Havinis Aug 2000 A
6108533 Brohoff Aug 2000 A
6121923 King Sep 2000 A
6122503 Daly Sep 2000 A
6122520 Want Sep 2000 A
6124810 Segal Sep 2000 A
6131028 Whittington Oct 2000 A
6131067 Girerd Oct 2000 A
6133874 Krasner Oct 2000 A
6134316 Kallioniemi Oct 2000 A
6134483 Vayanos Oct 2000 A
6138003 Kingdon Oct 2000 A
6148197 Bridges Nov 2000 A
6148198 Anderson Nov 2000 A
6149353 Nilsson Nov 2000 A
6150980 Krasner Nov 2000 A
6154172 Piccionelli Nov 2000 A
6169891 Gorham Jan 2001 B1
6169901 Boucher Jan 2001 B1
6169902 Kawamoto Jan 2001 B1
6173181 Losh Jan 2001 B1
6178505 Schneider Jan 2001 B1
6178506 Quick, Jr. Jan 2001 B1
6181935 Gossman Jan 2001 B1
6181939 Ahvenainen Jan 2001 B1
6188354 Soliman Feb 2001 B1
6188752 Lesley Feb 2001 B1
6188909 Alanara Feb 2001 B1
6189098 Kaliski, Jr. Feb 2001 B1
6195555 Dent Feb 2001 B1
6195557 Havinis Feb 2001 B1
6198431 Gibson Mar 2001 B1
6199045 Giniger Mar 2001 B1
6199113 Alegre Mar 2001 B1
6205330 Winbladh Mar 2001 B1
6208290 Krasner Mar 2001 B1
6208854 Roberts Mar 2001 B1
6215441 Moeglein Apr 2001 B1
6219557 Havinis Apr 2001 B1
6223046 Hamill-Keays Apr 2001 B1
6226529 Bruno May 2001 B1
6239742 Krasner May 2001 B1
6247135 Feague Jun 2001 B1
6249680 Wax Jun 2001 B1
6249744 Morita Jun 2001 B1
6249873 Richard Jun 2001 B1
6253074 Carlsson Jun 2001 B1
6253203 O'Flaherty Jun 2001 B1
6260147 Quick, Jr. Jul 2001 B1
6266614 Alumbaugh Jul 2001 B1
6275692 Skog Aug 2001 B1
6275849 Ludwig Aug 2001 B1
6278701 Ayyagari Aug 2001 B1
6289373 Dezonno Sep 2001 B1
6297768 Allen, Jr. Oct 2001 B1
6307504 Sheynblat Oct 2001 B1
6308269 Proidl Oct 2001 B2
6313786 Sheynblat Nov 2001 B1
6317594 Gossman Nov 2001 B1
6321091 Holland Nov 2001 B1
6321092 Fitch Nov 2001 B1
6321257 Kotola Nov 2001 B1
6324524 Lent Nov 2001 B1
6327473 Soliman Dec 2001 B1
6327479 Mikkola Dec 2001 B1
6330454 Verdonk 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
6397074 Pihl May 2002 B1
6400314 Krasner Jun 2002 B1
6400958 Isomursu Jun 2002 B1
6411254 Moeglein Jun 2002 B1
6421002 Krasner Jul 2002 B2
6427001 Contractor Jul 2002 B1
6429808 King Aug 2002 B1
6433734 Krasner Aug 2002 B1
6434381 Moore 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
6504491 Christians Jan 2003 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
6526026 Menon Feb 2003 B1
6529500 Pandharipande Mar 2003 B1
6529829 Turetzky Mar 2003 B2
6531982 White Mar 2003 B1
6538757 Sansone Mar 2003 B1
6539200 Schiff Mar 2003 B1
6539232 Hendrey et al. Mar 2003 B2
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
6553236 Dunko Apr 2003 B1
6556832 Soliman Apr 2003 B1
6560456 Lohtia May 2003 B1
6560461 Fomukong May 2003 B1
6560534 Abraham May 2003 B2
6564261 Gudjonsson May 2003 B1
6570530 Gaal May 2003 B2
6571095 Koodli May 2003 B1
6574558 Kohli Jun 2003 B2
6580390 Hay Jun 2003 B1
6584552 Kuno Jun 2003 B1
6587691 Granstam Jul 2003 B1
6594500 Bender Jul 2003 B2
6597311 Sheynblat Jul 2003 B2
6600927 Hamilton 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
6618593 Drutman Sep 2003 B1
6618670 Chansarkar Sep 2003 B1
6621452 Knockeart Sep 2003 B2
6621810 Leung Sep 2003 B1
6628233 Knockeart Sep 2003 B2
6633255 Krasner Oct 2003 B2
6640184 Rabe Oct 2003 B1
6650288 Pitt Nov 2003 B1
6661372 Girerd Dec 2003 B1
6665539 Sih Dec 2003 B2
6665541 Krasner Dec 2003 B1
6671620 Garin Dec 2003 B1
6675017 Zellner Jan 2004 B1
6677894 Sheynblat Jan 2004 B2
6680694 Knockheart Jan 2004 B1
6680695 Turetzky Jan 2004 B2
6687504 Raith Feb 2004 B1
6690940 Brown Feb 2004 B1
6691019 Seeley Feb 2004 B2
6694258 Johnson Feb 2004 B2
6694351 Shaffer Feb 2004 B1
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
6718174 Vayanos Apr 2004 B2
6720915 Sheynblat Apr 2004 B2
6721396 Chin Apr 2004 B2
6721578 Minear Apr 2004 B2
6721871 Piispanen Apr 2004 B2
6724342 Bloebaum Apr 2004 B2
6725159 Krasner Apr 2004 B2
6728701 Stoica Apr 2004 B1
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
6744856 Karnik Jun 2004 B2
6744858 Ryan Jun 2004 B1
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
6757545 Nowak Jun 2004 B2
6771742 McCalmont Aug 2004 B2
6771971 Smith Aug 2004 B2
6772340 Peinado Aug 2004 B1
6775255 Roy Aug 2004 B1
6775267 Kung Aug 2004 B1
6775534 Lindgren Aug 2004 B2
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
6795444 Vo Sep 2004 B1
6795699 McCraw Sep 2004 B1
6799049 Zellner Sep 2004 B1
6799050 Krasner Sep 2004 B1
6801159 Swope Oct 2004 B2
6804524 Vandermeijden Oct 2004 B1
6807534 Erickson Oct 2004 B1
6810323 Bullock Oct 2004 B1
6813264 Vassilovski Nov 2004 B2
6813499 McDonnell Nov 2004 B2
6813560 Van Diggelen Nov 2004 B2
6816111 Krasner Nov 2004 B2
6816580 Timmins Nov 2004 B2
6816710 Krasner Nov 2004 B2
6816719 Heinonen Nov 2004 B1
6816734 Wong Nov 2004 B2
6820069 Kogan Nov 2004 B1
6829475 Lee Dec 2004 B1
6832373 O'Neill Dec 2004 B2
6839020 Geier Jan 2005 B2
6839021 Sheynblat Jan 2005 B2
6839417 Weisman Jan 2005 B2
6842715 Gaal Jan 2005 B1
6847618 Laursen Jan 2005 B2
6847822 Dennison Jan 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
6867733 Sandhu Mar 2005 B2
6867734 Voor Mar 2005 B2
6873854 Crockett Mar 2005 B2
6876734 Summers Apr 2005 B1
6882850 McConnell et al. Apr 2005 B2
6885874 Grube Apr 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
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
6912230 Salkini Jun 2005 B1
6912395 Benes Jun 2005 B2
6912545 Lundy Jun 2005 B1
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
6940826 Simard Sep 2005 B1
6940950 Dickinson et al. Sep 2005 B2
6941144 Stein Sep 2005 B2
6944540 King Sep 2005 B2
6947772 Minear Sep 2005 B2
6950058 Davis Sep 2005 B1
6957073 Bye Oct 2005 B2
6961562 Ross Nov 2005 B2
6963557 Knox Nov 2005 B2
6965754 King Nov 2005 B2
6965767 Maggenti Nov 2005 B2
6968044 Beason Nov 2005 B2
6970917 Kushwaha Nov 2005 B1
6973320 Brown Dec 2005 B2
6975266 Abraham Dec 2005 B2
6978453 Rao Dec 2005 B2
6980816 Rohles Dec 2005 B2
6985747 Chithambaram Jan 2006 B2
6993355 Pershan Jan 2006 B1
6996720 DeMello Feb 2006 B1
6999782 Shaughnessy Feb 2006 B2
7024321 Deninger Apr 2006 B1
7024393 Peinado Apr 2006 B1
7047411 DeMello May 2006 B1
7065351 Carter Jun 2006 B2
7065507 Mohammed Jun 2006 B2
7072667 Olrik Jul 2006 B2
7079857 Maggenti Jul 2006 B2
7103018 Hansen Sep 2006 B1
7103574 Peinado Sep 2006 B1
7106717 Rousseau Sep 2006 B2
7110773 Wallace Sep 2006 B1
7123874 Brennan Oct 2006 B1
7136466 Gao Nov 2006 B1
7136838 Peinado Nov 2006 B1
7145900 Nix Dec 2006 B2
7151946 Maggenti Dec 2006 B2
7174153 Ehlers Feb 2007 B2
7177397 McCalmont Feb 2007 B2
7177398 Meer Feb 2007 B2
7177399 Dawson Feb 2007 B2
7200380 Havlark Apr 2007 B2
7209758 Moll et al. Apr 2007 B1
7209969 Lahti Apr 2007 B2
7218940 Niemenmaa May 2007 B2
7221959 Lindqvist May 2007 B2
7245900 Lamb Jul 2007 B1
7246187 Ezra Jul 2007 B1
7260186 Zhu Aug 2007 B2
7260384 Bales et al. Aug 2007 B2
7277938 Duimovich Oct 2007 B2
7302582 Snapp Nov 2007 B2
7321773 Hines Jan 2008 B2
7330899 Wong Feb 2008 B2
7333480 Clarke Feb 2008 B1
7369508 Parantainen May 2008 B2
7369530 Keagy May 2008 B2
7382773 Schoeneberger Jun 2008 B2
7392240 Scriffignano Jun 2008 B2
7394896 Norton Jul 2008 B2
7428571 Ichimura Sep 2008 B2
7436785 McMullen Oct 2008 B1
7440442 Grabelsky et al. Oct 2008 B2
7444342 Hall Oct 2008 B1
7450951 Vimpari Nov 2008 B2
7471236 Pitt Dec 2008 B1
7522182 Bang Apr 2009 B2
7573982 Breen Aug 2009 B2
7602886 Beech Oct 2009 B1
7623447 Faccin Nov 2009 B1
7711094 Olshansky May 2010 B1
7764961 Zhu Jul 2010 B2
7783297 Ishii Aug 2010 B2
7787611 Kotelly Aug 2010 B1
7822391 Delker Oct 2010 B1
7822871 Stolorz Oct 2010 B2
7825780 Pitt Nov 2010 B2
7881233 Bieselin Feb 2011 B2
7937067 Maier May 2011 B2
8200291 Steinmetz Jun 2012 B2
8688087 Pitt et al. Apr 2014 B2
20010011247 O'Flaherty Aug 2001 A1
20010040886 Jimenez Nov 2001 A1
20010049274 Degraeve Dec 2001 A1
20020002036 Uehara Jan 2002 A1
20020037735 Maggenti Mar 2002 A1
20020052214 Maggenti May 2002 A1
20020061760 Maggenti May 2002 A1
20020069079 Vega Jun 2002 A1
20020069529 Wieres Jun 2002 A1
20020077083 Zellner Jun 2002 A1
20020077084 Zellner Jun 2002 A1
20020077118 Zellner Jun 2002 A1
20020077897 Zellner Jun 2002 A1
20020085538 Leung Jul 2002 A1
20020086676 Hendrey Jul 2002 A1
20020098832 Fleischer Jul 2002 A1
20020102996 Jenkins Aug 2002 A1
20020102999 Maggenti Aug 2002 A1
20020111172 DeWolf Aug 2002 A1
20020112047 Kushwaha Aug 2002 A1
20020118650 Jagadeesan Aug 2002 A1
20020123327 Vataja Sep 2002 A1
20020126656 Park Sep 2002 A1
20020138650 Yamamoto Sep 2002 A1
20020147023 Sawada Oct 2002 A1
20020156732 Odijk Oct 2002 A1
20020158777 Flick Oct 2002 A1
20020164998 Younis Nov 2002 A1
20020173317 Nykanen Nov 2002 A1
20020174073 Nordman Nov 2002 A1
20020191595 Mar Dec 2002 A1
20030009277 Fan Jan 2003 A1
20030009602 Jacobs Jan 2003 A1
20030012148 Peters Jan 2003 A1
20030013449 Hose Jan 2003 A1
20030016804 Sheha Jan 2003 A1
20030026245 Ejzak Feb 2003 A1
20030037163 Kitada Feb 2003 A1
20030040272 Lelievre Feb 2003 A1
20030044654 Holt Mar 2003 A1
20030063730 Woodring Apr 2003 A1
20030065788 Salomaki Apr 2003 A1
20030072318 Lam Apr 2003 A1
20030078064 Chan Apr 2003 A1
20030081557 Mettala May 2003 A1
20030086422 Klinker et al. May 2003 A1
20030086539 McCalmont May 2003 A1
20030100320 Ranjan May 2003 A1
20030101329 Lahti May 2003 A1
20030101341 Kettler May 2003 A1
20030103484 Oommen Jun 2003 A1
20030108176 Kung Jun 2003 A1
20030109245 McCalmont Jun 2003 A1
20030114157 Spitz Jun 2003 A1
20030118160 Holt Jun 2003 A1
20030119521 Tipnis Jun 2003 A1
20030119528 Pew Jun 2003 A1
20030125042 Olrik Jul 2003 A1
20030137961 Tsirtsis 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
20030163483 Zingher et al. Aug 2003 A1
20030169881 Niedermeyer Sep 2003 A1
20030186709 Rhodes Oct 2003 A1
20030187803 Pitt Oct 2003 A1
20030196105 Fineberg Oct 2003 A1
20030204640 Sahinoja Oct 2003 A1
20030223381 Schroderus Dec 2003 A1
20040002326 Maher Jan 2004 A1
20040032485 Stephens Feb 2004 A1
20040043775 Kennedy Mar 2004 A1
20040044623 Wake Mar 2004 A1
20040047461 Weisman Mar 2004 A1
20040068724 Gardner Apr 2004 A1
20040070515 Burkley Apr 2004 A1
20040077359 Bernas Apr 2004 A1
20040078694 Lester Apr 2004 A1
20040092250 Valloppillil May 2004 A1
20040098497 Banet May 2004 A1
20040107143 Niemi Jun 2004 A1
20040132465 Mattila Jul 2004 A1
20040150518 Phillips Aug 2004 A1
20040152493 Phillips Aug 2004 A1
20040181689 Kiyoto Sep 2004 A1
20040184584 McCalmont Sep 2004 A1
20040185875 Diacakis Sep 2004 A1
20040190497 Knox Sep 2004 A1
20040198332 Lundsgaard Oct 2004 A1
20040198386 Dupray Oct 2004 A1
20040203876 Drawert Oct 2004 A1
20040203922 Hines Oct 2004 A1
20040205151 Sprigg Oct 2004 A1
20040209594 Naboulsi Oct 2004 A1
20040229632 Flynn Nov 2004 A1
20040235493 Ekerborn Nov 2004 A1
20040242238 Wang Dec 2004 A1
20040267445 De Luca Dec 2004 A1
20050003797 Baldwin Jan 2005 A1
20050028034 Gantman Feb 2005 A1
20050030977 Casey Feb 2005 A1
20050039178 Marolia Feb 2005 A1
20050041578 Huotari Feb 2005 A1
20050043037 Ioppe Feb 2005 A1
20050053209 D'Evelyn Mar 2005 A1
20050071251 Linden Mar 2005 A1
20050071671 Karaoguz Mar 2005 A1
20050074107 Renner Apr 2005 A1
20050083911 Grabelsky Apr 2005 A1
20050086467 Asokan Apr 2005 A1
20050090236 Schwinke Apr 2005 A1
20050107673 Ball May 2005 A1
20050112030 Gaus May 2005 A1
20050119012 Merheb Jun 2005 A1
20050125376 Curtis et al. Jun 2005 A1
20050134504 Harwood Jun 2005 A1
20050135569 Dickinson et al. Jun 2005 A1
20050136885 Kaltsukis Jun 2005 A1
20050148346 Maloney Jul 2005 A1
20050149430 Williams Jul 2005 A1
20050169248 Truesdale Aug 2005 A1
20050174991 Keagy Aug 2005 A1
20050186937 Graham Aug 2005 A1
20050190892 Dawson Sep 2005 A1
20050192822 Hartenstein Sep 2005 A1
20050201358 Nelson Sep 2005 A1
20050201529 Nelson Sep 2005 A1
20050209995 Aksu Sep 2005 A1
20050213716 Zhu Sep 2005 A1
20050215233 Perera Sep 2005 A1
20050216300 Appelman Sep 2005 A1
20050232252 Hoover Oct 2005 A1
20050238156 Turner Oct 2005 A1
20050250516 Shim Nov 2005 A1
20050259675 Tuohino Nov 2005 A1
20050265318 Khartabil Dec 2005 A1
20050271029 Iffland Dec 2005 A1
20050282518 D'Evelyn Dec 2005 A1
20050287979 Rollender Dec 2005 A1
20050289097 Trossen Dec 2005 A1
20060008065 Longman et al. Jan 2006 A1
20060010200 Mousseau Jan 2006 A1
20060020424 Quindel Jan 2006 A1
20060023747 Koren et al. Feb 2006 A1
20060026288 Acharya Feb 2006 A1
20060036680 Shim Feb 2006 A1
20060053225 Poikselka Mar 2006 A1
20060058042 Shim Mar 2006 A1
20060058045 Nilsen Mar 2006 A1
20060058102 Nguyen et al. Mar 2006 A1
20060068753 Karpen Mar 2006 A1
20060079249 Shim Apr 2006 A1
20060104306 Adamczyk May 2006 A1
20060106774 Cohen May 2006 A1
20060120517 Moon Jun 2006 A1
20060128395 Muhonen Jun 2006 A1
20060135177 Winterbottom Jun 2006 A1
20060188083 Breen Aug 2006 A1
20060193447 Schwartz Aug 2006 A1
20060206610 Ling Sep 2006 A1
20060212558 Sahinoja Sep 2006 A1
20060212562 Kushwaha Sep 2006 A1
20060225090 Shim et al. Oct 2006 A1
20060234639 Kushwaha Oct 2006 A1
20060234698 Fok Oct 2006 A1
20060239205 Warren Oct 2006 A1
20060258380 Liebowitz Nov 2006 A1
20060293024 Benco Dec 2006 A1
20060293066 Edge Dec 2006 A1
20070003024 Olivier Jan 2007 A1
20070019614 Hoffmann Jan 2007 A1
20070022011 Altberg Jan 2007 A1
20070026854 Nath Feb 2007 A1
20070026871 Wager Feb 2007 A1
20070027997 Polk Feb 2007 A1
20070030539 Nath Feb 2007 A1
20070036139 Patel Feb 2007 A1
20070037585 Shim Feb 2007 A1
20070041513 Gende Feb 2007 A1
20070049288 Lamprecht Mar 2007 A1
20070060097 Edge Mar 2007 A1
20070072624 Niemenmaa Mar 2007 A1
20070081635 Croak Apr 2007 A1
20070082681 Kim Apr 2007 A1
20070082682 Kim Apr 2007 A1
20070115941 Patel May 2007 A1
20070121601 Kikinis May 2007 A1
20070149213 Lamba Jun 2007 A1
20070160036 Smith Jul 2007 A1
20070162228 Mitchell Jul 2007 A1
20070167177 Kraufvelin Jul 2007 A1
20070182547 Wachter Aug 2007 A1
20070182631 Berlinsky Aug 2007 A1
20070201623 Hines Aug 2007 A1
20070206568 Silver Sep 2007 A1
20070206613 Silver Sep 2007 A1
20070242660 Xu Oct 2007 A1
20070243885 Shim Oct 2007 A1
20070263610 Mitchell Nov 2007 A1
20070263611 Mitchell Nov 2007 A1
20070270164 Maier Nov 2007 A1
20080032703 Krumm Feb 2008 A1
20080037715 Prozeniuk Feb 2008 A1
20080063153 Krivorot Mar 2008 A1
20080065775 Polk Mar 2008 A1
20080109650 Shim May 2008 A1
20080117859 Shahidi May 2008 A1
20080160953 Mia Jul 2008 A1
20080186164 Emigh Aug 2008 A1
20080192731 Dickinson Aug 2008 A1
20080208671 Ehrlich Aug 2008 A1
20080214202 Toomey Sep 2008 A1
20080268769 Brown Oct 2008 A1
20090029675 Steinmetz Jan 2009 A1
20090198733 Gounares Aug 2009 A1
20090204471 Elenbaas et al. Aug 2009 A1
20090204600 Kalik Aug 2009 A1
20090237210 Ciesla Sep 2009 A1
20100010860 Bose Jan 2010 A1
20100021013 Gale Jan 2010 A1
20100138400 Curtis et al. Jun 2010 A1
20100161662 Jonas et al. Jun 2010 A1
20100167691 Howarter Jul 2010 A1
20100198933 Smith Aug 2010 A1
20100233991 Crawford Sep 2010 A1
20100241507 Quinn et al. Sep 2010 A1
20100262668 Piett Oct 2010 A1
20110109468 Hirschfeld May 2011 A1
20110113060 Martini May 2011 A1
20110137549 Gupta Jun 2011 A1
20110151837 Winbush Jun 2011 A1
20110207429 Maier Aug 2011 A1
20120079600 Kellerman Mar 2012 A1
20120157136 Pitt et al. Jun 2012 A1
20130079152 Hall Mar 2013 A1
Foreign Referenced Citations (10)
Number Date Country
WO200607585 Jul 2006 KR
WO9921380 Apr 1999 SE
WO0040038 Dec 1999 WO
WO0145342 Jun 2001 WO
WO02057869 Jul 2002 WO
WO2004025941 Mar 2004 WO
WO2005051033 Jun 2005 WO
WO2007027166 Jun 2005 WO
WO2007025227 Mar 2007 WO
WO2009105603 Aug 2009 WO
Non-Patent Literature Citations (21)
Entry
International Search Report received in PCT/US2012/067857 dated Feb. 20, 2013.
International Search Report received in PCT/US2012/67689 dated Feb. 22, 2013.
International Search Report received in PCT/US2012/066313 dated Feb. 4, 2013.
International Search Report received in PCT/US2012/067932 dated Feb. 6, 2013.
International Search Report received in PCT/US2012/00266 dated Aug. 3, 3012.
International Search Report received in PCT/US2011/001990 dated Apr. 24, 2012.
Intrado Inc., Qwest Detailed SR/ALI to MPC/GMLC Interface Specification for TCP/IP Implementation of TIA/EIA/J-STD-036- E2 with Phase I Location Description Addition, Intrado Informed Response; Apr. 2004; Issue 1.11; pp. 1-57.
International Search Report in PCT/US2007/23243 dated Apr. 2, 2008.
PCT International Search Report (PCTUS2007/23714) and Written Opinion of International Searching Authority, Apr. 18, 2008.
Le-Pond Chin, Jyh-Hong Wen, Ting-Way Liu, The Study of the Interconnection of GSM Mobile Communication System Over IP based Network, May 6, 2001, IEEE, Vehicular Technology Conference, vol. 3, pp. 2219-2223.
Location Based Services V2 Roaming Support (non proprietary), 80-V8470-2NP A, dated Jan. 27, 2005, pp. 1-56.
Yilin Zhao, Efficient and reliable date transmission for cellular and GPS based mayday systems, Nov. 1997, IEEE, IEEE Conference on Intelligent Transportation System, 1997. ITSC 97, 555-559.
Qualcomm CDMA Technologies, LBS Control Plane/Use Plane Overview—80-VD378-1NP B, 2006, pp. 1-36.
Bhalla et al, TELUS, Technology Strategy—LBS Roaming Summit, Sep. 19, 2006.
Alfredo Aguirre, Ilusacell, First and Only Carrier in Mexico with a 3G CDMA Network, 2007.
Mike McMullen, Sprint, LBS Roaming Summit, Sep. 19, 2006.
Andrew Yeow, BCE, LBS Roaming Summit, Sep. 19, 2006, pp. 1-8.
Nars Haran, U.S. Cellular, Packet Data—Roaming and LBS Overview, Nov. 2, 2007, pp. 1-15.
Qualcomm CDMA Technologies, LBS Control Plane Roaming—80-VD377-1NP A, 2006, pp. 1-10.
Qualcomm CDMA Technologies, MS Resident User Plane LBS Roaming—80-VC718-1 E, 2006, pp. 1-37.
Intrado MSAG Prep for E911 Program and Documentation. Intrado Inc., Longmont, CO. Sep. 14, 2006. Accessed: Nov. 8, 2011. Idaho PSAP Standards Committee. Idaho Emergency Communications Commission,http://idahodispatch.com/index.php?option=com—documan&task=doc—download&gid=3&Itemid=7.
Related Publications (1)
Number Date Country
20120157125 A1 Jun 2012 US
Provisional Applications (3)
Number Date Country
61457145 Jan 2011 US
61457061 Dec 2010 US
61457744 May 2011 US
Continuation in Parts (1)
Number Date Country
Parent 13064796 Apr 2011 US
Child 13338978 US