US20090077077A1 - Optimal selection of MSAG address for valid civic/postal address - Google Patents
Optimal selection of MSAG address for valid civic/postal addressDownload PDFInfo
- Publication number
- US20090077077A1 US20090077077A1US12/232,507US23250708AUS2009077077A1US 20090077077 A1US20090077077 A1US 20090077077A1US 23250708 AUS23250708 AUS 23250708AUS 2009077077 A1US2009077077 A1US 2009077077A1
- Authority
- US
- United States
- Prior art keywords
- msag
- address
- match
- candidates
- valid
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034methodMethods0.000claimsabstractdescription36
- 230000001413cellular effectEffects0.000description4
- 239000004165Methyl ester of fatty acidsSubstances0.000description3
- 238000005516engineering processMethods0.000description3
- 238000013507mappingMethods0.000description3
- 235000015854Heliotropium curassavicumNutrition0.000description2
- 244000301682Heliotropium curassavicumSpecies0.000description2
- 108010007100Pulmonary Surfactant-Associated Protein AProteins0.000description2
- 102100027773Pulmonary surfactant-associated protein A2Human genes0.000description2
- 239000000969carrierSubstances0.000description2
- 238000010606normalizationMethods0.000description2
- 230000003068static effectEffects0.000description2
- 238000005259measurementMethods0.000description1
- 238000012986modificationMethods0.000description1
- 230000004048modificationEffects0.000description1
Images
Classifications
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5116—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing for emergency applications
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/04—Special services or facilities for emergency applications
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/30—Determination of the location of a subscriber
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/50—Connection management for emergency connections
Definitions
- This inventionrelates generally to long distance carriers, Internet Service Providers (ISPs), and information content delivery services/providers and long distance carriers. More particularly, it relates to emergency call systems (e.g., E9-1-1) including wireless and Internet Protocol (IP) based Voice Over Internet Protocol (VoIP) emergency call systems.
- emergency call systemse.g., E9-1-1
- IPInternet Protocol
- VoIPVoice Over Internet Protocol
- 9-1-1is a phone number widely recognized in North America as an emergency phone number that is used to contact emergency dispatch personnel.
- Enhanced 9-1-1(E9-1-1) is defined by an emergency call being selectively routed to an appropriate PSAP and enhanced information (callback number, name and location) is provided to the PSAP. This is accomplished through the use of the ANI.
- the ANImay be the real phone number of the caller (in landline E911) or a pseudo-ANI called an ESRK (in cellular E911) or ESQK (in VoIP E911).
- ESRKin cellular E911
- ESQKin VoIP E911
- This identifierallows the PSAP to retrieve location information such as the Master Street Address Guide (MSAG) valid address of the E9-1-1 caller's Civic/Postal Address.
- the Master Street Address Guide (MSAG)represents a community provided local address master guide that permits the most accurate dispatch of emergency personnel to a “correct address.”
- the “correct address”originates as the civic/postal address of an E9-1-1 emergency caller over a wireless and/or Internet Protocol (IP) based Voice Over Internet Protocol (VoIP) emergency call system.
- IPInternet Protocol
- VoIPVoice Over Internet Protocol
- the civic/postal addressrepresents the caller's location at the time when the emergency call is placed. This civic/postal address needs to be associated with an appropriate corresponding MSAG address, which is in most cases is required by the public safety answering point (PSAP).
- PSAPpublic safety answering point
- PSAPPublic Service Answering Point
- PSAPmay be a local, fire or police department, an ambulance service or a regional office covering all services.
- PSAPrefers to either a public safety access point (PSAP), or to an Emergency Call Center (ECC), a VoIP term.
- PSAPpublic safety access point
- ECCEmergency Call Center
- ALIlandline automatic location identification
- MSAGmaster street address guide
- ESNemergency service number
- GISgeographic information system
- VoIP systemsuse proprietary technologies, usually based on GIS polygons, or based on pre-provisioning of the caller in the traditional landline ALI long before the need for an emergency call.
- the MSAG-valid addressis required by most PSAPs, as it represents a community provided local address that allows accurate dispatch of emergency personnel to the correct address. But a challenge remains to provide this MSAG-valid address for a real-time Voice Over Internet Protocol (VoIP) emergency call, given that the source address is usually civic/postal.
- VoIPVoice Over Internet Protocol
- a method of determining an optimal MSAG-valid match in real timecomprises performing a master street address guide (MSAG) simple match to find a set of MSAG address candidates, performing an MSAG historical data match to find a set of MSAG address candidates, and performing a pinned MSAG data match using a commercial location engine to find a set of MSAG address candidates.
- MSAGmaster street address guide
- the first non-empty set of candidatesis used, and the MSAG addresses in this set are checked for conflicts.
- An MSAG-valid addressis returned when no conflicts are found.
- apparatus for returning an optimal MSAG-vaild match in real timecomprises a master street address guide (MSAG) simple match module to determine a set of MSAG address candidates.
- An MSAG historical data match moduledetermines a set of MSAG address candidates.
- a pinned MSAG data match moduleuses a commercial location engine to determine a set of MSAG address candidates.
- a comparison modulecompares the MSAG addresses in the first non-empty set of candidates, and returns an MSAG-valid address when no conflicts are found.
- FIG. 1depicts operation of three different MSAG matching steps which together, if consistent, allow determination of an optimal MSAG-valid address, in accordance with the principles of the present invention.
- FIG. 2shows an exemplary MSAG data store including a database used for a simple MSAG match, a database used for a historical data match, and a database used for a pinned match, in accordance with the principles of the present invention.
- FIG. 3shows the process within the simple MSAG match module in an exemplary MSAG address selection technique shown in FIG. 1 , in more detail.
- FIG. 4shows the historical data MSAG match in an exemplary MSAG address selection module shown in FIG. 1 in more detail.
- FIG. 5shows the pinned commercial engine MSAG match in an exemplary MSAG address selection module shown in FIG. 1 , in more detail.
- the present inventionfinds the optimal Master Street Address Guide (MSAG) address for a given civic/postal address (such as the one assigned to an E9-1-1 caller).
- MSAGMaster Street Address Guide
- the present inventionprovides a technique and apparatus to find an optimal MSAG-valid address in real time following a well-defined path that determines the accurate, i.e. optimal, MSAG address for the E9-1-1 caller.
- an MSAG-valid addressis selected for a given civic/postal address in such a way as to ensure that the resulting MSAG address is the most optimal address.
- arrival at an optimal MSAG address selectionmoves through as many as three well defined MSAG matching steps.
- the three MSAG matching stepsare preferably performed in tandem or in parallel to allow quick, real-time MSAG address determination, though sequential functionality is within the scope of the present invention.
- a simple match of an MSAG addressis performed, a historical data match for an MSAG address is attempted, and a pinned MSAG match is performed using a commercial location engine.
- FIG. 1depicts operation of three different MSAG matching steps which together allow determination of an optimal MSAG-valid address, in accordance with the principles of the present invention.
- a civic/postal addressis Simple Matched against the relevant data store ( 200 shown in FIG. 2 ) containing MSAG Address data.
- the Simple Match database 200uses normalized fields for the highest possible success rate. In this way, in many cases the Simple Match 300 finds MSAG address candidate(s).
- Step 302determines if the Simple Match module 300 found one or more MSAG address candidates. If so, then the process provides the MSAG address candidates to a conflict check module 106 (shown in FIGS. 1 and 5 ) to determine if the MSAG address candidates conflict with one another. If there is a conflict between the two or more MSAG address candidates, then the process proceeds to step 108 and returns no MSAG address. If there are no conflicts between the MSAG address candidates from Simple Match 300 then that MSAG address is returned as the MSAG-valid address in step 190 .
- step 302determines that no MSAG address candidates were found, a second real time step of an historical data MSAG match 304 is also performed to find MSAG address candidates.
- the civic/postal addressis compared to historical matched data in the MSAG historical address table forming the historical match database 202 .
- Step 306determines if the Historical Data Match module 304 found one or more MSAG address candidates. If so, then the process provides the MSAG address candidates to a conflict check module 106 (shown in FIGS. 1 and 5 ) to determine if the MSAG address candidates conflict with one another. If there is a conflict between the two or more MSAG address candidates, then the process proceeds to step 108 and returns no MSAG address. If there are no conflicts between the MSAG address candidates from Historical Data Match 304 then that MSAG address is returned as the MSAG-valid address in step 190 .
- step 308determines if step 302 determines that no MSAG address candidates were found.
- Step 310determines if the Pinned MSAG Match module 308 found any MSAG address candidates. If none were found, then the process proceeds to step 108 and returns no MSAG address. If however one or more MSAG address candidates were found in the Pinned MSAG Match module 308 , then the process provides the MSAG Address Candidates to a conflict check module 106 to determine if the MSAG address candidates conflict with one another. If there is a conflict between the two or more MSAG address candidates, then the process proceeds to step 108 and returns no MSAG address. If there are no conflicts between the MSAG address candidates from Pinned MSAG Match 304 , then that MSAG is returned as the MSAG-valid address in step 190 .
- FIG. 2shows an exemplary MSAG data store including a database 200 used for a simple MSAG match, a database 202 used for a historical data match, and a database 204 used for a pinned match, in accordance with the principles of the present invention.
- an exemplary MSAG data storeincludes an MSAG address table 200 , an historical data table 202 , and a mapping data table 204 .
- Entries in the MSAG address table 200preferably include an MSAG Address_ID, and an MSAG Address.
- Entries in the historical data table 202include Historical Data_ID, the civic/postal address, and the MSAG address.
- Entries in the mapping data table 204include a Mapping_ID, and the MSAG Address_ID.
- FIG. 3shows the process within the Simple MSAG Match module 300 in an exemplary MSAG address selection technique shown in FIG. 1 , in more detail.
- the input civic/postal address 100is normalized for case, whitespace, & punctuation, then compared (i.e., Simple Matched) to similarly normalized MSAG addresses in the MSAG address table 200 .
- the normalization processallows representation of equivalent address data in consistent format allowing easier comparison and a higher success rate. See, e.g., co-pending and co-owned U.S. patent application Ser. No. 12/______, co-filed herewith and claiming priority from 60/960,148 and 60/960,459, entitled “Optimal Selection of MSAG Address For Valid Subaru/Postal Address” to Geldenbott et al., the entirety of which is expressly incorporated herein by reference.
- step 102the appropriate MSAG data store 200 ( FIG. 2 , Simple Match Database) is searched using the input civic/postal address against the MSAG addresses in the table.
- step 103a determination is made as to whether or not there has been a database error. If so, then the process proceeds to report a system error in step 150 , and no MSAG address is returned. If there were no system errors, then the process determines in step 104 if any MSAG address candidates have been found. If candidates have been found, the process provides them to module 106 that determines if the MSAG address candidates conflict with one another. Only if no conflicting MSAG address candidates are found is the optimal MSAG-valid address returned. If conflicting candidates are found, however, the method unsuccessfully comes to end and returns no MSAG address since at this point the MSAG data store 204 is considered ambiguous, at least for the given input civic/postal address.
- MSAG address candidateswere found by Simple Match 102 at step 104 , then proceed to the next MSAG matching module, e.g., to the historical data MSAG match module 304 shown in FIG. 4 .
- FIG. 4shows the historical data MSAG match in an exemplary MSAG address selection module 304 shown in FIG. 1 in more detail.
- the civic/postal addressis input, and the appropriate MSAG historical data table 202 ( FIG. 2 ) is queried using an historical match data technique, as depicted in step 110 .
- the historical MSAG data store 202may be either human or machine generated data that associates a select set of adjacent civic/postal address to their correct MSAG addresses. The same normalizations are applied to the civic/postal address as described earlier for Simple Match, and then the Historical Data Table 202 is searched using the input civic/postal address against the civic/postal addresses in the table 202 .
- step 113a determination is made as to whether or not there has been a database error. If so, then the process proceeds to return no MSAG address in step 152 . If no error occurred, then the process determines in step 112 if any MSAG address candidates have been found. If MSAG candidate addresses were found, the process provides them to module 106 that determines if the MSAG address candidates conflict with one another. Only if no conflicting MSAG address candidates are found is the optimal MSAG-valid address returned. If conflicting candidates are found, the method unsuccessfully comes to end and returns no MSAG address since at this point the Historical data store 202 is considered ambiguous, at least for the given input civic/postal address.
- MSAG address candidateswere found by Historical Match 110 at step 112 , then proceed to the next MSAG matching module, e.g., to the pinned data MSAG match module 308 shown in FIG. 5 .
- FIG. 5shows the Pinned MSAG Match using a commercial engine in an exemplary MSAG address selection module 308 shown in FIG. 1 , in more detail.
- the civic/postal addressis input, and submitted to a commercial location engine, as depicted in step 114 . If the commercial location engine submission fails to result in a mapped address, then the process proceeds to step 154 and returns no MSAG address. If, on the other hand, the commercial location engine submission does result in a mapped address, the process proceeds to a module 118 that queries the Mapping data table in the pinned match database 204 .
- Commercial location enginesuse a Mapping_ID for each street segment known to the engine.
- the pinned match data in 204is a collection of MSAG addresses associated with (pinned to) these Mapping_IDs.
- the query in module 118uses the Mapping_ID found for the input civic/postal from 114, to query the database 204 for the MSAG addresses associated with (pinned to) that same Mapping_ID.
- step 143a determination is made as to whether or not there has been a database error. If so, then the process proceeds to return no MSAG address in step 154 . If no errors occurred, then the process determines in step 120 if any MSAG address candidates have been found. If no MSAG address candidates were found, then the process proceeds to step 154 and returns no MSAG address. If MSAG address candidates were found, the process provides them to step 106 that determines if the MSAG address candidates conflict with one another. If conflicting candidates are found, the method unsuccessfully comes to end and returns no MSAG address since at this point the Pinned Match data store 204 is considered ambiguous, at least for the given input civic/postal address. If the MSAG address candidates don't conflict, the MSAG-valid address is returned at 170 .
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Emergency Management (AREA)
- Marketing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
- This application claims priority from U.S. Provisional Application No. 60/960,148, entitled “Optimal Selection of MSAG Address for Valid Civic/Postal Address”, to Geldenbott, filed Sep. 18, 2007; and also from U.S. Provisional Application No. 60/960,459, entitled “MSAG Simple Matching a Civic/Postal Address Using Unique Normalized House Number Fields”, to Geldenboft, Hines, Martin and Backus, filed Oct. 1, 2007, the entirety of both of which are expressly incorporated herein by reference.
- 1. Field of the Invention
- This invention relates generally to long distance carriers, Internet Service Providers (ISPs), and information content delivery services/providers and long distance carriers. More particularly, it relates to emergency call systems (e.g., E9-1-1) including wireless and Internet Protocol (IP) based Voice Over Internet Protocol (VoIP) emergency call systems.
- 2. Background of Related Art
- 9-1-1 is a phone number widely recognized in North America as an emergency phone number that is used to contact emergency dispatch personnel. Enhanced 9-1-1 (E9-1-1) is defined by an emergency call being selectively routed to an appropriate PSAP and enhanced information (callback number, name and location) is provided to the PSAP. This is accomplished through the use of the ANI. The ANI may be the real phone number of the caller (in landline E911) or a pseudo-ANI called an ESRK (in cellular E911) or ESQK (in VoIP E911). Regardless of the network type, a 9-1-1 service becomes E-9-1-1 when automatic number identification and automatic location information related to the call is provided to the 9-1-1 operator at the PSAP.
- This identifier allows the PSAP to retrieve location information such as the Master Street Address Guide (MSAG) valid address of the E9-1-1 caller's Civic/Postal Address. The Master Street Address Guide (MSAG) represents a community provided local address master guide that permits the most accurate dispatch of emergency personnel to a “correct address.” The “correct address” originates as the civic/postal address of an E9-1-1 emergency caller over a wireless and/or Internet Protocol (IP) based Voice Over Internet Protocol (VoIP) emergency call system. The civic/postal address represents the caller's location at the time when the emergency call is placed. This civic/postal address needs to be associated with an appropriate corresponding MSAG address, which is in most cases is required by the public safety answering point (PSAP).
- A Public Service Answering Point (PSAP) is a dispatch office that receives 9-1-1 calls from the public. A PSAP may be a local, fire or police department, an ambulance service or a regional office covering all services. As used herein, the term “PSAP” refers to either a public safety access point (PSAP), or to an Emergency Call Center (ECC), a VoIP term.
- Distributed emergency call systems in telecommunications are in general very complex computing systems. Emergency calls that originate from a VoIP network use well proven routing paradigms already used for cellular 911 calls, or for traditional landline 911 calls. These paradigms usually work well, because VoIP customers can usually be grouped into two categories: a mobile VoIP caller that resembles a cellular user, and a stationary VoIP user resembling landline usage.
- Traditional landline systems use pre-provisioned, generally static subscriber addresses, where the landline automatic location identification (ALI) provisioning process insures a match to a master street address guide (MSAG) record, which contains an emergency service number (ESN) used to route emergency calls to a PSAP.
- But determination of the location of a mobile device proves much, much more challenging. To determine location of a mobile device, some conventional cellular systems use separate triangulation technologies (or any of a number of other techniques) to find a latitude & longitude of an emergency caller. These systems then use a geographic information system (GIS) system to query for a pre-defined region (e.g., a PSAP polygon) that contains this location.
- Of course, errors may occur in conventional systems when determining the location of a mobile user. But even though it's very possible that these queried PSAP polygons can lead to a different (i.e., wrong) neighboring PSAP than an equivalent address provisioned in a landline ALI, this discrepancy is conventionally accepted by PSAPs because the location itself is likely to be imprecise due to measurement errors—sometimes the location is off by hundreds of feet.
- Conventional VoIP systems use proprietary technologies, usually based on GIS polygons, or based on pre-provisioning of the caller in the traditional landline ALI long before the need for an emergency call.
- Thus, traditional landline paradigms provide the most accurate location for its static users, but require the caller's address to be pre-provisioned into a landline automatic location identifier (ALI). This pre-provisioning (often referred to as service order interface (SOI) loading) usually takes a few days between the caller notifying their service provider of their address change, and this change being reflected in the landline ALI. But during this window a 911 call might be made, and if so it would be routed using the “old” data still in the landline ALI. Even the fastest possible conventional landline ALI provisioning takes at least several hours.
- Existing solutions include the NENA VoIP architecture for enhanced 9-1-1 services standard NENA 08-001. However, such conventional technologies are too complicated and not always practical. Moreover, conventional systems are disadvantageous because they are unable to handle the embedded geographic location to precisely route the caller to the correct PSAP using the “just-in-time” paradigm.
- The MSAG-valid address is required by most PSAPs, as it represents a community provided local address that allows accurate dispatch of emergency personnel to the correct address. But a challenge remains to provide this MSAG-valid address for a real-time Voice Over Internet Protocol (VoIP) emergency call, given that the source address is usually civic/postal.
- In accordance with the principles of the present invention, a method of determining an optimal MSAG-valid match in real time, comprises performing a master street address guide (MSAG) simple match to find a set of MSAG address candidates, performing an MSAG historical data match to find a set of MSAG address candidates, and performing a pinned MSAG data match using a commercial location engine to find a set of MSAG address candidates. The first non-empty set of candidates is used, and the MSAG addresses in this set are checked for conflicts. An MSAG-valid address is returned when no conflicts are found.
- In accordance with other aspects of the invention, apparatus for returning an optimal MSAG-vaild match in real time comprises a master street address guide (MSAG) simple match module to determine a set of MSAG address candidates. An MSAG historical data match module determines a set of MSAG address candidates. A pinned MSAG data match module uses a commercial location engine to determine a set of MSAG address candidates. A comparison module compares the MSAG addresses in the first non-empty set of candidates, and returns an MSAG-valid address when no conflicts are found.
- 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 operation of three different MSAG matching steps which together, if consistent, allow determination of an optimal MSAG-valid address, in accordance with the principles of the present invention.FIG. 2 shows an exemplary MSAG data store including a database used for a simple MSAG match, a database used for a historical data match, and a database used for a pinned match, in accordance with the principles of the present invention.FIG. 3 shows the process within the simple MSAG match module in an exemplary MSAG address selection technique shown inFIG. 1 , in more detail.FIG. 4 shows the historical data MSAG match in an exemplary MSAG address selection module shown inFIG. 1 in more detail.FIG. 5 shows the pinned commercial engine MSAG match in an exemplary MSAG address selection module shown inFIG. 1 , in more detail.- The present invention finds the optimal Master Street Address Guide (MSAG) address for a given civic/postal address (such as the one assigned to an E9-1-1 caller).
- The present invention provides a technique and apparatus to find an optimal MSAG-valid address in real time following a well-defined path that determines the accurate, i.e. optimal, MSAG address for the E9-1-1 caller. Using the inventive multi-step technique, an MSAG-valid address is selected for a given civic/postal address in such a way as to ensure that the resulting MSAG address is the most optimal address.
- In accordance with the principles of the present invention, arrival at an optimal MSAG address selection moves through as many as three well defined MSAG matching steps. In the disclosed embodiments, the three MSAG matching steps are preferably performed in tandem or in parallel to allow quick, real-time MSAG address determination, though sequential functionality is within the scope of the present invention.
- In the preferred embodiments, a simple match of an MSAG address is performed, a historical data match for an MSAG address is attempted, and a pinned MSAG match is performed using a commercial location engine.
FIG. 1 depicts operation of three different MSAG matching steps which together allow determination of an optimal MSAG-valid address, in accordance with the principles of the present invention.- In particular, in a
first step 300 shown inFIG. 1 , a civic/postal address is Simple Matched against the relevant data store (200 shown inFIG. 2 ) containing MSAG Address data. Preferably the SimpleMatch database 200 uses normalized fields for the highest possible success rate. In this way, in many cases theSimple Match 300 finds MSAG address candidate(s). - Step302 determines if the
Simple Match module 300 found one or more MSAG address candidates. If so, then the process provides the MSAG address candidates to a conflict check module106 (shown inFIGS. 1 and 5 ) to determine if the MSAG address candidates conflict with one another. If there is a conflict between the two or more MSAG address candidates, then the process proceeds to step108 and returns no MSAG address. If there are no conflicts between the MSAG address candidates fromSimple Match 300 then that MSAG address is returned as the MSAG-valid address instep 190. - In accordance with the principles of the present invention, if
step 302 determines that no MSAG address candidates were found, a second real time step of an historicaldata MSAG match 304 is also performed to find MSAG address candidates. In the historical dataMSAG match module 304, the civic/postal address is compared to historical matched data in the MSAG historical address table forming thehistorical match database 202. - Step306 determines if the Historical
Data Match module 304 found one or more MSAG address candidates. If so, then the process provides the MSAG address candidates to a conflict check module106 (shown inFIGS. 1 and 5 ) to determine if the MSAG address candidates conflict with one another. If there is a conflict between the two or more MSAG address candidates, then the process proceeds to step108 and returns no MSAG address. If there are no conflicts between the MSAG address candidates fromHistorical Data Match 304 then that MSAG address is returned as the MSAG-valid address instep 190. - In accordance with the principles of the present invention, if
step 302 determines that no MSAG address candidates were found, a final real time Pinned MSAG Match using a commercial location engine is performed instep 308. Step310 determines if the PinnedMSAG Match module 308 found any MSAG address candidates. If none were found, then the process proceeds to step108 and returns no MSAG address. If however one or more MSAG address candidates were found in the PinnedMSAG Match module 308, then the process provides the MSAG Address Candidates to aconflict check module 106 to determine if the MSAG address candidates conflict with one another. If there is a conflict between the two or more MSAG address candidates, then the process proceeds to step108 and returns no MSAG address. If there are no conflicts between the MSAG address candidates from PinnedMSAG Match 304, then that MSAG is returned as the MSAG-valid address instep 190. FIG. 2 shows an exemplary MSAG data store including adatabase 200 used for a simple MSAG match, adatabase 202 used for a historical data match, and adatabase 204 used for a pinned match, in accordance with the principles of the present invention.- In particular, as shown in
FIG. 2 , an exemplary MSAG data store includes an MSAG address table200, an historical data table202, and a mapping data table204. - Entries in the MSAG address table200 preferably include an MSAG Address_ID, and an MSAG Address.
- Entries in the historical data table202 include Historical Data_ID, the civic/postal address, and the MSAG address.
- Entries in the mapping data table204 include a Mapping_ID, and the MSAG Address_ID.
FIG. 3 shows the process within the SimpleMSAG Match module 300 in an exemplary MSAG address selection technique shown inFIG. 1 , in more detail.- In particular, as shown in
FIG. 3 , the input civic/postal address 100 is normalized for case, whitespace, & punctuation, then compared (i.e., Simple Matched) to similarly normalized MSAG addresses in the MSAG address table200. The normalization process allows representation of equivalent address data in consistent format allowing easier comparison and a higher success rate. See, e.g., co-pending and co-owned U.S. patent application Ser. No. 12/______, co-filed herewith and claiming priority from 60/960,148 and 60/960,459, entitled “Optimal Selection of MSAG Address For Valid Civic/Postal Address” to Geldenbott et al., the entirety of which is expressly incorporated herein by reference. - In
step 102, the appropriate MSAG data store200 (FIG. 2 , Simple Match Database) is searched using the input civic/postal address against the MSAG addresses in the table. - In
step 103, a determination is made as to whether or not there has been a database error. If so, then the process proceeds to report a system error instep 150, and no MSAG address is returned. If there were no system errors, then the process determines instep 104 if any MSAG address candidates have been found. If candidates have been found, the process provides them tomodule 106 that determines if the MSAG address candidates conflict with one another. Only if no conflicting MSAG address candidates are found is the optimal MSAG-valid address returned. If conflicting candidates are found, however, the method unsuccessfully comes to end and returns no MSAG address since at this point theMSAG data store 204 is considered ambiguous, at least for the given input civic/postal address. - If there were no errors, but no MSAG address candidates were found by
Simple Match 102 atstep 104, then proceed to the next MSAG matching module, e.g., to the historical dataMSAG match module 304 shown inFIG. 4 . FIG. 4 shows the historical data MSAG match in an exemplary MSAGaddress selection module 304 shown inFIG. 1 in more detail.- In particular, as shown in
FIG. 4 , the civic/postal address is input, and the appropriate MSAG historical data table202 (FIG. 2 ) is queried using an historical match data technique, as depicted instep 110. The historicalMSAG data store 202 may be either human or machine generated data that associates a select set of adjacent civic/postal address to their correct MSAG addresses. The same normalizations are applied to the civic/postal address as described earlier for Simple Match, and then the Historical Data Table202 is searched using the input civic/postal address against the civic/postal addresses in the table202. - In
step 113, a determination is made as to whether or not there has been a database error. If so, then the process proceeds to return no MSAG address instep 152. If no error occurred, then the process determines instep 112 if any MSAG address candidates have been found. If MSAG candidate addresses were found, the process provides them tomodule 106 that determines if the MSAG address candidates conflict with one another. Only if no conflicting MSAG address candidates are found is the optimal MSAG-valid address returned. If conflicting candidates are found, the method unsuccessfully comes to end and returns no MSAG address since at this point theHistorical data store 202 is considered ambiguous, at least for the given input civic/postal address. - If there were no errors, but no MSAG address candidates were found by
Historical Match 110 atstep 112, then proceed to the next MSAG matching module, e.g., to the pinned dataMSAG match module 308 shown inFIG. 5 . FIG. 5 shows the Pinned MSAG Match using a commercial engine in an exemplary MSAGaddress selection module 308 shown inFIG. 1 , in more detail.- In particular, as shown in
FIG. 5 , the civic/postal address is input, and submitted to a commercial location engine, as depicted instep 114. If the commercial location engine submission fails to result in a mapped address, then the process proceeds to step154 and returns no MSAG address. If, on the other hand, the commercial location engine submission does result in a mapped address, the process proceeds to amodule 118 that queries the Mapping data table in the pinnedmatch database 204. Commercial location engines use a Mapping_ID for each street segment known to the engine. The pinned match data in204 is a collection of MSAG addresses associated with (pinned to) these Mapping_IDs. The query inmodule 118 uses the Mapping_ID found for the input civic/postal from 114, to query thedatabase 204 for the MSAG addresses associated with (pinned to) that same Mapping_ID. - In
step 143, a determination is made as to whether or not there has been a database error. If so, then the process proceeds to return no MSAG address instep 154. If no errors occurred, then the process determines instep 120 if any MSAG address candidates have been found. If no MSAG address candidates were found, then the process proceeds to step154 and returns no MSAG address. If MSAG address candidates were found, the process provides them to step106 that determines if the MSAG address candidates conflict with one another. If conflicting candidates are found, the method unsuccessfully comes to end and returns no MSAG address since at this point the PinnedMatch data store 204 is considered ambiguous, at least for the given input civic/postal address. If the MSAG address candidates don't conflict, the MSAG-valid address is returned at170. - 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 (3)
1. A method of determining an optimal MSAG-valid match in real time, comprising:
performing a master street address guide (MSAG) simple match to find a set of MSAG simple match address candidates;
performing an MSAG historical data match to find a set of MSAG historical data address candidates;
performing a pinned MSAG data match using a commercial location engine to find a set of MSAG pinned address candidates; and
comparing MSAG addresses in a first non-empty set of said MSAG address candidates to verify they do not conflict, and return an MSAG-valid address.
2. Apparatus for determining an optimal MSAG-valid match in real time, comprising:
a master street address guide (MSAG) simple match module to determine an MSAG simple match set of MSAG simple match address candidates;
an MSAG historical data match module to determine an MSAG historical data match set of MSAG historical data address candidates;
a pinned MSAG data match module using a commercial location engine to determine a pinned MSAG match set of MSAG pinned address candidates; and
a comparison module to compare MSAG addresses in a first non-empty set of said MSAG address candidates to verify they do not conflict, and return an MSAG-valid address.
3. Apparatus for determining an optimal MSAG-valid match in real time, comprising:
means for performing a master street address guide (MSAG) simple match to find a set of MSAG simple match address candidates;
means for performing an MSAG historical data match to find a set of MSAG historical data address candidates;
means for performing a pinned MSAG data match using a commercial location engine to find a set of MSAG pinned address candidates; and
means for comparing MSAG addresses in a first non-empty set of said MSAG address candidates to verify they do not conflict, and return an MSAG-valid address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US12/232,507US20090077077A1 (en) | 2007-09-18 | 2008-09-18 | Optimal selection of MSAG address for valid civic/postal address |
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US96014807P | 2007-09-18 | 2007-09-18 | |
| US96045907P | 2007-10-01 | 2007-10-01 | |
| US12/232,507US20090077077A1 (en) | 2007-09-18 | 2008-09-18 | Optimal selection of MSAG address for valid civic/postal address |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| US20090077077A1true US20090077077A1 (en) | 2009-03-19 |
Family
ID=40455678
Family Applications (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US12/232,484Active2030-05-29US9413889B2 (en) | 2007-09-18 | 2008-09-18 | House number normalization for master street address guide (MSAG) address matching |
| US12/232,507AbandonedUS20090077077A1 (en) | 2007-09-18 | 2008-09-18 | Optimal selection of MSAG address for valid civic/postal address |
| US15/217,095AbandonedUS20160330321A1 (en) | 2007-09-18 | 2016-07-22 | House number normalization for master street address guide (msag) address matching |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US12/232,484Active2030-05-29US9413889B2 (en) | 2007-09-18 | 2008-09-18 | House number normalization for master street address guide (MSAG) address matching |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US15/217,095AbandonedUS20160330321A1 (en) | 2007-09-18 | 2016-07-22 | House number normalization for master street address guide (msag) address matching |
Country Status (1)
| Country | Link |
|---|---|
| US (3) | US9413889B2 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090298492A1 (en)* | 2008-06-02 | 2009-12-03 | West Corporation | System, apparatus and method for availing a mobile call of address information |
| US20110087839A1 (en)* | 2009-10-09 | 2011-04-14 | Verizon Patent And Licensing Inc. | Apparatuses, methods and systems for a smart address parser |
| US20130143516A1 (en)* | 2011-12-02 | 2013-06-06 | Andrew Llc | Enabling location determination of user device originating emergency service call |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090094270A1 (en)* | 2007-10-08 | 2009-04-09 | Alirez Baldomero J | Method of building a validation database |
| US8606798B2 (en)* | 2011-03-17 | 2013-12-10 | Mastercard International Incorporated | Systems and methods for creating standardized street addresses from raw address data |
| US20130262153A1 (en)* | 2012-03-28 | 2013-10-03 | The Travelers Indemnity Company | Systems and methods for certified location data collection, management, and utilization |
| US10684753B2 (en) | 2012-03-28 | 2020-06-16 | The Travelers Indemnity Company | Systems and methods for geospatial value subject analysis and management |
| US11188853B2 (en) | 2019-09-30 | 2021-11-30 | The Travelers Indemnity Company | Systems and methods for artificial intelligence (AI) damage triage and dynamic resource allocation, routing, and scheduling |
Citations (98)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4445118A (en)* | 1981-05-22 | 1984-04-24 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Navigation system and method |
| US4494119A (en)* | 1983-08-04 | 1985-01-15 | 122923 Canada Limited | Distress radiolocation method and system |
| US4651156A (en)* | 1982-02-08 | 1987-03-17 | Mcgraw-Edison Co. | Integrated radio location and communication system |
| US4891650A (en)* | 1988-05-16 | 1990-01-02 | Trackmobile Inc. | Vehicle location system |
| US4891638A (en)* | 1987-10-30 | 1990-01-02 | Motorola, Inc. | Nationwide display pager with location readout |
| US5014206A (en)* | 1988-08-22 | 1991-05-07 | Facilitech International Incorporated | Tracking system |
| US6032051A (en)* | 1997-12-01 | 2000-02-29 | Telefonaktiebolaget L/M Ericsson | Wireless mobile comunication devices for group use |
| US6067045A (en)* | 1998-09-01 | 2000-05-23 | Hughes Electronics Corporation | Communication network initialization apparatus and method for fast GPS-based positioning |
| US6181939B1 (en)* | 1998-02-18 | 2001-01-30 | Nokia Networks Oy | Method of processing mobile station data |
| US6253074B1 (en)* | 1996-01-10 | 2001-06-26 | Telefonaktiebolaget L/M Ericsson (Publ) | Cellular telecommunications systems having selectively associatable usage parameters |
| US6360102B1 (en)* | 1998-09-10 | 2002-03-19 | Ericsson Inc. | System and method for defining a subscriber location privacy profile |
| US20020077897A1 (en)* | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a web advertiser |
| US20020077118A1 (en)* | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a wireless service provider |
| US20020077083A1 (en)* | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a wireless service provider |
| US20020077084A1 (en)* | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a web advertiser |
| US20030009277A1 (en)* | 2001-07-03 | 2003-01-09 | Fan Rodric C. | Using location data to determine traffic information |
| US20030012148A1 (en)* | 2001-07-10 | 2003-01-16 | Michael Peters | Software based single agent multipoint conference capability |
| US20030026245A1 (en)* | 2001-07-31 | 2003-02-06 | Ejzak Richard Paul | Communication system including an interworking mobile switching center for call termination |
| US6526026B1 (en)* | 1997-12-10 | 2003-02-25 | Intel Corporation | Digit transmission over wireless communication link |
| US6529500B1 (en)* | 1999-08-26 | 2003-03-04 | Verizon Laboratories Inc. | Unified messaging notification |
| US6564261B1 (en)* | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
| US20030108176A1 (en)* | 1999-12-30 | 2003-06-12 | Fen-Chung Kung | Personal ip follow-me service |
| US20030109245A1 (en)* | 2001-11-05 | 2003-06-12 | Mccalmont Patti L | Routing of emergency calls based on geographic location of originating telephone end office |
| US6580390B1 (en)* | 2002-05-30 | 2003-06-17 | General Motors Corporation | Method and system for global positioning system mask angle optimization |
| US20030119521A1 (en)* | 2001-12-21 | 2003-06-26 | Shilpa Tipnis | Wireless network tour guide |
| US20030119528A1 (en)* | 2001-12-26 | 2003-06-26 | Boathouse Communication Partners, Llc | System and method for an automated intermediary to broker remote transaction between parties based on actively managed private profile information |
| US6687504B1 (en)* | 2000-07-28 | 2004-02-03 | Telefonaktiebolaget L. M. Ericsson | Method and apparatus for releasing location information of a mobile communications device |
| US20040043775A1 (en)* | 2002-08-29 | 2004-03-04 | Kennedy Joseph P. | Tasking and reporting method and implementation for wireless appliance location systems |
| US20040047461A1 (en)* | 2002-09-10 | 2004-03-11 | Weisman Jordan Kent | Method and apparatus for improved conference call management |
| US6731940B1 (en)* | 2000-04-28 | 2004-05-04 | Trafficmaster Usa, Inc. | Methods of using wireless geolocation to customize content and delivery of information to wireless communication devices |
| US6744858B1 (en)* | 2001-01-26 | 2004-06-01 | Telcontrol, Inc. | System and method for supporting multiple call centers |
| US6847618B2 (en)* | 2001-06-29 | 2005-01-25 | Ip Unity | Method and system for distributed conference bridge processing |
| US20050020242A1 (en)* | 1999-07-29 | 2005-01-27 | Bryan Holland | Locator system |
| US20050043037A1 (en)* | 2001-07-16 | 2005-02-24 | Ioppe Igor V. | System for providing alert-based services to mobile stations in a wireless communications network |
| US20050053209A1 (en)* | 2003-09-06 | 2005-03-10 | D'evelyn Linda Kaye | Method and system for availing participants in a special number call event and others of information contained in a plurality of data stores |
| US20050063519A1 (en)* | 2003-09-22 | 2005-03-24 | Foundry Networks, Inc. | System, method and apparatus for supporting E911 emergency services in a data communications network |
| US6876734B1 (en)* | 2000-02-29 | 2005-04-05 | Emeeting.Net, Inc. | Internet-enabled conferencing system and method accommodating PSTN and IP traffic |
| US20050083891A1 (en)* | 2003-10-21 | 2005-04-21 | Chia-En Chuang | Method and apparatus for updating frame number |
| US20050083911A1 (en)* | 2003-10-21 | 2005-04-21 | 3Com Corporation, A Corporation Of The State Of Delaware | IP-based enhanced emergency services using intelligent client devices |
| US20050107673A1 (en)* | 2003-11-13 | 2005-05-19 | General Motors Corporation | System and method for maintaining and providing personal information in real time |
| US6898633B1 (en)* | 2000-10-04 | 2005-05-24 | Microsoft Corporation | Selecting a server to service client requests |
| US20050119012A1 (en)* | 2003-12-02 | 2005-06-02 | Alcatel | Method of transmitting area specific content |
| US20050136885A1 (en)* | 2003-12-22 | 2005-06-23 | Kaltsukis Calvin L. | Emergency conference calling system |
| US20050135569A1 (en)* | 2003-12-19 | 2005-06-23 | Richard Dickinson | Enhanced E911 location information using voice over internet protocol (VoIP) |
| US6985747B2 (en)* | 2003-02-05 | 2006-01-10 | Autodesk, Inc. | Use of triggers and a location hypercube to enable push-based location applications |
| US20060008065A1 (en)* | 2004-07-08 | 2006-01-12 | Timothy Longman | Method for setting up a conference call |
| US20060026288A1 (en)* | 2004-07-30 | 2006-02-02 | Arup Acharya | Method and apparatus for integrating wearable devices within a SIP infrastructure |
| US20060068753A1 (en)* | 2004-09-22 | 2006-03-30 | Jim Karpen | Emergency call handling system |
| US20060073930A1 (en)* | 2004-09-08 | 2006-04-06 | Daimlerchrysler Ag | Transverse differential of a motor vehicle and method for production thereof |
| US20060104306A1 (en)* | 2004-11-15 | 2006-05-18 | Maria Adamczyk | Application services infrastructure for next generation networks |
| US20060120517A1 (en)* | 2004-03-05 | 2006-06-08 | Avaya Technology Corp. | Advanced port-based E911 strategy for IP telephony |
| US20060128395A1 (en)* | 2002-08-02 | 2006-06-15 | Janne Muhonen | Location services for mobile communication system |
| US20060135177A1 (en)* | 2004-10-29 | 2006-06-22 | James Winterbottom | Relating to internet protocol (IP) location, privacy and presence |
| US20070003024A1 (en)* | 2005-06-22 | 2007-01-04 | Cml Emergency Services Inc. | Network emergency call taking system and method |
| US20070019614A1 (en)* | 2003-09-09 | 2007-01-25 | Klaus Hoffmann | Method for providing a user interaction dialogue (uid) prior to connection acceptance by the called user |
| US20070022011A1 (en)* | 2003-10-06 | 2007-01-25 | Utbk, Inc. | Methods and apparatuses to determine prices of communication leads |
| US20070027997A1 (en)* | 2005-07-29 | 2007-02-01 | Cisco Technology, Inc. | Technique for translating location information |
| US20070026871A1 (en)* | 2005-07-28 | 2007-02-01 | Openwave Systems Inc. | Wireless network with adaptive autonomous location push |
| US7174153B2 (en)* | 2003-12-23 | 2007-02-06 | Gregory A Ehlers | System and method for providing information to an operator of an emergency response vehicle |
| US7177399B2 (en)* | 2004-02-27 | 2007-02-13 | Nortel Network Limited | Determining the geographical location from which an emergency call originates in a packet-based communications network |
| US7177398B2 (en)* | 2004-03-13 | 2007-02-13 | Intrado Inc. | Bi-directional messaging for an emergency services network |
| US7177397B2 (en)* | 2001-11-05 | 2007-02-13 | Intrado Inc. | Geographic routing of emergency service call center emergency calls |
| US20070036139A1 (en)* | 2005-08-09 | 2007-02-15 | Ashish Patel | System and method for authenticating internetwork resource requests |
| US20070041513A1 (en)* | 2005-02-08 | 2007-02-22 | Gende Michael F | Emergency call identification, location and routing method and system |
| US20070041516A1 (en)* | 2005-05-26 | 2007-02-22 | Richard Dickinson | E911 call blocking for non-initialized wireless telephones |
| US20070042765A1 (en)* | 2005-08-19 | 2007-02-22 | Global Locate, Inc. | Method and apparatus for providing intelligent deactivation of electronic devices in aircraft |
| US20070049288A1 (en)* | 2005-08-24 | 2007-03-01 | Lamprecht Leslie J | Creating optimum temporal location trigger for multiple requests |
| US20070060097A1 (en)* | 2005-08-02 | 2007-03-15 | Edge Stephen W | VOIP emergency call support |
| US7200380B2 (en)* | 2002-03-28 | 2007-04-03 | Telecommunication Systems, Inc. | Wireless telecommunications location based services scheme selection |
| US20070081635A1 (en)* | 2005-09-29 | 2007-04-12 | Marian Croak | Method and apparatus for providing enhanced 911 for nomadic users |
| US20070115941A1 (en)* | 2005-10-24 | 2007-05-24 | Ashish Patel | Peering Network for Parameter-Based Routing of Special Number Calls |
| US20070121601A1 (en)* | 1998-09-24 | 2007-05-31 | Genesys Telecommunications Laboratories, Inc | Integrating SIP Control Messaging into Existing Communication Center Routing Infrastructure |
| US20070149213A1 (en)* | 2005-11-30 | 2007-06-28 | Gaurav Lamba | Method and apparatus for supporting location services with roaming |
| US20080032703A1 (en)* | 2006-08-07 | 2008-02-07 | Microsoft Corporation | Location based notification services |
| US7330899B2 (en)* | 2003-06-05 | 2008-02-12 | Oracle International Corporation | Apparatus and method for developing applications with telephony functionality |
| US20080037715A1 (en)* | 2006-06-29 | 2008-02-14 | Nortel Networks Ltd. | Adaption of emergency calls to the emergency services network based on caller location |
| US7333480B1 (en)* | 2004-09-20 | 2008-02-19 | Nortel Networks Limited | Localization of call routing for TDM sets in an IP network |
| US20080059304A1 (en)* | 2006-08-16 | 2008-03-06 | Kimsey Robert S | Method of active advertising and promotion in an online environment |
| US20080065775A1 (en)* | 2006-09-13 | 2008-03-13 | Cisco Technology, Inc. | Location data-URL mechanism |
| US20080063153A1 (en)* | 2006-08-21 | 2008-03-13 | Connexon Telecom Inc. | System and method for delivering callback numbers for emergency calls in a voip system |
| US20080080691A1 (en)* | 2006-10-03 | 2008-04-03 | Stein E. Dolan | Call abuse prevention for pay-per-call services |
| US7369530B2 (en)* | 2004-01-30 | 2008-05-06 | Scott Keagy | Apparatus and method for interfacing packet-based phone services with emergency call centers |
| US7369508B2 (en)* | 2001-10-17 | 2008-05-06 | Spyder Navigations L.L.C. | Informing network about amount of data to be transferred |
| US20080117859A1 (en)* | 2006-11-21 | 2008-05-22 | Reza Shahidi | Dynamic operational mode management for a wireless terminal |
| US7382773B2 (en)* | 2002-08-16 | 2008-06-03 | Intervoice, Inc. | Contact center with normalized multiple protocol architecture |
| US20080146343A1 (en)* | 2006-12-14 | 2008-06-19 | Sullivan C Bart | Wireless video game system and method |
| US7392240B2 (en)* | 2002-11-08 | 2008-06-24 | Dun & Bradstreet, Inc. | System and method for searching and matching databases |
| US7495608B1 (en)* | 2006-06-16 | 2009-02-24 | Cellco Partnership | Position determination using almanac for virtual base stations |
| US20100029244A1 (en)* | 2007-11-05 | 2010-02-04 | Neeta Moodbidri | Method and system for allowing incoming emergency communications on a disabled device |
| US20100069034A1 (en)* | 2005-05-26 | 2010-03-18 | Richard Dickinson | E911 call blocking for non-initialized wireless telephones |
| US7711094B1 (en)* | 2005-11-16 | 2010-05-04 | Verizon Data Services Llc | E911 location server |
| US7881233B2 (en)* | 2004-09-01 | 2011-02-01 | Cisco Technology, Inc. | Techniques for planning a conference using location data |
| US7890122B2 (en)* | 2000-02-04 | 2011-02-15 | At&T Intellectual Property I, L.P. | Location privacy manager for a wireless communication device and method thereof |
| US7937067B2 (en)* | 2006-05-16 | 2011-05-03 | Red Sky Technologies, Inc. | System and method for an emergency location information service (E-LIS) |
| US20110113060A1 (en)* | 2008-04-30 | 2011-05-12 | Giovanni Martini | Method and system for enabling a user to get information about entities of predefined categories |
| US20120001750A1 (en)* | 2006-07-13 | 2012-01-05 | Henry Schein, Inc. | Central facility that communicates with portable container via mobile device |
| US20130072308A1 (en)* | 2011-09-15 | 2013-03-21 | Qonqr, Llc | Location-Based Multiplayer Game System and Method |
| US20130079152A1 (en)* | 2007-08-17 | 2013-03-28 | At&T Intellectual Property I, L.P. | Location-based mobile gaming application and method for implementing the same using a scalable tiered geocast protocol |
Family Cites Families (118)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US1103073A (en) | 1912-07-18 | 1914-07-14 | American Telephone & Telegraph | Emergency signaling system for telephone toll-collecting apparatus. |
| DE3639753A1 (en) | 1986-11-21 | 1988-06-01 | Inst Rundfunktechnik Gmbh | METHOD FOR TRANSMITTING DIGITALIZED SOUND SIGNALS |
| US4868570A (en)* | 1988-01-15 | 1989-09-19 | Arthur D. Little, Inc. | Method and system for storing and retrieving compressed data |
| US5055851A (en) | 1988-05-16 | 1991-10-08 | Trackmobile, Inc. | Vehicle location system |
| US4952928A (en) | 1988-08-29 | 1990-08-28 | B. I. Incorporated | Adaptable electronic monitoring and identification system |
| US5043736B1 (en) | 1990-07-27 | 1994-09-06 | Cae Link Corp | Cellular position location system |
| US5068656A (en) | 1990-12-21 | 1991-11-26 | Rockwell International Corporation | System and method for monitoring and reporting out-of-route mileage for long haul trucks |
| US6134316A (en) | 1996-10-18 | 2000-10-17 | Telefonaktiebolaget Lm Ericsson | Telecommunications network with relocateability of subscriber number |
| US6240294B1 (en) | 1997-05-30 | 2001-05-29 | Itt Manufacturing Enterprises, Inc. | Mobile radio device having adaptive position transmitting capabilities |
| US6108533A (en) | 1997-08-22 | 2000-08-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Geographical database for radio system |
| US6278701B1 (en) | 1998-07-10 | 2001-08-21 | Verizon Laboratories Inc. | Capacity enhancement for multi-code CDMA with integrated services through quality of services and admission control |
| US6321092B1 (en) | 1998-11-03 | 2001-11-20 | Signal Soft Corporation | Multiple input data management for wireless location-based applications |
| US20040198386A1 (en) | 2002-01-16 | 2004-10-07 | Dupray Dennis J. | Applications for a wireless location gateway |
| US6397208B1 (en) | 1999-01-19 | 2002-05-28 | Microsoft Corporation | System and method for locating real estate in the context of points-of-interest |
| SE9900710L (en) | 1999-02-25 | 2000-08-26 | Ericsson Telefon Ab L M | Method and device relating to communication networks for mobile phones |
| US6621810B1 (en) | 1999-05-27 | 2003-09-16 | Cisco Technology, Inc. | Mobile IP intra-agent mobility |
| US6795444B1 (en) | 1999-10-26 | 2004-09-21 | Telefonaktiebolaget L M Ericsson (Publ) | System and method for providing wireless telephony over a packet-switched network |
| US7269428B1 (en) | 1999-11-23 | 2007-09-11 | Nokia Coporation | Method for enabling a user to be notified of his/her positioning requests |
| US7603411B1 (en) | 1999-12-14 | 2009-10-13 | Nortel Networks Limited | Presence management system |
| US6940826B1 (en) | 1999-12-30 | 2005-09-06 | Nortel Networks Limited | Apparatus and method for packet-based media communications |
| AU2629601A (en) | 2000-01-07 | 2001-07-24 | Informio, Inc. | Methods and apparatus for an audio web retrieval telephone system |
| US7623447B1 (en) | 2000-04-10 | 2009-11-24 | Nokia Corporation | Telephony services in mobile IP networks |
| US7110773B1 (en) | 2000-04-11 | 2006-09-19 | Telecommunication Systems, Inc. | Mobile activity status tracker |
| GB2361389B (en) | 2000-04-15 | 2004-01-28 | Ericsson Telefon Ab L M | Telecommunications system |
| US7031268B1 (en) | 2000-05-17 | 2006-04-18 | Cisco Technology, Inc. | Call optimization in ad-hoc conference calls |
| US6737989B2 (en) | 2000-05-17 | 2004-05-18 | Omega Patents, L.L.C. | Vehicle tracker including variable frequency transmission and related methods |
| US8060389B2 (en) | 2000-06-07 | 2011-11-15 | Apple Inc. | System and method for anonymous location based services |
| US6539232B2 (en) | 2000-06-10 | 2003-03-25 | Telcontar | Method and system for connecting mobile users based on degree of separation |
| US6694351B1 (en) | 2000-06-30 | 2004-02-17 | Cisco Technology, Inc. | Call optimization in meet-me conference calls |
| AU2001285161A1 (en)* | 2000-08-21 | 2002-03-04 | United States Postal Services | Delivery point validation system |
| US7246187B1 (en) | 2000-11-28 | 2007-07-17 | Emc Corporation | Method and apparatus for controlling exclusive access to a shared resource in a data storage system |
| US6377793B1 (en) | 2000-12-06 | 2002-04-23 | Xybernaut Corporation | System and method of accessing and recording messages at coordinate way points |
| US7016847B1 (en) | 2000-12-08 | 2006-03-21 | Ben Franklin Patent Holdings L.L.C. | Open architecture for a voice user interface |
| FI112902B (en) | 2000-12-28 | 2004-01-30 | Nokia Corp | Method of conveying a position-dependent message, message transfer system and wireless communication device |
| US7099332B2 (en) | 2000-12-29 | 2006-08-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Emergency calling with a VoIP device in a VLAN environment |
| US7012901B2 (en) | 2001-02-28 | 2006-03-14 | Cisco Systems, Inc. | Devices, software and methods for generating aggregate comfort noise in teleconferencing over VoIP networks |
| KR100369803B1 (en) | 2001-03-10 | 2003-02-05 | 삼성전자 주식회사 | Packet voice call service method in wireless telecommunication network and network architecture therefor |
| US6594483B2 (en) | 2001-05-15 | 2003-07-15 | Nokia Corporation | System and method for location based web services |
| FI113001B (en) | 2001-05-28 | 2004-02-13 | Nokia Corp | A method and an arrangement for locating a terminal in a packet switched network and a terminal utilizing the method |
| US6427001B1 (en) | 2001-06-07 | 2002-07-30 | Bellsouth Intellectual Property Corporation | System and method for notification of 911 telephone calls using a link monitoring system |
| US20030044654A1 (en) | 2001-08-31 | 2003-03-06 | Holt Laurence E. | Extending external telephone calls as conference calls with other communicatively proximate wireless devices |
| DE60238073D1 (en) | 2001-10-30 | 2010-12-02 | Alexander C Lang | ADVANCED CALLS USING A BRIEFING SERVICE |
| US6813264B2 (en) | 2001-11-02 | 2004-11-02 | Qualcomm, Incorporated | System and method for routing voice over IP calls |
| EP1315389A1 (en) | 2001-11-16 | 2003-05-28 | Telefonaktiebolaget Lm Ericsson | Method for the determination of a receiver for location information |
| US6909776B2 (en) | 2001-12-19 | 2005-06-21 | Bellsouth Intellectual Property Corporation | Systems and methods for monitoring network-based voice messaging systems |
| US7072667B2 (en) | 2001-12-31 | 2006-07-04 | Nokia Corporation | Location information service for a cellular telecommunications network |
| US7321773B2 (en) | 2002-03-28 | 2008-01-22 | Telecommunication Systems, Inc. | Area watcher for wireless network |
| US6922565B2 (en) | 2002-03-28 | 2005-07-26 | Telecommunication Systems, Inc. | Public safety access point (PSAP) selection for E911 wireless callers in a GSM type system |
| US7426380B2 (en) | 2002-03-28 | 2008-09-16 | Telecommunication Systems, Inc. | Location derived presence information |
| JP4199475B2 (en) | 2002-04-11 | 2008-12-17 | 日本電気株式会社 | Positioning gateway device, terminal location information request processing method and program |
| US6957068B2 (en) | 2002-05-13 | 2005-10-18 | Qualcomm, Incorporated | Subscriber station with dynamic multi-mode service acquisition capability |
| US7136466B1 (en) | 2002-05-30 | 2006-11-14 | Bellsouth Intellectual Property Corporation | DSL integrated call waiting |
| ES2296950T3 (en) | 2002-07-04 | 2008-05-01 | Spyder Navigations L.L.C. | MANAGEMENT OF A CALL IN CONFERENCE BY SWITCHING PACKAGES. |
| JP4016787B2 (en) | 2002-07-31 | 2007-12-05 | 日本電気株式会社 | Positioning system in mobile communication network |
| AU2002368446A1 (en) | 2002-12-10 | 2004-06-30 | Nokia Corporation | Method and device for continuing an electronic multi-player game, in case of an absence of a player of said game |
| US20070238455A1 (en) | 2006-04-07 | 2007-10-11 | Yinjun Zhu | Mobile based area event handling when currently visited network doe not cover area |
| US20040143852A1 (en) | 2003-01-08 | 2004-07-22 | Meyers Philip G. | Systems and methods for massively multi-player online role playing games |
| ZA200506365B (en) | 2003-02-11 | 2006-04-26 | Mobix Global Holdings Ltd | Conference call facility |
| JP4517578B2 (en) | 2003-03-11 | 2010-08-04 | 株式会社日立製作所 | Peer-to-peer communication apparatus and communication method |
| US7730014B2 (en) | 2003-03-25 | 2010-06-01 | Hartenstein Mark A | Systems and methods for managing affiliations |
| US6963557B2 (en) | 2003-03-29 | 2005-11-08 | Intrado Inc. | System and method for routing telephone calls involving internet protocol network |
| US7403939B1 (en) | 2003-05-30 | 2008-07-22 | Aol Llc | Resolving queries based on automatic determination of requestor geographic location |
| ATE461593T1 (en) | 2003-06-27 | 2010-04-15 | Nortel Networks Ltd | ROUTING CALLS AND UPDATING ROUTING INFORMATION APPROPRIATELY |
| EP1656755B1 (en) | 2003-08-22 | 2016-12-21 | Nokia Technologies Oy | Facilitating location determination of a mobile station pursuant to a location based application |
| US7330112B1 (en) | 2003-09-09 | 2008-02-12 | Emigh Aaron T | Location-aware services |
| US7412050B2 (en) | 2003-10-01 | 2008-08-12 | Aol Llc, A Delaware Limited Liability Company | Conference calls via an intelligent call waiting interface |
| BRPI0415833A (en)* | 2003-10-23 | 2007-01-02 | Hoffmann La Roche | triaza-spiropiperidine derivatives for use as glyt-1 inhibitors in the treatment of neurological and neuropsychiatric disorders |
| US7113797B2 (en) | 2003-11-06 | 2006-09-26 | International Business Machines Corporation | System, method and program product for scheduling meetings |
| US7436785B1 (en) | 2003-11-12 | 2008-10-14 | Sprint Spectrum L.P. | Method and system for location based subject matter teleconferencing |
| US20050125493A1 (en) | 2003-11-13 | 2005-06-09 | Hemant Chaskar | IP-based mechanism for location service systems, methods, and devices |
| US7860811B2 (en) | 2004-11-04 | 2010-12-28 | Manyworlds, Inc. | Adaptive recommendation explanations |
| US7424293B2 (en) | 2003-12-02 | 2008-09-09 | Telecommunication Systems, Inc. | User plane location based service using message tunneling to support roaming |
| US6968044B2 (en) | 2003-12-05 | 2005-11-22 | Bellsouth Intellectual Property Corporation | Telephone emergency response system and method |
| US7181447B2 (en) | 2003-12-08 | 2007-02-20 | Iac Search And Media, Inc. | Methods and systems for conceptually organizing and presenting information |
| US7260186B2 (en) | 2004-03-23 | 2007-08-21 | Telecommunication Systems, Inc. | Solutions for voice over internet protocol (VoIP) 911 location services |
| US20080090546A1 (en) | 2006-10-17 | 2008-04-17 | Richard Dickinson | Enhanced E911 network access for a call center using session initiation protocol (SIP) messaging |
| CN101088273B (en) | 2003-12-22 | 2012-04-25 | 林克威尔公司 | System and method for initiating a conference call |
| US20050265318A1 (en) | 2004-01-08 | 2005-12-01 | Nokia Corporation | Apparatus, system, and method for rejecting a session establishment request |
| US20050169248A1 (en) | 2004-02-04 | 2005-08-04 | Nortel Networks Limited | Method and apparatus for providing in-band location information in an emergency response network |
| US7386111B2 (en) | 2004-02-10 | 2008-06-10 | Vonage Network Inc. | Method and apparatus for placing a long distance call based on a virtual phone number |
| US7123693B2 (en) | 2004-03-13 | 2006-10-17 | Intrado Inc. | Method and apparatus for increasing the reliability of an emergency call communication network |
| US7983835B2 (en) | 2004-11-03 | 2011-07-19 | Lagassey Paul J | Modular intelligent transportation system |
| KR101085633B1 (en) | 2004-05-17 | 2011-11-22 | 삼성전자주식회사 | Method of selecting location server of roaming mobile terminal and device and method for determining location of mobile terminal |
| WO2005115035A1 (en) | 2004-05-20 | 2005-12-01 | Research In Motion Limited | Handling an audio conference related to a text-based message |
| US8265587B2 (en) | 2004-06-17 | 2012-09-11 | West Corporation | System and method for amending instructions for emergency auxiliary services following an emergency services request |
| US8903820B2 (en) | 2004-06-23 | 2014-12-02 | Nokia Corporation | Method, system and computer program to enable querying of resources in a certain context by definition of SIP even package |
| US7764944B2 (en) | 2004-06-24 | 2010-07-27 | Alcatel-Lucent Usa Inc. | Method of providing a unique call back number for wireless 9-1-1 calls |
| US7260384B2 (en) | 2004-07-29 | 2007-08-21 | Sprint Spectrum L.P. | Method and system for dynamic selection of voice mail system |
| US7787611B1 (en) | 2004-09-17 | 2010-08-31 | Cisco Technology, Inc. | Packet telephony bridging server |
| US20080214273A1 (en) | 2004-09-21 | 2008-09-04 | Snoddy Jon H | System, method and handheld controller for multi-player gaming |
| US7532713B2 (en) | 2004-09-23 | 2009-05-12 | Vapps Llc | System and method for voice over internet protocol audio conferencing |
| US7573982B2 (en) | 2004-10-12 | 2009-08-11 | Bellsouth Intellectual Property Corporation | Methods and systems for managing a call session |
| US20060079330A1 (en) | 2004-10-13 | 2006-04-13 | Motorola, Inc. | Method and apparatus utilizing dynamic visual characters to address communications |
| US7113128B1 (en) | 2004-10-15 | 2006-09-26 | Telecommunication Systems, Inc. | Culled satellite ephemeris information for quick, accurate assisted locating satellite location determination for cell site antennas |
| US20060088152A1 (en) | 2004-10-21 | 2006-04-27 | Lightbridge, Inc. | Conference-call initiation |
| US20060117020A1 (en) | 2004-12-01 | 2006-06-01 | John Toebes | Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device |
| US8027658B2 (en) | 2004-12-10 | 2011-09-27 | At&T Intellectual Property I, L.P. | Enhanced emergency service provider |
| IL165817A0 (en) | 2004-12-16 | 2006-01-15 | Samsung Electronics U K Ltd | Electronic music on hand portable and communication enabled devices |
| US7747258B2 (en) | 2005-02-04 | 2010-06-29 | Qualcomm Incorporated | Method and apparatus for performing position determination with pre-session action |
| US7756253B2 (en) | 2005-02-22 | 2010-07-13 | At&T Intellectual Property Ii, Lp | Methods and systems for providing foreign call back number compatibility for VoIP E9-1-1 calls |
| US7545916B2 (en) | 2005-02-28 | 2009-06-09 | At&T Intellectual Property I | Methods of placing emergency calls using data networks |
| US20060258380A1 (en) | 2005-05-16 | 2006-11-16 | Kai Liebowitz | Interactive opt-in-messaging |
| US20060281437A1 (en) | 2005-06-13 | 2006-12-14 | Qwest Communications International Inc. | Systems and methods for supporting E911 emergency services in a data communications network |
| US9154907B2 (en) | 2005-06-21 | 2015-10-06 | Qualcomm Incorporated | Efficient periodic location reporting in a radio access network |
| US20060293024A1 (en) | 2005-06-23 | 2006-12-28 | Lucent Technologies Inc. | Methods and apparatus for improved 911 support for VoIP service |
| US7245900B1 (en) | 2005-08-24 | 2007-07-17 | Sprint Spectrum L.P. | Method and system for using basic service set identifiers (BSSIDs) for emergency services routing |
| US8185567B2 (en) | 2006-01-02 | 2012-05-22 | Telecommunication Systems, Inc. | Location aware content using presence information data formation with location object (PIDF-LO) |
| US20070160036A1 (en) | 2006-01-10 | 2007-07-12 | Smith David M | Method and system for servicing enhanced 911 calls |
| US8059789B2 (en) | 2006-02-24 | 2011-11-15 | Telecommunication Systems, Inc. | Automatic location identification (ALI) emergency services pseudo key (ESPK) |
| US7843901B2 (en) | 2006-03-02 | 2010-11-30 | Tango Networks, Inc. | Call flow system and method for use in a legacy telecommunication system |
| US8208461B2 (en) | 2006-04-04 | 2012-06-26 | Telecommunication Systems, Inc. | SS7 MAP/Lg+ to SIP based call signaling conversion gateway for wireless VoIP E911 |
| US8358645B2 (en) | 2006-04-14 | 2013-01-22 | Cisco Technology, Inc. | Determining a physical location of a VoIP endpoint device utilized to originate an emergency call |
| ATE514272T1 (en) | 2006-08-03 | 2011-07-15 | Accuris Technologies Ltd | ROAMING GATEWAY |
| US9319518B2 (en) | 2006-12-22 | 2016-04-19 | Bce Inc. | Method and system for configuring information regarding processing of calls involving a party |
| US20080214202A1 (en) | 2007-03-02 | 2008-09-04 | General Instrument Corporation | Method and Apparatus for Bluetooth Discoverability Using Region Estimation |
| US20090319180A1 (en) | 2007-04-27 | 2009-12-24 | Aaron Thomas Robinson | Emergency responder geographic information system |
| US8308570B2 (en) | 2009-11-18 | 2012-11-13 | Sony Computer Entertainment America Inc. | Synchronizing mission progress in peer-to-peer cooperative games |
| US20110149953A1 (en) | 2009-12-23 | 2011-06-23 | William Helgeson | Tracking results of a v2 query in voice over internet (VoIP) emergency call systems |
- 2008
- 2008-09-18USUS12/232,484patent/US9413889B2/enactiveActive
- 2008-09-18USUS12/232,507patent/US20090077077A1/ennot_activeAbandoned
- 2016
- 2016-07-22USUS15/217,095patent/US20160330321A1/ennot_activeAbandoned
Patent Citations (99)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4445118A (en)* | 1981-05-22 | 1984-04-24 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Navigation system and method |
| US4651156A (en)* | 1982-02-08 | 1987-03-17 | Mcgraw-Edison Co. | Integrated radio location and communication system |
| US4494119A (en)* | 1983-08-04 | 1985-01-15 | 122923 Canada Limited | Distress radiolocation method and system |
| US4891638A (en)* | 1987-10-30 | 1990-01-02 | Motorola, Inc. | Nationwide display pager with location readout |
| US4891650A (en)* | 1988-05-16 | 1990-01-02 | Trackmobile Inc. | Vehicle location system |
| US5014206A (en)* | 1988-08-22 | 1991-05-07 | Facilitech International Incorporated | Tracking system |
| US6253074B1 (en)* | 1996-01-10 | 2001-06-26 | Telefonaktiebolaget L/M Ericsson (Publ) | Cellular telecommunications systems having selectively associatable usage parameters |
| US6032051A (en)* | 1997-12-01 | 2000-02-29 | Telefonaktiebolaget L/M Ericsson | Wireless mobile comunication devices for group use |
| US6526026B1 (en)* | 1997-12-10 | 2003-02-25 | Intel Corporation | Digit transmission over wireless communication link |
| US6181939B1 (en)* | 1998-02-18 | 2001-01-30 | Nokia Networks Oy | Method of processing mobile station data |
| US6067045A (en)* | 1998-09-01 | 2000-05-23 | Hughes Electronics Corporation | Communication network initialization apparatus and method for fast GPS-based positioning |
| US6360102B1 (en)* | 1998-09-10 | 2002-03-19 | Ericsson Inc. | System and method for defining a subscriber location privacy profile |
| US20070121601A1 (en)* | 1998-09-24 | 2007-05-31 | Genesys Telecommunications Laboratories, Inc | Integrating SIP Control Messaging into Existing Communication Center Routing Infrastructure |
| US6564261B1 (en)* | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
| US20050020242A1 (en)* | 1999-07-29 | 2005-01-27 | Bryan Holland | Locator system |
| US6529500B1 (en)* | 1999-08-26 | 2003-03-04 | Verizon Laboratories Inc. | Unified messaging notification |
| US20030108176A1 (en)* | 1999-12-30 | 2003-06-12 | Fen-Chung Kung | Personal ip follow-me service |
| US7890122B2 (en)* | 2000-02-04 | 2011-02-15 | At&T Intellectual Property I, L.P. | Location privacy manager for a wireless communication device and method thereof |
| US6876734B1 (en)* | 2000-02-29 | 2005-04-05 | Emeeting.Net, Inc. | Internet-enabled conferencing system and method accommodating PSTN and IP traffic |
| US6731940B1 (en)* | 2000-04-28 | 2004-05-04 | Trafficmaster Usa, Inc. | Methods of using wireless geolocation to customize content and delivery of information to wireless communication devices |
| US6687504B1 (en)* | 2000-07-28 | 2004-02-03 | Telefonaktiebolaget L. M. Ericsson | Method and apparatus for releasing location information of a mobile communications device |
| US6898633B1 (en)* | 2000-10-04 | 2005-05-24 | Microsoft Corporation | Selecting a server to service client requests |
| US20020077084A1 (en)* | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a web advertiser |
| US20020077083A1 (en)* | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a wireless service provider |
| US20020077118A1 (en)* | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a wireless service provider |
| US20020077897A1 (en)* | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a web advertiser |
| US6744858B1 (en)* | 2001-01-26 | 2004-06-01 | Telcontrol, Inc. | System and method for supporting multiple call centers |
| US6847618B2 (en)* | 2001-06-29 | 2005-01-25 | Ip Unity | Method and system for distributed conference bridge processing |
| US20030009277A1 (en)* | 2001-07-03 | 2003-01-09 | Fan Rodric C. | Using location data to determine traffic information |
| US20030012148A1 (en)* | 2001-07-10 | 2003-01-16 | Michael Peters | Software based single agent multipoint conference capability |
| US20050043037A1 (en)* | 2001-07-16 | 2005-02-24 | Ioppe Igor V. | System for providing alert-based services to mobile stations in a wireless communications network |
| US20030026245A1 (en)* | 2001-07-31 | 2003-02-06 | Ejzak Richard Paul | Communication system including an interworking mobile switching center for call termination |
| US7369508B2 (en)* | 2001-10-17 | 2008-05-06 | Spyder Navigations L.L.C. | Informing network about amount of data to be transferred |
| US20030109245A1 (en)* | 2001-11-05 | 2003-06-12 | Mccalmont Patti L | Routing of emergency calls based on geographic location of originating telephone end office |
| US7177397B2 (en)* | 2001-11-05 | 2007-02-13 | Intrado Inc. | Geographic routing of emergency service call center emergency calls |
| US20030119521A1 (en)* | 2001-12-21 | 2003-06-26 | Shilpa Tipnis | Wireless network tour guide |
| US20030119528A1 (en)* | 2001-12-26 | 2003-06-26 | Boathouse Communication Partners, Llc | System and method for an automated intermediary to broker remote transaction between parties based on actively managed private profile information |
| US7200380B2 (en)* | 2002-03-28 | 2007-04-03 | Telecommunication Systems, Inc. | Wireless telecommunications location based services scheme selection |
| US6580390B1 (en)* | 2002-05-30 | 2003-06-17 | General Motors Corporation | Method and system for global positioning system mask angle optimization |
| US20060128395A1 (en)* | 2002-08-02 | 2006-06-15 | Janne Muhonen | Location services for mobile communication system |
| US7382773B2 (en)* | 2002-08-16 | 2008-06-03 | Intervoice, Inc. | Contact center with normalized multiple protocol architecture |
| US20040043775A1 (en)* | 2002-08-29 | 2004-03-04 | Kennedy Joseph P. | Tasking and reporting method and implementation for wireless appliance location systems |
| US20040047461A1 (en)* | 2002-09-10 | 2004-03-11 | Weisman Jordan Kent | Method and apparatus for improved conference call management |
| US6839417B2 (en)* | 2002-09-10 | 2005-01-04 | Myriad Entertainment, Inc. | Method and apparatus for improved conference call management |
| US7392240B2 (en)* | 2002-11-08 | 2008-06-24 | Dun & Bradstreet, Inc. | System and method for searching and matching databases |
| US6985747B2 (en)* | 2003-02-05 | 2006-01-10 | Autodesk, Inc. | Use of triggers and a location hypercube to enable push-based location applications |
| US7330899B2 (en)* | 2003-06-05 | 2008-02-12 | Oracle International Corporation | Apparatus and method for developing applications with telephony functionality |
| US20050053209A1 (en)* | 2003-09-06 | 2005-03-10 | D'evelyn Linda Kaye | Method and system for availing participants in a special number call event and others of information contained in a plurality of data stores |
| US20070019614A1 (en)* | 2003-09-09 | 2007-01-25 | Klaus Hoffmann | Method for providing a user interaction dialogue (uid) prior to connection acceptance by the called user |
| US20050063519A1 (en)* | 2003-09-22 | 2005-03-24 | Foundry Networks, Inc. | System, method and apparatus for supporting E911 emergency services in a data communications network |
| US20070022011A1 (en)* | 2003-10-06 | 2007-01-25 | Utbk, Inc. | Methods and apparatuses to determine prices of communication leads |
| US20050083891A1 (en)* | 2003-10-21 | 2005-04-21 | Chia-En Chuang | Method and apparatus for updating frame number |
| US20050083911A1 (en)* | 2003-10-21 | 2005-04-21 | 3Com Corporation, A Corporation Of The State Of Delaware | IP-based enhanced emergency services using intelligent client devices |
| US20050107673A1 (en)* | 2003-11-13 | 2005-05-19 | General Motors Corporation | System and method for maintaining and providing personal information in real time |
| US20050119012A1 (en)* | 2003-12-02 | 2005-06-02 | Alcatel | Method of transmitting area specific content |
| US20050135569A1 (en)* | 2003-12-19 | 2005-06-23 | Richard Dickinson | Enhanced E911 location information using voice over internet protocol (VoIP) |
| US20050136885A1 (en)* | 2003-12-22 | 2005-06-23 | Kaltsukis Calvin L. | Emergency conference calling system |
| US7174153B2 (en)* | 2003-12-23 | 2007-02-06 | Gregory A Ehlers | System and method for providing information to an operator of an emergency response vehicle |
| US7369530B2 (en)* | 2004-01-30 | 2008-05-06 | Scott Keagy | Apparatus and method for interfacing packet-based phone services with emergency call centers |
| US7177399B2 (en)* | 2004-02-27 | 2007-02-13 | Nortel Network Limited | Determining the geographical location from which an emergency call originates in a packet-based communications network |
| US20060120517A1 (en)* | 2004-03-05 | 2006-06-08 | Avaya Technology Corp. | Advanced port-based E911 strategy for IP telephony |
| US7177398B2 (en)* | 2004-03-13 | 2007-02-13 | Intrado Inc. | Bi-directional messaging for an emergency services network |
| US20060008065A1 (en)* | 2004-07-08 | 2006-01-12 | Timothy Longman | Method for setting up a conference call |
| US20060026288A1 (en)* | 2004-07-30 | 2006-02-02 | Arup Acharya | Method and apparatus for integrating wearable devices within a SIP infrastructure |
| US7881233B2 (en)* | 2004-09-01 | 2011-02-01 | Cisco Technology, Inc. | Techniques for planning a conference using location data |
| US20060073930A1 (en)* | 2004-09-08 | 2006-04-06 | Daimlerchrysler Ag | Transverse differential of a motor vehicle and method for production thereof |
| US7333480B1 (en)* | 2004-09-20 | 2008-02-19 | Nortel Networks Limited | Localization of call routing for TDM sets in an IP network |
| US20060068753A1 (en)* | 2004-09-22 | 2006-03-30 | Jim Karpen | Emergency call handling system |
| US20060135177A1 (en)* | 2004-10-29 | 2006-06-22 | James Winterbottom | Relating to internet protocol (IP) location, privacy and presence |
| US20060104306A1 (en)* | 2004-11-15 | 2006-05-18 | Maria Adamczyk | Application services infrastructure for next generation networks |
| US20070041513A1 (en)* | 2005-02-08 | 2007-02-22 | Gende Michael F | Emergency call identification, location and routing method and system |
| US20070041516A1 (en)* | 2005-05-26 | 2007-02-22 | Richard Dickinson | E911 call blocking for non-initialized wireless telephones |
| US20100069034A1 (en)* | 2005-05-26 | 2010-03-18 | Richard Dickinson | E911 call blocking for non-initialized wireless telephones |
| US20070003024A1 (en)* | 2005-06-22 | 2007-01-04 | Cml Emergency Services Inc. | Network emergency call taking system and method |
| US20070026871A1 (en)* | 2005-07-28 | 2007-02-01 | Openwave Systems Inc. | Wireless network with adaptive autonomous location push |
| US20070027997A1 (en)* | 2005-07-29 | 2007-02-01 | Cisco Technology, Inc. | Technique for translating location information |
| US20070060097A1 (en)* | 2005-08-02 | 2007-03-15 | Edge Stephen W | VOIP emergency call support |
| US20070036139A1 (en)* | 2005-08-09 | 2007-02-15 | Ashish Patel | System and method for authenticating internetwork resource requests |
| US20070042765A1 (en)* | 2005-08-19 | 2007-02-22 | Global Locate, Inc. | Method and apparatus for providing intelligent deactivation of electronic devices in aircraft |
| US20070049288A1 (en)* | 2005-08-24 | 2007-03-01 | Lamprecht Leslie J | Creating optimum temporal location trigger for multiple requests |
| US20070081635A1 (en)* | 2005-09-29 | 2007-04-12 | Marian Croak | Method and apparatus for providing enhanced 911 for nomadic users |
| US20070115941A1 (en)* | 2005-10-24 | 2007-05-24 | Ashish Patel | Peering Network for Parameter-Based Routing of Special Number Calls |
| US7711094B1 (en)* | 2005-11-16 | 2010-05-04 | Verizon Data Services Llc | E911 location server |
| US20070149213A1 (en)* | 2005-11-30 | 2007-06-28 | Gaurav Lamba | Method and apparatus for supporting location services with roaming |
| US7937067B2 (en)* | 2006-05-16 | 2011-05-03 | Red Sky Technologies, Inc. | System and method for an emergency location information service (E-LIS) |
| US7495608B1 (en)* | 2006-06-16 | 2009-02-24 | Cellco Partnership | Position determination using almanac for virtual base stations |
| US20080037715A1 (en)* | 2006-06-29 | 2008-02-14 | Nortel Networks Ltd. | Adaption of emergency calls to the emergency services network based on caller location |
| US20120001750A1 (en)* | 2006-07-13 | 2012-01-05 | Henry Schein, Inc. | Central facility that communicates with portable container via mobile device |
| US20080032703A1 (en)* | 2006-08-07 | 2008-02-07 | Microsoft Corporation | Location based notification services |
| US20080059304A1 (en)* | 2006-08-16 | 2008-03-06 | Kimsey Robert S | Method of active advertising and promotion in an online environment |
| US20080063153A1 (en)* | 2006-08-21 | 2008-03-13 | Connexon Telecom Inc. | System and method for delivering callback numbers for emergency calls in a voip system |
| US20080065775A1 (en)* | 2006-09-13 | 2008-03-13 | Cisco Technology, Inc. | Location data-URL mechanism |
| US20080080691A1 (en)* | 2006-10-03 | 2008-04-03 | Stein E. Dolan | Call abuse prevention for pay-per-call services |
| US20080117859A1 (en)* | 2006-11-21 | 2008-05-22 | Reza Shahidi | Dynamic operational mode management for a wireless terminal |
| US20080146343A1 (en)* | 2006-12-14 | 2008-06-19 | Sullivan C Bart | Wireless video game system and method |
| US20130079152A1 (en)* | 2007-08-17 | 2013-03-28 | At&T Intellectual Property I, L.P. | Location-based mobile gaming application and method for implementing the same using a scalable tiered geocast protocol |
| US20100029244A1 (en)* | 2007-11-05 | 2010-02-04 | Neeta Moodbidri | Method and system for allowing incoming emergency communications on a disabled device |
| US20110113060A1 (en)* | 2008-04-30 | 2011-05-12 | Giovanni Martini | Method and system for enabling a user to get information about entities of predefined categories |
| US20130072308A1 (en)* | 2011-09-15 | 2013-03-21 | Qonqr, Llc | Location-Based Multiplayer Game System and Method |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090298492A1 (en)* | 2008-06-02 | 2009-12-03 | West Corporation | System, apparatus and method for availing a mobile call of address information |
| US8208909B2 (en)* | 2008-06-02 | 2012-06-26 | West Corporation | System, apparatus and method for availing a mobile call of address information |
| US20110087839A1 (en)* | 2009-10-09 | 2011-04-14 | Verizon Patent And Licensing Inc. | Apparatuses, methods and systems for a smart address parser |
| US8271525B2 (en)* | 2009-10-09 | 2012-09-18 | Verizon Patent And Licensing Inc. | Apparatuses, methods and systems for a smart address parser |
| US20130143516A1 (en)* | 2011-12-02 | 2013-06-06 | Andrew Llc | Enabling location determination of user device originating emergency service call |
| US8929855B2 (en)* | 2011-12-02 | 2015-01-06 | Maple Acquisition Llc | Enabling location determination of user device originating emergency service call |
Also Published As
| Publication number | Publication date |
|---|---|
| US20090092232A1 (en) | 2009-04-09 |
| US20160330321A1 (en) | 2016-11-10 |
| US9413889B2 (en) | 2016-08-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7773975B2 (en) | Providing an indication of network capabilities to a user for special number calls | |
| US20090077077A1 (en) | Optimal selection of MSAG address for valid civic/postal address | |
| US8068587B2 (en) | Nationwide table routing of voice over internet protocol (VOIP) emergency calls | |
| US9743378B2 (en) | Associating metro street address guide (MSAG) validated addresses with geographic map data | |
| US8880021B2 (en) | System and method for updating location information of voice-over-internet protocol based devices for E911 services | |
| US8520805B2 (en) | Video E911 | |
| US6963557B2 (en) | System and method for routing telephone calls involving internet protocol network | |
| US8830987B2 (en) | IP-based call answering point selection and routing | |
| US8554168B1 (en) | Systems and methods for alternative routing of voice over IP originated emergency calls | |
| US8442204B2 (en) | Real-time update of location information regarding a communications device | |
| US20050090225A1 (en) | A Simplified Second Generation Enhanced Emergency Communications System SSGE-911 | |
| US20050169248A1 (en) | Method and apparatus for providing in-band location information in an emergency response network | |
| US9401986B2 (en) | Unique global identifier header for minimizing prank emergency 911 calls | |
| US8503973B1 (en) | Method and system for obtaining emergency caller location | |
| US9584661B2 (en) | Extended efficient usage of emergency services keys | |
| US8280341B2 (en) | GPS-assisted architecture for VoIP 9-1-1 | |
| US20180220275A1 (en) | Supplemental location information for an emergency services call | |
| US20100046720A1 (en) | Point-in-poly routing for voice over internet protocol (VoIP) emergency calls with embedded geographic location information | |
| US20160029196A1 (en) | System and method for routing emergency services calls from fixed wireless terminals | |
| US8532266B2 (en) | Efficient usage of emergency services keys |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AS | Assignment | Owner name:TELECOMMUNICATION SYSTEMS, INC., MARYLAND Free format text:ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GELDENBOTT, GERHARD;HINES, GORDON JOHN;MARTIN, JEFFREY THOMAS;AND OTHERS;REEL/FRAME:021612/0276;SIGNING DATES FROM 20080916 TO 20080917 | |
| AS | Assignment | Owner name:SILICON VALLEY BANK, AGENT, MASSACHUSETTS Free format text:SECURITY AGREEMENT;ASSIGNORS:TELECOMMUNICATION SYSTEMS, INC.;LONGHORN ACQUISITION, LLC;SOLVERN INNOVATIONS, INC.;AND OTHERS;REEL/FRAME:023870/0484 Effective date:20091231 Owner name:SILICON VALLEY BANK, AGENT,MASSACHUSETTS Free format text:SECURITY AGREEMENT;ASSIGNORS:TELECOMMUNICATION SYSTEMS, INC.;LONGHORN ACQUISITION, LLC;SOLVERN INNOVATIONS, INC.;AND OTHERS;REEL/FRAME:023870/0484 Effective date:20091231 | |
| STCB | Information on status: application discontinuation | Free format text:ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION | |
| AS | Assignment | Owner name:QUASAR ACQUISITION, LLC, GEORGIA Free format text:RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date:20160223 Owner name:SOLVEM INNOVATIONS, INC., MARYLAND Free format text:RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date:20160223 Owner name:NETWORKS IN MOTION, INC., WISCONSIN Free format text:RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date:20160223 Owner name:LONGHORN ACQUISITION, LLC, MARYLAND Free format text:RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date:20160223 Owner name:TELECOMMUNICATION SYSTEMS, INC., MARYLAND Free format text:RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date:20160223 |