WO2012177279A1 - Procédé et système d'alerte par messagerie cellulaire - Google Patents

Procédé et système d'alerte par messagerie cellulaire Download PDF

Info

Publication number
WO2012177279A1
WO2012177279A1 PCT/US2011/059547 US2011059547W WO2012177279A1 WO 2012177279 A1 WO2012177279 A1 WO 2012177279A1 US 2011059547 W US2011059547 W US 2011059547W WO 2012177279 A1 WO2012177279 A1 WO 2012177279A1
Authority
WO
WIPO (PCT)
Prior art keywords
alert
location
database
location register
cellular
Prior art date
Application number
PCT/US2011/059547
Other languages
English (en)
Inventor
Donald J. VELLA
Jeffrey N. REAM
Original Assignee
Cmas Holdings, Llc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Cmas Holdings, Llc filed Critical Cmas Holdings, Llc
Publication of WO2012177279A1 publication Critical patent/WO2012177279A1/fr

Links

Classifications

    • 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/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • 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
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • This invention relates generally to the field of alert systems and, more specifically, to a method and system for providing an alert using wireless telecommunication technology.
  • EAS Emergency Broadcast System
  • a specific location alert receiver to alert members of the public.
  • a receiver can be a device that is plugged into a common household electrical outlet.
  • the alert of the receiver is activated by an incoming transmission from an authorized authority with access to a transmitting source in the specific area of the devices such as cell phone towers or transmitting vehicles and activates any number of devices within one home and/or all homes simultaneously.
  • the device can be mobile so as to be powered at remote locations.
  • Yet another approach is to require users to subscribe to an alerting service, wherein a subscriber database is maintained for storing information on the subscribers. Users may be required to pay a subscription fee in order to receive alerts from the alerting service. Additionally, these services often require a user to provide personal information beyond what is necessary to alert the user, for example, information on age, gender, yearly income, etc.
  • a person's radio and/or television must be turned on in order for them to receive the alert information. Unlike with cellular phones, these devices are usually not turned on except during actual use by their owner. Even further, these broadcasting systems are limited in their ability to narrowly target a percentage of the population and/or a specific location, wherein those persons receiving the alert who are outside of the hazard area may become desensitized to future alert broadcasts. Further still, these broadcasting systems indiscriminately provide the alert information to an area and fail to consider that individuals may be outside the alert area, for example, away on vacation. Even further, because periodic test broadcasts may be required to insure that the broadcasting system is in working order, the population at large may become desensitized to broadcast alert indications.
  • devices such as specific location alert receivers also have various drawbacks.
  • users are required to purchase, install, and maintain separate equipment for the purpose of receiving alerts.
  • users must carry around this additional equipment in order for it to be effective in providing alerts away from the user's home.
  • subscription-based alert services also have various drawbacks.
  • users must provide their information in advance to receive any alerts, and often must pay a periodic subscription fee as well.
  • users may not have the time, energy, desire, etc. to proactively subscribe to an alert service.
  • users are discouraged from subscribing to these alert services out of fear that their personal information may be misused, such as for sending unsolicited messages (i.e., spam), or simply sold to third parties without their consent.
  • users may deem these services cost prohibitive.
  • subscription alert services require users to voluntarily subscribe.
  • subscription alert services represent an ineffective tool for alerting a large percentage of the population in a targeted geographical region.
  • the present invention satisfies the aforementioned objects and provides the aforementioned advantages.
  • the present invention encompasses a method for providing an alert message, comprising (a) selecting at least one location for the alert to encompass; (b) determining at least one phone number based on the selected at least one location, each phone number corresponding to a wireless device; (c) inputting message data; (d) generating an alert message using the message data; and (e) sending the alert message to said at least one wireless device in the selected at least one location.
  • the present invention encompasses a system for providing an alert message, comprising (a) a web interface server, (b) a launch server; and (c) a system database, wherein the web interface server, the launch server, and the system database are connected.
  • An alert originator connects to the web interface server and selects a location for the alert to encompass.
  • the web interface server then accesses a system database to determine phone numbers corresponding to the selected location, wherein each phone number belongs to a wireless device of a potential alert recipient.
  • the web interface server collects message data input by the alert originator.
  • the web interface server transfers each determined phone number and the.message data to a launch server, and the launch server generates an alert message from the message data.
  • the launch server sends the alert message to the wireless devices corresponding to the determined phone numbers in the selected location.
  • FIG. 1 illustrates an exemplary method for providing an alert
  • FIGS. 2A-2B illustrate another exemplary method for providing an alert
  • FIG. 3 illustrates an exemplary system and network architecture for providing an alert
  • FIG. 4 illustrates exemplary approaches for selecting locations for an alert to encompass
  • FIG. 5 illustrates an exemplary location selection menu
  • FIG. 6 illustrates an exemplary data input screen
  • FIG. 7 illustrates another exemplary data input screen
  • FIG. 8 illustrates another exemplary system and network architecture for providing an alert.
  • FIG. 9 illustrates another exemplary system and network architecture for providing an alert.
  • FIG. 1 illustrates a method that can be used by an alert originator, such as a law enforcement agency or an emergency management official, to alert a large percentage of the population in a geographic area of an event, message or individual.
  • an alert originator such as a law enforcement agency or an emergency management official
  • the alert originator selects a location for the alert to encompass (S 100). Any manner of data input can be used to select the location.
  • a hierarchical series of menus are provided to the alert originator to select the location. For example, a listing of all fifty states is provided. Upon selecting a particular state, a listing of all of the counties in the state is provided.
  • a listing of major cities, major airports, etc. in the state can be provided.
  • Use of a hierarchy of menus provides a simple mechanism for the alert originator to quickly and narrowly target the intended recipients of the alert.
  • the information on states, counties, cities, airports, etc. is readily available through government resources and other documented resources.
  • maps are displayed to the alert originator for selecting the location.
  • maps of the continental United States, Alaska, Hawaii and regional maps can be displayed. Additionally, maps of other countries, such as Canada or Mexico, could be displayed.
  • the alert originator uses an input device, such as a mouse or stylus, to draw a right-angle geometric shape on the map. The geometric shape indicates the area for the alert to be sent.
  • the maps can be proprietary or supplied by a third party, such as Maponics.
  • the maps are in a Mercator format.
  • This format allows for a flat image to be plotted with longitude and latitude on an area that is spherical.
  • the maps can be calibrated by using a mathematical equation that converts the pixels of the image into degrees of longitude and latitude.
  • a mathematical equation that converts the pixels of the image into degrees of longitude and latitude.
  • the alert originator draws the geometric shape on the map using a software program, which defines an initial pressing "click" of the input device as a starting point (with coordinates xl, yl) and the subsequent releasing "click” of the input device as an ending point (with coordinates xc, ye), wherein c equals the current position.
  • a software program defines an initial pressing "click" of the input device as a starting point (with coordinates xl, yl) and the subsequent releasing "click” of the input device as an ending point (with coordinates xc, ye), wherein c equals the current position.
  • a list of predefined locations is provided to the alert originator to select the location for the alert.
  • a database storing
  • alert originator can search the database based on various search criteria such as "display only airports" or “display only locations currently open for business", in order to have a customized list displayed. The contents of the database are updated as needed.
  • the alert originator contacts a website to select the location.
  • the alert originator can contact the website via the World Wide Web or via a dedicated line.
  • the recipients of the alert are determined based on the selected location (SI 10).
  • a database stores information including contact information, such as phone numbers, as well as geographic information.
  • contact information such as phone numbers
  • geographic information such as city, city, etc.
  • SI 20 For example, the alert originator is prompted for any data to be included in an alert message, such as text and/or image data.
  • the alert originator contacts a website to input the text data for the alert message.
  • the website can provide a text box for collection of the text data, whereby the alert originator types their text data directly on the website.
  • a character counter can be provided for notifying the alert originator how many characters have currently been input.
  • a maximum number of characters allowed can be displayed. By subtracting the current character count from the maximum characters allowed, the alert originator can be notified of how many additional characters can be entered before the character limit is reached.
  • the alert originator wants to include image data, for example a picture, in the alert message, the alert originator is prompted to provide the image data.
  • the alert originator can e-mail the image data (e.g., a JPEG image file) to a particular address, such as that of the website, or use a file transfer program, such as one based on the File Transfer Protocol, to transfer the image data to a specified location, such as that of the website.
  • predefined images/icons can be presented to the alert originator to designate for inclusion in the alert message.
  • an alert message is generated to include any data input by the alert originator (SI 20)
  • the alert is delivered to the intended recipients (SI 30).
  • the alert message is sent to the recipients as a text message, such as an SMS message.
  • the alert message can be sent over the Internet to the various communications service providers servicing the recipients, wherein the recipients receive the alert in a timely and simple manner.
  • FIGS. 2A and 2B illustrate another exemplary method for providing an alert to a target audience.
  • an alert originator selects one or more locations, for example using any of the aforementioned approaches (S200).
  • an alert originator is able to specify the location for an alert to encompass with increased precision.
  • the alert originator contacts a website to select the one or more locations.
  • the alert originator's authority is verified as a security measure (S210).
  • the alert originator is required to enter a correct user name and password.
  • the alert originator's authority is verified before performing any alert recipient determinations.
  • the alert originator may also be required, as an additional security measure, to verbally provide an identification code before delivery of the alert message will commence.
  • this "launch code" will be unique to a specific user/entity.
  • the alert originator is verified as a security measure (S210).
  • the alert originator is required to enter a correct user name and password.
  • the alert originator's authority is verified before performing any alert recipient determinations.
  • the alert originator may also be required, as an additional security measure, to verbally provide an identification code before delivery
  • identification code will be changed at random intervals. Additionally, the alert originator can be required to verbally provide the identification code to another "live" individual, thereby providing a sort of "failsafe” to keep unauthorized individuals from sending an unwarranted alert.
  • phone numbers for recipients of alert are determined based on the selected one or more locations (S220).
  • these phone numbers are cellular phone numbers.
  • a database stores information including cellular phone number information and geographic information.
  • the database can include information from third party resources.
  • the database can be the result of merging two or more existing databases, such as those provided by Bellcore and PC
  • the system database can include vertical and horizontal coordinates information, geographic longitude and latitude information, three digit area codes, three digit exchanges, four digit Operating Company Numbers (OCNs), city and state information, and county information.
  • OCNs Operating Company Numbers
  • the system database can be populated with the necessary information without using information solicited from or directly provided by any potential recipients. Additionally, information can be retrieved from the system database for display on a website.
  • the Bellcore database is provided by Telcordia and has monthly updates.
  • Bellcore database has indicators to describe the type of service in a particular exchange, for example, plain old telephone service (POTS), pager, wireless, etc.
  • POTS plain old telephone service
  • pager pager
  • wireless etc.
  • the information relating to wireless devices, as described by Bellcore is retrieved from the Bellcore database.
  • cellular phone numbers for the recipients of the alert are retrieved based on the selected one or more locations (S220).
  • the approximate number of potential recipients is calculated by taking the total number of available lines in the defined area and dividing by 2. This formula was derived by taking the stated number of cellular phones from the FCC and the total number of available lines as defined in the Bellcore database. Thus, an alert originator receives an estimate of the number of potential recipients based on the selected one or more locations.
  • the geographic center of county is determined and a circular search is conducted outward from the center, in order to make sure that viable individuals are located and identified as recipients of the alert. For example, the circular search continues outward to a maximum radius of 100 miles, and for every 25 mile radius covered by the search, a number of located target recipients is reported.
  • the alert originator can halt the search at anytime.
  • the alert originator is prompted for any data to be included in an alert message, such as text and/or image data (S230). As discussed above, preferably, but not necessarily, the alert originator contacts a website to input the text data for the alert message.
  • an alert message is generated to include any data input by the alert originator (S240).
  • the alert message can be in a proprietary format or can adhere to an established standard, such as for SMS messages.
  • cellular phone numbers for recipients that have left the targeted area are discarded (S250).
  • individuals that are "roaming" in the targeted area can be considered recipients and their cellular phone numbers added to the information relating to the determined recipients.
  • HLR Home Location Register
  • VLR Visitor Location Register
  • ESN ESN Number that associates the cellular subscriber's phone number with the cellular subscriber's current wireless device, and the carrier identification.
  • interfacing with these databases provides numerous advantages. For example, interfacing with the HLR and VLR databases allows for the effective delivery of messages to individuals in high tourist traffic areas, such as Disney World, who would otherwise not receive the alert message because their home location was not a targeted location. Furthermore, the sending of alert messages to individuals who are traveling outside of their home location and therefore have no need for the notification in the targeted area, can be avoided. [0057] Furthermore, prior to delivery of the alert message to the recipients via their cellular phones, the alert message is formatted to comply with the particular address format of each cellular carrier that provides service to one or more of the recipients (S260). The aforementioned OCNs, retrieved from the system database, indicate the identity of the relevant cellular carriers.
  • An address format used by each of these relevant cellular carriers is determined and is used to format the alert message for delivery to those recipients serviced by each of the relevant cellular carriers. For example, if it is determined that a particular three digit exchange belongs to AT&T, those 10,000 alert messages would be formatted as
  • Another exchange might belong to Verizon, such that an address format of 10DIGITS@vtext.com is used, and another exchange might belong to Cingular, such that a format of 10DIGITS@mobile.mycingular.com is used.
  • the proper address format e.g., email address
  • 10DIGITS@mobile.attmet. Another exchange might belong to Verizon, such that an address format of 10DIGITS@vtext.com is used, and another exchange might belong to Cingular, such that a format of 10DIGITS@mobile.mycingular.com is used.
  • the proper address format e.g., email address
  • secondary integration can increase efficiency, although it requires third party cooperation. For example, instead of formatting and sending the 10,000 alert messages, as described above, a single alert message is sent to the cellular carrier's SMS server with instructions for that server to launch a corresponding message to all cell phones currently registered in the server's HLR/VLR database. This approach would require cooperation from, and connectivity to, the targeted cellular carriers, but would speed the delivery of the alert message to the targeted recipients.
  • alert message Once the alert message has been properly formatted based on the recipients' cellular carriers (S260), these formatted alert messages are delivered to the recipients via their cellular devices, such as cellular phones (S270). Preferably, but not necessarily, the formatted alert messages are delivered to the appropriate cellular carriers via the Internet.
  • the alert originator is notified of the delivery completion, for example via e-mail (S280).
  • FIG. 3 illustrates an exemplary system for providing an alert 300, and the related network layout.
  • a web interface server 325 and a launch server 330 are connected through a network connection, such as an Ethernet connection 350.
  • a network connection such as an Ethernet connection 350.
  • the web interface server 325 and the launch server 330 can be integrated into a single server, which combines the functionality of the individual servers.
  • a first alerting agency 305 connects to the web interface server 325 via the
  • a second alerting agency 310 connects to the web interface server 325 via a dedicated communications line 315.
  • the web interface server 325 displays information to alerting agencies 305 and 310, for example in the form of one or more web pages.
  • the alerting agencies 305 and 310 can interact with these web pages through the web interface server 325 to select one or more locations for an alert to encompass, using any of the approaches discussed above.
  • an alerting agency can elect to choose an individual state and/or county to send an alert (405), can choose a selected security force (410), or use an input device to drag a box around a target area of a displayed map (420).
  • the web page displayed by web interface server 325 can also contain a box 440 containing the current longitude and latitude coordinates.
  • the contents of a web page displayed by the web interface server 325 can represent a sub-menu within a menu hierarchy.
  • the submenu 500 of FIG. 5 was displayed in response to an alerting agency 305 or 310 selecting New York 510 as a state containing counties to be targeted by the alert.
  • the sub-menu 500 includes a scrollable list 520 of all of the counties in New York.
  • the web page provides instructions to an alerting agency 305 or 310 for selecting one or more locations, for example
  • the web interface server 325 accesses a system database 335 in order to determine the recipients for the alert within the defined area.
  • the system database 335 can include data from third-party databases such as a
  • the web interface server 325 receives message data from an alerting agency 305 or 310 to be included in the alert message.
  • a web page can contain a text box for collection of text data, whereby an alerting agency 305 or 310 types their text data directly in the text box of the web page.
  • FIG. 6 illustrates an exemplary data input screen 600, including a display of the estimated number of recipients for the selected one or more locations (605) and a text box 610 for entering message data to be included in the alert message. Because some text message standards (e.g., SMS) place character limits on their messages, the data input screen 600 indicates a maximum number of characters permitted in an alert message (620), and the data input screen 600 includes a box indicating the number of characters remaining that can be input for the alert message (625). Additionally, the data input screen 600 includes a "send" button 640 for sending the message data contained in the text box 610 and a "clear” button 645 for clearing the contents of the text box 610.
  • SMS Short Messaging
  • FIG. 7 illustrates another exemplary data input screen 700, including instructions for selection multiple locations for the alert (705), a scrollable list of predefined alert locations (i.e., airports) 720, a text box 730 for entering message data to be included in the alert message, an indication of the number of characters remaining that can be input for the alert message (740), and a "clear" button 750 for clearing the contents of the text box 730.
  • the data input screen 700 also includes an authentication code field 760 and a user name field 765 for an alerting agency 305 or 310 to input their authentication code and user name, thereby verifying their authorization to send alert messages.
  • the web interface server 325 combines the input message data with the information polled from the system database and outputs the result to a file.
  • the web interface server 325 then transfers this file to the web launch server 330, for example over Ethernet connection 350.
  • the launch server 330 accesses the system database 335 in order to determine an address format that a particular cellular carrier 380 or 385 utilizes for receiving text messages. Thereafter, the launch server 330 formats the alert message to comply with an address format of a particular cellular carrier providing service to the recipients. The launch server 330 then sends the formatted messages to a public network (the Internet 320), for example via a Cisco router interface. With up to 40 Megs of burstable bandwidth, the launch server 330 can send up to 100,000 messages per minute.
  • a public network the Internet 320
  • Cisco router interface With up to 40 Megs of burstable bandwidth, the launch server 330 can send up to 100,000 messages per minute.
  • the launch server 330 instead of formatting the alert message based on a particular cellular carrier 380 or 385, the launch server 330 simply sends the unformatted alert message to the SMS server 355/357 of the cellular carrier 380/385 with instructions for the SMS server 355/357 to launch a properly formatted message to all cellular phone currently registered in the SMS server's HLR/VLR database 360.
  • the launch server 330 preferably, but not necessarily, sends an e-mail receipt to the alerting agency 305 or 310 as notification of delivery completion.
  • the launch server 330 accesses HLR databases and VLR databases to determine which intended recipients are outside of the targeted area, as well as to determine if any individuals are "roaming" in the targeted area and should therefore be considered intended recipients of the alert message.
  • the launch server accesses HLR database 365 and VLR database 367, and determines that intended recipient 375 is not currently in the targeted area, while roaming user 379 is currently in the targeted area. Therefore, the launch server 330 insures that the cellular subscriber 375 does not receive the alert message, while the roaming user 379 does receive the alert message.
  • the alert system 300 is operated by a single agency, for example the Department of Homeland Security. Other agencies, for example local law enforcement agencies, would access the alert system 300 through the Department's website. The Department's personnel would be responsible for verifying and authenticating all external alert originators, as well as for the actual launch of the prescribed alert.
  • the software and hardware constituting the alert system 300 can be distributed to numerous agencies and organizations at the national, state, and local levels.
  • the hardware of the alert system 300 can be installed and managed on an agency-by- agency basis. Thus, individuals at each installation site would be responsible for
  • One advantage to this de-centralized approach is that it would facilitate communities to use the alert system 300 in different ways. For example, while the Los Angeles Police Department might only launch messages that adhere to today's Amber Alert criteria, a Sheriff in a rural community might launch a message for a far more minor incident, such as a stolen car or a lost cat.
  • the hardware of the alert system 300 is duplicated at another secure location.
  • the alert system 300 which is located for example in Dallas, TX, is duplicated at a location in Los Angeles, CA.
  • the network itself is designed to reroute traffic, should one site be down. This redundancy substantially increases the reliability of disseminating an alert to the public using the alert system 300.
  • FIG. 8 shows an alternative embodiment.
  • different handsets 770 are in communication with different cellular towers 775.
  • the handsets or other cellular devices are honing on a particular cellular tower 775 located within their service area.
  • the service towers 775 have a controlling switching platform located on the premises, called a base station (labeled Cell 780 in FIG. 8).
  • Base stations 780 are hardwired to a Base Station Controller 785 by both voice and data circuits (Abis
  • the Base Station Controller (BSC) 785 keeps track of the signal strength the handset is emitting to the receiving towers. As the signal strength decreases on the present servicing tower and increase on an adjacent tower, the Base Station Controller 785 handles the seamless handoff of the handset from one servicing tower to the next.
  • the Base Station Controllers 785 are connected to a Mobile Switching Center 790 by both voice and data channels ("A" Interface).
  • Mobile Switching Center, (MSC) 790 is the interconnect point for a cellular subscriber to reach other cell phones within the wireless carrier's network or any other wireless or landline device outside of the network.
  • the MSC 790 controls several Base
  • Station Controllers 785 and thus multiple tower locations in a given area.
  • one MSC might control all of the towers servicing a forty square block area.
  • the MSC servicing the northern section of Phoenix, AZ is also responsible for all of the towers in Flagstaff, AZ.
  • the MSC 790 has a Visitor Location
  • VLR Visit Location Registry
  • the HLR 800 houses all of the subscriber information pertinent to the consumer. This information includes billing name, address, cell plan and features associated with the subscribers account. When the MSC 790 recognizes a new device in its service area it informs the HLR 800. This new device could, for example, be an existing subscriber who has transited from another servicing MSC, or an out of network device known as a "roamer". This updated information to the HLR 800 is how the carrier's network knows which MSC 790 to route a voice call or text to a device when a service request comes in.
  • the VLR (Visitor Location Registry) 795 which resides within the MSC 790, houses the information regarding the mobile devices location.
  • the MSC 790 updates the VLR 795 with "real time" information as to what tower ID is currently servicing the handset.
  • the device As the device travels in and around the MSC's servicing area, it constantly updates the VLR 795 with current tower information so that incoming calls and/or data/texts can be routed appropriately.
  • a quick five minute trip to the airport might be serviced out of one MSC, but as you are in transit, you may be handed off to multiple different towers. Each hand off is updated in the VLR 795.
  • the system passively monitors two data feeds to the VRL 795, ("A" and "D" interface links). These data feeds are provided to a compiling server 805 having its own associated pseudo or auxiliary VLR 810. As shown in the exemplary embodiment of FIG. 8, this pseudo or auxiliary VLR database 810 resides in the CMAS compiling server.
  • IMSI International Mobile Subscriber Identity
  • HLR 800 On the "D" interface to determine if this subscriber, or roamer, can be serviced by the carrier. If the HLR 800 determines that the subscriber is serviceable, then it sends the VLR 795 the MSISDN information. The VLR then assigns the IMSI a TMSI and sends that information back to the HLR, (once again on the "D” interface) and to the subscriber handset and BSC, (on the "A" interface).
  • the BSC then sends the VLR, (on the "A" interface), the Cell-ID which is a unique number for each of the cellular towers within the carrier network, and the Location
  • LAC Area Code
  • VLR (on the "A" interface) the Cell-ID and LAC information regarding the TMSI back to the
  • the Cell-ID information is updated to the VLR every time the TMSI requests or receives service in the form of a voice call or SMS text message.
  • the LAC information is updated to the VLR, (on the "A" interface), every time the TMSI moves from one LAC to another. Also, the LAC and Cell-ID information is updated for every TSMI when the carrier network does a "refresh" which is typically performed every six hours. [0086] For the embodiment shown in FIG. 8, the compiling server 805 with associated Pseudo VLR 810, needs to keep track of the TMSI assigned to the MSISDN which is done by the passive monitoring of the "D" interface data.
  • the next important component is to keep track of the TMSI's relationship to the servicing Cell-ID which is accomplished by passively monitoring the data sent on the "A" interface which is provide to the compiling server 805. If the TMSI has been idle, (i.e., has not been sending or receiving service requests), for some period of time, (for example, 30 minutes), then the system shown in FIG. 8 will utilize the LAC data which is retrieved by passively monitoring the "A" interface.
  • a Web Portal Server 815 will send the compiling server 805 the Cell-IDs of the geographical defined alert area.
  • the compiling server 805 will query its Pseudo VLR 810 database of TMSI / Cell-ID information in order to determine which TMSIs should receive the alert message. If a TMSI has been idle for some period of time and the Cell-ID data is not current, then the TMSI will be included in the "batch" if the LAC it is operating in falls within the geographical-target area.
  • the compiling server 805 then sends the alert message and MSISDNs out on its own Short Message Service Center (SMSC) 820.
  • SMSC 820 Short Message Service Center
  • the message format and connection protocol from SMSC 820 to the carrier's MSC 790 will mirror the carrier's current SMSC 825/ MSC 790 interface.
  • the compiling server 805 could send the alert messages directly to the carrier's SMSC 825, once again mirroring the carrier's present day configurations.
  • FIG. 9 shows another alternative embodiment.
  • different handsets 770 are in communication with different cellular towers 775.
  • the handsets or other cellular devices are honing on a particular cellular tower 775 located within their service area.
  • the service towers 775 have a controlling switching platform located on the premises, called a base station 780.
  • Base stations 780 are hardwired to a Base Station Controller 785 by both voice and data circuits (Abis Interface(s)).
  • the Base Station Controller (BSC) 785 keeps track of the signal strength the handset is emitting to the receiving towers. As the signal strength decreases on the present servicing tower and increases on an adjacent tower, the Base Station Controller 785 handles the seamless handoff of the handset from one servicing tower to the next.
  • the Base Station Controllers 785 are connected to a Mobile Switching Center 790 by both voice and data channels ("A" Interface).
  • Mobile Switching Center, (MSC) 790 is the interconnect point for a cellular subscriber to reach other cell phones within the wireless carrier's network or any other wireless or landline device outside of the network.
  • the MSC 790 controls several Base Station Controllers 785 and thus multiple tower locations in a given area. As an example, in a metropolitan area, one MSC might control all of the towers servicing a forty square block area. As another example, the MSC servicing the northern section of Phoenix, AZ is also responsible for all of the towers in Flagstaff, AZ.
  • the MSC 790 has a Visitor Location Registry (VLR) database 795 that records in real time all of the updated movements of the servicing handsets through the "A-Interface" link from the BSCs 785.
  • VLR Visitor Location Registry
  • the MSC 790 also reports, (through the "D" Interface), to the off-premise Home Location Registry (HLR) 800 database to update that database that it is in control of a particular device.
  • HLR Home Location Registry
  • the HLR 800 houses all of the subscriber information pertinent to the consumer. This information includes billing name, address, cell plan and features associated with the subscribers account.
  • the MSC 790 recognizes a new device in its service area it informs the HLR 800.
  • This new device could, for example, be an existing subscriber who has transited from another servicing MSC, or an out of network device known as a "roamer".
  • This updated information to the HLR 800 is how the carrier's network knows which MSC 790 to route a voice call or text to a device when a service request comes in.
  • the VLR (Visitor Location Registry) 795 which resides within the MSC 790, houses the information regarding the mobile devices location.
  • the MSC 790 updates the VLR 795 with "real time" information as to what tower ID is currently servicing the handset.
  • the device As the device travels in and around the MSC's servicing area, it constantly updates the VLR 795 with current tower information so that incoming calls and/or data/texts can be routed appropriately.
  • a quick five minute trip to the airport might be serviced out of one MSC, but as you are in transit, you may be handed off to a multitude of different towers. Each hand off is updated in the VLR 795.
  • IMSI Subscriber Identity
  • HLR 800 Mobile Subscriber Integrated Services Digital
  • the VLR 795 assigns the IMSI a Temporary Mobile Subscriber Identity (TMSI) and sends that information back to the HLR 800, (once again on the "D” interface) and to the subscriber handset and BSC, (on the "A" interface).
  • TMSI Temporary Mobile Subscriber Identity
  • the BSC 785 then sends the VLR, (on the "A” interface), the Cell-ID which is a unique number for each of the cellular towers within the carrier network, and the Location Area Code (LAC) information which is a group of towers in a specific geographic area as defined by the wireless carrier for service paging purposes.
  • the BSC 785 sends the VLR (on the "A” interface) the Cell-ID and LAC information regarding the TMSI back to the VLR.
  • the Cell-ID information is updated to the VLR every time the TMSI requests or receives service in the form of a voice call or SMS text message.
  • the LAC information is updated to the VLR, (on the "A” interface), every time the TMSI moves from one LAC to another.
  • the LAC and Cell-ID information is updated for every TSMI when the carrier network does a "refresh" which is typically performed every six hours.
  • a Compiling Server 805 with associated Pseudo VLR 810 is provided.
  • the Compiling Server 805 and Pseduo VLR 810 needs to keep track of the TMSI assigned to the MSISDN which is done by the passive monitoring of the "D" interface data.
  • the next important component is to keep track of the TMSI's relationship to the servicing Cell-ID which is accomplished by passively monitoring the data sent on the "A" interface which is provide to the compiling server 805.
  • the system will utilize the LAC data which is retrieved by passively monitoring the "A" interface.
  • the passive monitoring of the essential data is performed by monitoring probes which are connected to the to the "A" and "D" interfaces. This data is transmitted to the Monitoring Filter 920 where it is parsed down to MSISDN, TMSI, Cell-ID and LAC and is transmitted onto the Compiling Server 805. All other non-essential data to the platform is filtered out.
  • a Web Portal Server 815 will send the compiling server 805 the Cell-IDs of the geographical defined alert area.
  • the compiling server 805 will query its Pseudo VLR 810 database of TMSI / Cell-ID information in order to determine which TMSIs should receive the alert message. If a TMSI has been idle for some period of time and the Cell-ID data is not current, then the TMSI will be included in the "batch" if the LAC it is operating in falls within the geographical-target area.
  • Those handset numbers 770 that are capable of an Internet interface are moved to the IP Gateway 900 and then the gateway "pings" those individual handsets 770 through the Public Internet 925 to determine if they are presently IP capable. If the ping response is positive, the number is marked for delivery in the 905 database and the alert message is sent to the individual handsets 770 from the IP Gateway 900 through the Public Internet 925. If the ping response is negative, the handset number is moved to the 910 side of the Real Time Delivery Database within the compiling server 805.
  • MSISDNs are sent out to the carrier's Short Message Service Center (SMSC) 825 for delivery to the intended recipients.
  • SMSC Short Message Service Center
  • the CMAS Throttling Gateway 915 continuously monitors the carrier's SMSC during the delivery event to ensure that the delivery process does not overwhelm the carrier network capacity.
  • An alternative method to utilizing the carrier SMSC 825 for alert message delivery is to implement a secondary SMSC 930 for the SMS alert message delivery.
  • a by product of the methodology for alert delivery according to the present embodiment is the abundance of data captured by the Monitoring Filter 920.
  • This data can supply other server platforms for the purpose of providing a variety of valuable services.
  • This services include such things as Lawful Intercept (CALEA), which is the ability for law enforcement, (through the issuance of a warrant), to track and record an individual's movements and voice / text conversations for immediate review or later analysis.
  • CALEA Lawful Intercept
  • Another service capability is the analysis of the network data to determine service outages or congestions during peak hours that might lead to subscriber complaints.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention se rapporte à un procédé et à un système qui permettent d'utiliser des dispositifs de communication et des réseaux sans fil existants, comme des téléphones cellulaires et des opérateurs de réseaux cellulaires par exemple, ainsi qu'une infrastructure sous-jacente, dans le but de fournir des informations d'urgence à un pourcentage ciblé d'une population située dans un endroit géographique spécifié. La fourniture desdites informations d'urgence se fait alors sans exiger des personnes ciblées qu'elles soient abonnées à un service d'alerte et sans utiliser des informations sollicitées par les destinataires ciblés de l'alerte ni des informations fournies par eux.
PCT/US2011/059547 2011-06-21 2011-11-07 Procédé et système d'alerte par messagerie cellulaire WO2012177279A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US2011041169 2011-06-21
USPCT/US2011/041169 2011-06-21

Publications (1)

Publication Number Publication Date
WO2012177279A1 true WO2012177279A1 (fr) 2012-12-27

Family

ID=47422864

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2011/059547 WO2012177279A1 (fr) 2011-06-21 2011-11-07 Procédé et système d'alerte par messagerie cellulaire

Country Status (1)

Country Link
WO (1) WO2012177279A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2906003A1 (fr) * 2014-02-10 2015-08-12 Telefonaktiebolaget L M Ericsson (publ) Pagination d'un dispositif sans fil utilisant un identificateur de cellule radio
CN113079544A (zh) * 2020-01-06 2021-07-06 深圳市嘉盈资讯有限公司 一种运营商基站下发送信息的方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070066366A1 (en) * 2005-09-16 2007-03-22 Katherine Graham Method and system for implementing an emergency alert receiver system in a cellular phone
US7617287B2 (en) * 2002-11-27 2009-11-10 Rga Intl, Inc. Cellular messaging alert method and system
US7743052B2 (en) * 2006-02-14 2010-06-22 International Business Machines Corporation Method and apparatus for projecting the effect of maintaining an auxiliary database structure for use in executing database queries

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7617287B2 (en) * 2002-11-27 2009-11-10 Rga Intl, Inc. Cellular messaging alert method and system
US20070066366A1 (en) * 2005-09-16 2007-03-22 Katherine Graham Method and system for implementing an emergency alert receiver system in a cellular phone
US7743052B2 (en) * 2006-02-14 2010-06-22 International Business Machines Corporation Method and apparatus for projecting the effect of maintaining an auxiliary database structure for use in executing database queries

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2906003A1 (fr) * 2014-02-10 2015-08-12 Telefonaktiebolaget L M Ericsson (publ) Pagination d'un dispositif sans fil utilisant un identificateur de cellule radio
US9467901B2 (en) 2014-02-10 2016-10-11 Telefonaktiebolaget L M Ericsson (Publ) Paging a wireless device using a radio cell identifier
CN113079544A (zh) * 2020-01-06 2021-07-06 深圳市嘉盈资讯有限公司 一种运营商基站下发送信息的方法及系统
CN113079544B (zh) * 2020-01-06 2022-06-21 深圳市嘉盈资讯有限公司 一种运营商基站下发送信息的方法及系统

Similar Documents

Publication Publication Date Title
CA2430344C (fr) Methode et systeme d'alerte de message cellulaire
US8494489B2 (en) Wireless user based notification system
EP2124493B1 (fr) Procédé de ciblage géographique des alertes d'urgence sans fil
US7133685B2 (en) Monitoring boundary crossings in a wireless network
US20070159322A1 (en) Location, tracking and alerting apparatus and method
US20040193617A1 (en) Geographically specific advisory alert broadcasting system
US9569961B2 (en) System and method for using cellular network components to derive traffic information
US20070202927A1 (en) Automated search and rescue call generation to mobile phones in a defined geographic disaster area
WO2006036807A2 (fr) Systeme de traitement d'appel d'urgence
CN101861726B (zh) 紧急信息发布系统、紧急信息发布方法、发送服务器以及便携终端
WO2012048383A1 (fr) Procédé et appareil pour système de communication et d'alerte
TWI420426B (zh) Multidimensional emergency messaging system
US8285694B1 (en) Distribution of enterprise related alerts via the emergency alert system
US9769781B2 (en) System and method for providing multi-carrier tracking of wireless devices during an emergency
Aloudat et al. Location-based services in emergency management-from government to citizens: Global case studies
CN111479221A (zh) 移动发起的sms小区广播
WO2012177279A1 (fr) Procédé et système d'alerte par messagerie cellulaire
CN111480352B (zh) 用于lte网络基于边缘的特定于位置的警报系统
US20110298611A1 (en) Apparatus and Method for an Alert Notification System
Aziz et al. Cooperative flood detection using GSMD via SMS
AU2010251874A1 (en) System and method for tracking events
CN102104828A (zh) 分散式终端信令监测实现定位鉴权的系统和方法
KR20160006899A (ko) 재난 어플리케이션을 이용한 재난 메시지 전송 방법 및 시스템
Udu-gama Implementing Inclusive ICTs: Mobile Cell Broadcasting for a Public Warning System in the Maldives
CN102655457A (zh) 公共服务消息广播系统和方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11868157

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11868157

Country of ref document: EP

Kind code of ref document: A1