US20080162667A1 - Method and system for rapid dissemination of public announcements - Google Patents

Method and system for rapid dissemination of public announcements Download PDF

Info

Publication number
US20080162667A1
US20080162667A1 US12/048,316 US4831608A US2008162667A1 US 20080162667 A1 US20080162667 A1 US 20080162667A1 US 4831608 A US4831608 A US 4831608A US 2008162667 A1 US2008162667 A1 US 2008162667A1
Authority
US
United States
Prior art keywords
announcement
user
network
system
internet
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
Application number
US12/048,316
Inventor
Dinesh Chandra Verma
Paridhi Verma
Original Assignee
Dinesh Chandra Verma
Paridhi Verma
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
Priority to US11/077,146 priority Critical patent/US7529850B2/en
Application filed by Dinesh Chandra Verma, Paridhi Verma filed Critical Dinesh Chandra Verma
Priority to US12/048,316 priority patent/US20080162667A1/en
Publication of US20080162667A1 publication Critical patent/US20080162667A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B27/00Alarm systems in which the alarm condition is signalled from a central station to a plurality of substations
    • G08B27/005Alarm systems in which the alarm condition is signalled from a central station to a plurality of substations with transmission via computer network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12783Arrangements for addressing and naming in data networks involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address, functional addressing, i.e. assigning an address to a function
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/35Network arrangements or network protocols for addressing or naming involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/02Network-specific arrangements or communication protocols supporting networked applications involving the use of web-based technology, e.g. hyper text transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/18Network-specific arrangements or communication protocols supporting networked applications in which the network application is adapted for the location of the user terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information

Abstract

The present invention provides a method and system for disseminating urgent public announcements over an IP-based network. One or a plurality of Internet- or Intranet-connected servers receive and store data identifying particular geographic locations to current announcements. The servers identify IP addresses of users making URL requests or requests for target applications (an access point by which a network-connectable mobile device is connected to an Internet- or Intranet-connected server), determine a location for each user from the user's IP address (or access point), and determine whether an IP address (or access point) of a user corresponds to a location for which an announcement has been posted. If the user is identified to a location for which a current announcement is available, the announcement is displayed to the user.
The announcement may be displayed by redirecting the user to a web page containing the announcement. Alternatively, the announcement may be displayed in a pop-up window or in a banner on a web page requested by said user. A banner displaying such an announcement may incorporate a link to permit the user to click through to a web page containing a more detailed version of the announcement.

Description

    BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • The present invention generally relates to the dissemination of public announcements and, more particularly, to the rapid dissemination of urgent public announcements using client computers connected to a network, including an Internet Protocol-based network such as the Internet or a private Intranet.
  • 2. Background Description
  • The Emergency Broadcast System is a well-established means for rapid dissemination of urgent public announcements by interrupting regularly scheduled programming on traditional broadcast communications media such as radio and television. Traditional broadcast communications media are well suited for the rapid dissemination of urgent public announcements because the systems employed by such media are characterized by a large number of user terminals (such as radios or television sets) in a concentrated geographic area, which are configured to receive a continuous stream of a relatively limited selection of information content (such as entertainment) from a relatively limited number of transmitters (such as local television or radio stations). In addition, the continuously streaming nature of radio and television means that program interruptions may have an immediate impact on the information content being displayed by a user terminal. Thus, a large number of persons in a given geographic area may be reached almost immediately by interrupting a relatively small amount of television or radio programming.
  • Increasingly, however, people are spending time using the Internet instead of listening to radio or watching television. As of October, 2004, approximately two-thirds of the U.S. population regularly used the Internet, and the time devoted by average Internet user to the Internet was approximately 1.7 times as much as the time devoted by the average Internet user to watching television.
  • As radio and television increasingly lose audience to the Internet, communities are experiencing a decline in the number of people who can be reached at any given moment by interrupting regularly scheduled radio or television programming.
  • Communities are not currently able to disseminate urgent public announcements to persons while they are engaged in operating user terminals to access the Internet, unless there is a radio or television set turned on in the background. Thus, there is an unfilled need for a capability to disseminate urgent public announcements through the Internet, in addition to using conventional radio and television.
  • Technical differences between the Internet and conventional broadcast media have made it difficult or impossible to establish an Internet equivalent of the Emergency Broadcast System. For example, as noted, radio and television are characterized by a relatively limited number of centralized transmitters broadcasting a continuous stream of a relatively limited selection of entertainment and other information content to a relatively large number of user terminals in a relatively concentrated geographic area.
  • Unlike radio and television, the Internet is characterized by a relatively large number of geographically dispersed servers providing information content to a relatively small number of user terminals per server, with little or no attention paid to the users' geographic location. Such differences between the Internet and conventional radio or television have made it difficult or impossible to implement an Internet equivalent of the Emergency Broadcast System prior to the present invention.
  • Existing art systems for making announcements over the Internet consist of either (a) posting announcements on a web site, thus requiring a user proactively to access the web site to look for urgent announcements; (b) sending announcements by email, thus requiring users to access their email before becoming aware of an announcement requiring their attention; or (c) including announcements in an XML-based Rich Site Summary (RSS) feed, thus requiring users to install specialized RSS software on their browsers, to have the software configured to provide new feeds promptly, and to subscribe to an RSS service used to disseminate the announcement in question. Current RSS feeds use insecure communication channels.
  • SUMMARY OF THE INVENTION
  • It is therefore an object of the present invention to provide a method and system for rapid dissemination of urgent public announcements to persons who are occupied by accessing the Internet using client-side software such as a browser.
  • It is a further object of the present invention to provide such a method and system to Internet users who do not have an open and available email client and an appropriately configured RSS feed, and to do so requiring users proactively to access a web site to see if there are any urgent announcements requiring the user's attention.
  • It is a further object of the present invention to provide such a method and system to users of cell phones and Internet users connected to network providers using mobile wireless broadband connections.
  • It is a further object of the present invention to provide such a method and system to drivers in cars and other transportation vehicles who have services dependent on Geographical Position Sensing (GPS) technology within their vehicles.
  • According to the invention, there may be various approaches to implementing an Internet Emergency Alert System (IEAS), all of which depend on the ability to identify Internet users by geographic location. That ability is conventionally available. For example, the Internet Protocol (IP) addresses of Internet users—which are provided to web sites to enable a requested web page to be loaded on the user terminal of a requesting user—can be used to identify Internet users' geographic locations. This is conventionally done through the use of commercially available databases developed to enable web sites to map users' IP addresses to their geographic locations. Given the current state of the art for mapping IP addresses to localities, therefore, it is possible to identify the locations of Internet users for the purpose of giving customized emergency alerts to users in specific localities.
  • The Internet is only sometimes employed in modes that involve the continuous streaming of data in the manner of radio or television programming, which may be instantly interrupted by an emergency announcement. Nevertheless, web pages tend to be refreshed frequently, and Internet users typically move relatively quickly from one universal resource locator (URL) to another. As a result, the normal mode of Internet use affords ready opportunity to provide users with urgent public announcements as discussed below.
  • One approach to implementing the present invention may be employed where an IEAS service controls or has the cooperation of a proxy that provides service for an audience of target users. Such proxies may include Internet service providers, which necessarily control their subscribers' Internet access, and they may also include private Intranets. While Internet service providers and private Intranets may have ready access to users' geographic locations, other possible proxy sites may determine geographic location from users' IP addresses as discussed above. In either case, the geographic location of a user may be cross-referenced to a list of posted local alerts. Having identified a user as being within a geographic location for which an IEAS alert has been posted, the proxy may then redirect a URL request (or a request for a target application) from such a user's browser to a public alert site displaying an urgent public announcement for the user's geographic location. Users whose geographic locations are not associated with a public alert would not have their browsers redirected but would instead access the URL (or target application) as originally requested. Proxies may be implemented in a transparent manner. An Internet service provider may configure the routers, switches or other devices at its points of access so that they redirect all network communications from customers subject to an IEAS site when there is an emergency in the geographic location.
  • Another approach may be used when control of a proxy site is not available, or to communicate with users who are not served by a proxy site that is cooperating with the IEAS service. To reach such users, an IEAS service may enlist the participation of popular web sites to obtain access to relatively small areas on their web pages for use as alert areas in disseminating public alerts. An alert area could be a banner, among other configurations. Alternatively, the alert area could take the form of a pop-up window. A cooperating web site could employ conventional means to identify the geographic location of a user accessing the web site's URL through a browser. If the user's geographic location corresponds to a geographic location for which a public alert has been posted, the participating web site would then display an urgent public announcement in the alert area previously set up for that purpose. Such a public alert could include a hyperlink to enable users to click through to a public alert web page, which may be the same web page to which proxy servers are redirecting users according to the first approach to an IEAS service, as discussed above.
  • The proxy based approach can be used for disseminating broadcast information to users of cell-phone services or the users of mobile broadband users within a geographical area. All cell phones operate by connecting to an access point or a tower in their geographical location. The access point can intercept the calls made by cell phones from a location affected by an emergency.
  • In the case of users identified to geographic locations for which no public alert has been posted, the space on the web page reserved for use as an alert area could be employed by the participating web site for other purposes (including, but not limited to, the display of advertising) when such users access the site.
  • An IEAS service may employ both approaches, with proxies redirecting users in a selected geographic location to an IEAS public alert web page, while cooperating web sites provide banner public alert messages to users in the selected geographic location, potentially including a link to enable users to click through to an IEAS public alert web page. Users of the Internet can also use the web site to provide feedback and update to emergency officials, e.g. a person whose only exit route has been cut off by an emergency may notify officials to make alternate rescue arrangements.
  • A structured format may be employed for creating public alert messages, and electronic forms may be provided to enable authorized users to input alerts. Such forms may contain a relatively simple structured format for alert messages, including such categories as severity of alerts, text message to display, time of issuance of alert, and time of expiration of alert. The severity of alerts could be signaled by the use of distinct background colors on the IEAS public alert web page according to an established coding system (e.g., red, orange, yellow, etc.).
  • An IEAS service may simultaneously disseminate separate public alerts for different communities, distributing new alerts to participating proxies and web sites. Depending on the population of areas to which public alerts relate, a large number of users say millions of users may simultaneously seek access to one or more IEAS public alert web pages. An IEAS public alert web site must therefore be capable of handling a large number of users.
  • Various techniques are available for handling the peak load requirements of an IEAS service, including but not limited to the use of a series of distributed sites for IEAS servers and the use of geographic load-balancing techniques. A content delivery network (CDN) service, with appropriate extensions for security, could be employed to enable public alert data to be cached throughout an edge network maintained by the CDN service. Such duplication of content throughout the Internet would facilitate the handling of peak loads and provide users with quicker access than if the data were to reside exclusively on a single server.
  • Hackers, pranksters, and even terrorists may try to subvert an IEAS service by creating and posting falsified alerts, which may cause immediate panic and, over a longer term, may tend to undermine public confidence and trust in the IEAS service. IEAS public alert web sites are therefore likely to implement security measures in order to maintain public confidence and trust. One such measure is the use of Secure Socket Layer (SSL) or Transport Layer Security) TLS protocols to assure secure access to the IEAS service.
  • While browsers may appear to be the most suitable means for users to receive an IEAS public alert, other client-side software (including, but not limited to, plug-ins and extensions for browsers) may be used which would allow clients to input or store IEAS alert preferences, to provide more granular geographic location data about a user, or to identify additional geographic locations for which a user wants to receive alerts. Such client-side software applications may include text messaging applications, mobile browsers, or other software running on a mobile Internet-capable device such as a cell phone or personal digital assistant. Such additional client-side software may also permit more effective filtering of alert messages according to their relevance to the user.
  • The present invention may also be used within an enterprise computing environment to provide alerts to users of an Intranet. While enterprises may already use Intranets to disseminate some announcements, there is an increasing need for enterprises to limit the dissemination of some announcements to, for example, workers located in a particular facility. Enterprises are increasingly dispersed geographically, and an increasing number of workers are working remotely from their homes or other locations. A conventional audio public address system, while effective for notifying persons within a specific building, cannot reach workers outside the building. Thus, an Intranet-based implementation of the present invention may enable enterprises to disseminate announcements more effectively.
  • An enterprise-based or Intranet implementation of the present invention may also enable an enterprise system to serve as an IEAS proxy for the purpose of disseminating IEAS public alerts to workers located within affected localities, according to the present invention.
  • Thus, the present invention provides a system and a method for disseminating announcements over an IP-based network, wherein there is one or a plurality of Internet- or Intranet-connected servers which: (a) receive and store data identifying particular locations to current announcements; (b) identify either (i) IP addresses of users making requests, for either a URL or a target application, to an Internet- or Intranet-connected server or (ii) an access point by which a network-connectable mobile device, including, but not limited to, a cellular telephone (cell phone) or personal digital assistant (PDA), is connected to an Internet- or Intranet-connected sever; (c) determine a location for each of said users from either said IP addresses or said access point; (d) determine whether an IP address or an access point of a user is an IP address or an access point corresponding to a location for which an announcement has been posted; and (e) display said announcement to said user. The announcement may be displayed to the user by redirecting the user to a web page containing said announcement. The announcement may also be displayed in a pop-up window. Alternatively, the announcement may be displayed to the user in a banner on a web page requested by the user. Said banner may incorporate a link to permit the user to click through to a web page containing a more detailed version of the announcement displayed in the banner. The link and the corresponding web site may be used to provide information by general public relating to the emergency to officers responding to the emergency. As noted, user's location may also be determined from an access point to which a network-connectable mobile device, including, but not limited to, a cell phone or PDA, employed by the user is connected to the network, instead of from the user's IP address. In some mobile applications, an alert announcement may be provided in a combined audio-visual or in an audio-only format. Finally, a router may be employed to identify IP addresses of users making requests (for either a URL or a target application) to an Internet-connected server.
  • The present invention further provides a network-based warning or public announcement system comprising: (a) a plurality of servers that are selectively connectable to a plurality of clients, each of said plurality of clients capable of providing at least one of said plurality of servers with an IP address, said plurality of servers being connected by a network; (b) one or more tables which correlate location information for one or more of said plurality of clients with said IP address; and (c) a source of a warning or public announcement which electronically provides a warning or public announcement to at least a portion of said plurality of client, without action being taken by said portion of said plurality of clients, using at least a portion of said plurality servers and at least one of said one or more tables based on said location information. The warning or public announcement electronically provided by said source in said network-based warning or public announcement system may cause at least one of a visual, textual or audible signal to be reproduced at least one client of said plurality of clients. In addition, said one or more tables and said plurality of servers in said warning or public announcement system may function to transmit said warning or public announcement only to a select portion of said plurality of clients based on said location information. The network address employed in said network-based warning or public announcement system may be the IP address of said client. Alternatively, said network address may be the GPS coordinate of said client or the identity of an access point to which said client is identified. The client may be a personal computer or other conventional computing device, or it may be a network-connectable mobile device, including, but not limited to, a cell phone or PDA.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The foregoing and other objects, aspects and advantages will be better understood from the following detailed description of a preferred embodiment of the invention with reference to the drawings, in which:
  • FIG. 1 is a representation of an IP-based network configured for disseminating public announcements.
  • FIG. 2 is a representation of an IP-based network configured for disseminating public announcements in which an announcement is displayed by redirecting the user to a web page containing the announcement.
  • FIG. 3 is a representation of an IP-based network configured for disseminating public announcements in which a proxy redirects the user to a web page containing the announcement.
  • FIG. 4 is a representation of a public announcement displayed on an IP client.
  • FIG. 5 is a representation of an IP based network configured for disseminating public information in which a router acts as a transparent proxy to redirect the user to a web-page containing the announcement.
  • FIG. 6 is a representation of the apparatus required at the IEAS server for the purpose of disseminating public information to users on the Internet.
  • FIG. 7 is a representation of a mobile network configured for disseminating public information in which an access point acts as a means for providing the user public announcements.
  • DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT OF THE INVENTION
  • Referring now to the drawings, and more particularly to FIG. 1, there is shown a user 11 employing a user terminal to access a web site on an Internet-connected server 12 which has received and stored an alert table 13 provided by an Internet Emergency Alert System (IEAS) server 14, which identifies current public announcements and particular geographic locations to which they relate. In step 100, the Internet Emergency Alert System Server 14 updates and maintains the information stored in the alert table 13. When the user 11 access the Internet-connected server 12 in step 101, the Internet-connected server 12 provides an appropriate alert in step 102. The alert provided in step 102 is based on the data in the alert table 13. FIG. 1 provides an overview of the overall operation of the system.
  • Referring to FIG. 2, a user makes a request to a target web site in step 21. The target web site then consults an IEAS server in step 22. The IEAS server has previously received alert data from a IEAS source in step 29. An IEAS source could be a Government official or other entity who is authorized to issue alerts to the geographical population at large. Based on this alert data and a database of IP address data or other user location data, the IEAS server determines whether any public alert relevant to the user and/or the target web site is in place and then communicates that determination, along with any public alert, to the target web site in step 23. Based on the data received from the IEAS server, the target web site provides the user with a response which either does or does not include a public alert announcement, as appropriate, in step 24.
  • FIG. 2 provides an embodiment of the Internet emergency alert system when the alert is provided by means of agreements among several web sites and an IEAS server. Variants of the above embodiment can be developed using the state of the art technology in caching and content distribution. The alert information from the IEAS server can be cached at the target web site, so that the target web site need not access IEAS on every user interaction. State of the art caching algorithms may be used to maintain the alert table at the target web site current.
  • Referring to FIG. 3, a user makes a request to a proxy in step 31. The proxy then consults a IEAS server in step 32. The IEAS server has previously received alert data from a IEAS source in step 39. Based on this alert data and a database of IP address data or other user location data, the IEAS server determines whether any public alert relevant to the user and/or the target web site is in place and then communicates that determination, along with any relevant public alert, to the proxy in step 33. If there is no alert relevant to the user, the proxy passes the user's request to the target web set in step 34 and then receives a response from the target web site in step 35, which is passed on to the user in step 36. However, if there is an alert relevant to the user, the proxy skips steps 34 and 35 and provides the user with the applicable public alert received from the PA site, instead of accessing the target web site as requested by the user, in step 36.
  • FIG. 3 provides an embodiment which can be readily used by Internet Service Providers and enterprises which operate proxy servers to improve, control, or otherwise influence their users or employees connect to the Internet. Proxies are used in the current state of the art for a variety of TCP/IP based applications, including web-proxies, file transfer proxies, mail-proxies, etc. Variants of the embodiment described above can also be used. One possible variant would be for the proxy to combine the alert information obtained in step 33 with the response from target web site obtained in step 35 and present the combination to the user, instead of presenting only the alert information. One possible way to combine alert information for web-proxies is to display the alert in a special header or banner area of a web-page.
  • FIG. 4 shows a public alert that may be displayed to a user. The alert notification may have a color code 41 based on severity of the emergency, a alert header 42 displayed prominently in large font, a brief description 43 that provides a concise overview of the alert conditions, an instruction 44 that provides information on actions to be taken by the user, a URL 45 that can be used to access more details about the alert condition, an identification of the location 46 where alerts are to be displayed, the date 47 and the time 48 of the notification. Furthermore, various language preferences may be implemented, and the size of window may be adjusted (full screen, half screen, etc.) based on severity of the emergency or other factors. The above description of an alert is intended to be exemplary, and different embodiments may include additional fields, and display the fields in a different manner.
  • FIG. 5 shows an alternative embodiment of the invention in which the generation of alerts is done by means of an IP router. As compared to the embodiment shown in FIG. 3, this embodiment does not require the presence of a proxy server in the network. A router is a device that forwards IP packets in the network, and current TCP/IP networks deploy several routers for their operation. In the ordinary course of operation, a user 501 accesses a target application 502. The access is conducted by means of exchanging several IP packets which are transmitted among the user 501 and the target 502 through a set of routers. One of the routers 503 can be modified to implement support for displaying alerts to the user. During normal operation, the user 501 generates IP packets and sends them within the network in step 51. When the router 503 receives these packets, it relays them to the target application 502 in step 52. A set of response IP packets may be generated by target application 502 in step 53, and the router 503 forwards these packets to the user application 501 in step 54. However, when there is a need for emergency information to be disseminated, the forwarding process of IP Packets is modified by the router. A source for Internet Emergency alert service (IEAS Source 504) could be a Government official or otherwise authorized entity which is allowed to provide notification for emergency alert. In step 56, the IEAS source 504 informs an IEAS server 505 of an emergency which needs to be disseminated. The IEAS server 505 then modifies the configuration or router 503 in step 57. The router 503 will then forward packets in the emergency alert mode. In this mode, when the user 501 sends a packet intended for the target application 502 in step 581, the router 503 forwards that packet to the IEAS server 505. in step 582 The IEAS server 505 responds with a set of packets in step 583, which are forwarded by the router 503 over to the user 501 in step 584. These packets carry the information required to display the alert system.
  • The router 503 can be augmented with state of the art efficiency mechanisms for the redirection of packets described in FIG. 5. Thus, router 503 may be designed to only forward a subset of packets (e.g. those initiating a connection or carrying the SYN flag in the TCP protocol, or packets which run on TCP/IP port 80 or some other subset of packets). If the router 503 is forwarding packets from multiple users, and only a subset of users is affected by an emergency alert, then the router 503 may only forward the packets originating from that subset of users. The embodiment shown in FIG. 5 can be used in mobile broadband access networks deploying communication technologies such as 802.16 and 802.20 where the router 503 is located at the access points of the service providers offering mobile broadband IP access. In other variations of this embodiment, router 503 may only be present in the path of packets sent from user 501 to target application 503, but need not be present in the reverse path of packets sent from the target application 503 to user 501. In these cases, the IEAS server 505 may send packets to the user 501 through other set of routers in step 583, and step 584 may be eliminated.
  • FIG. 6 shows the structure of the software apparatus needed at the IEAS server described in previous figures. The IEAS server consists of an access protocol module 601, a geographical location mapping module 602, an alert table module 603, a alert processor 604, and a alert creation module 605. The access protocol module 601 is responsible for processing the protocol required by users to access the IEAS server, and for authorized personnel and IEAS sources to create new types of alerts. The access protocol module 601 provides the IP address of a user accessing the server to the geographical location mapping module 602. IP addresses are unique numbers assigned to computers using the TCP/IP protocols. An example of an IP address is 9.2.22.89. The geographical location mapping module 602 is responsible for mapping the IP address of the user to a geographical locality. An example of geographic locality would be “New York” or “Buffalo, N.Y.”. The geographical location of the user is provided by the geographical location mapping module to the alert table module 603. The alert table module 603 contains a table mapping the geographical location to a set of active alerts. The alert table module 603 provides the active alert to the alert processor 604, which converts this into an alert message passed back to the protocol module 601 for transmitting back to the user.
  • The protocol module 601 also provides new alerts that may originate from an authorized IEAS source to the alert creation module 605. The alert creation module 605 is responsible for obtaining and storing entries from the alter table contained in alert module 603.
  • In other embodiments, properties different than IP addresses can be used to map users to specific localities, e.g. user specified preferences can be used in addition to the IP addresses to determine the geographic location of a user, or Global Positioning System (GPS) coordinates may be used to determine the geographic location of a user. The address of a network attached device, e.g. an access point for wireless communication, can also be used to determine the geographic location of a user.
  • FIG. 7 shows an embodiment of this invention when used by a cellular mobile phone operator to provide emergency broadcast notifications to all cell-phone subscribers who are within a specific geographical region. The users of a cellular mobile phone operator or the Internet users of a mobile broadband access provider would connect to the cellular telephone (cell phone) network, or the Internet by means of an access point. As shown in FIG. 7, the user of a cell phone 701 is associated at a given time with a cell phone access tower 703. The cell phone 701 will associate with the cell phone access tower 703 when it comes within its geographic vicinity by communicating with it in step 71. The cell phone access tower 703 may have more than one cell phone associated with it. The cell phone access tower 703 is informed on an emergency situation by the IEAS server 704, such information occurring in step 72. The cell phone access tower 703 can notify the user 701 of the emergency situation by initiating a phone call to the user 701 in step 73. If the user 701 is currently engaged in a cell-phone conversation with another user, the cell phone access tower 703 may interrupt the phone conversation in step 73 to inform the user 701 of the emergency.
  • The embodiment shown in FIG. 7 can also be used to provide emergency notification to drivers of automobiles or other vehicles that are equipped with GPS (Global Position System) devices and subscribe to vehicle emergency services, including, but not limited to, services provided by OnStar® (a registered service mark of General Motors Corporation). In these cases, the role of the access tower 703 is performed by the controller system of the OnStar® service which maps the GPS location of a vehicle to determine if an emergency alert is applicable to the area in which the vehicle is located. Announcements relating to road conditions and/or hazards could be disseminated to users whose locations and/or network-connection types would suggest that they are (or are likely to be) driving (or riding in) automobiles. As noted above, in some mobile applications, an alert announcement may be provided in a combined audio-visual or in an audio-only format.
  • While the invention has been described in terms of a single preferred embodiment, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the appended claims.

Claims (18)

1. A method for disseminating public announcements over an IP-based network, wherein there is
one or a plurality of Internet- or Intranet-connected servers performing the steps of:
receiving and storing data identifying current announcements and particular locations to which they relate;
identifying either
IP addresses of users making requests, for either a URL or a target application, to an Internet- or Intranet-connected server, or
an access point by which a network-connectable mobile device is connected to an Internet- or Intranet-connected server;
determining a location for each of said users from either said IP addresses or said access point;
determining whether an IP address or an access point of a user is an IP address or an access point corresponding to a location for which an announcement has been posted; and
displaying said announcement to said user.
2. The method of claim 1, wherein said announcement is displayed to said user by redirecting the user to a web page containing said announcement.
3. The system of claim 1, wherein said announcement is displayed in a pop-up window.
4. The system of claim 1, wherein said announcement is displayed to said user in a banner on a web page requested by said user.
5. The system of claim 4, wherein said banner incorporates a link to permit said user to click through to a web page containing a more detailed version of the announcement displayed in the banner.
6. The method of claim 1, further comprising the step of using a router to identify IP addresses or access points of users making requests to an Internet or Intranet-connected server.
7. A system for disseminating public announcements over an IP-based network, comprised of
one or a plurality of Internet- or Intranet-connected servers with:
means to receive and store data identifying current announcements and particular locations to which they relate;
means to identify either
IP addresses of users making requests, for either a URL or a target application, to an Internet- or Intranet-connected server, or
an access point to which a network-connectable mobile device is connected to an Internet- or Intranet-connectable server;
means to determine a location for each of said users from said IP addresses or said access point;
means to determine whether an IP address or an access point of a user is an IP address or an access point corresponding to a location for which an announcement has been posted; and
means to display said announcement to said user.
8. The system of claim 7, wherein said means to display said announcement redirects the user to a web page containing said announcement.
9. The system of claim 7, wherein said means to display said announcement comprises a pop-up window.
10. The system of claim 7, wherein said means to display said announcement displays said announcement in a banner on a web page requested by said user.
11. The system of claim 10, wherein said banner incorporates a link to permit said user to click through to a web page containing a more detailed version of the announcement displayed in the banner.
12. The system of claim 7, further comprising a router employed to identify IP addresses or access points of users making requests to an Internet- or Intranet-connected server.
13. A network-based warning or public announcement system, comprising:
a plurality of servers that are selectively connectable to a plurality of clients, each of said plurality of clients capable of providing at least one of said plurality of servers with a network address, said plurality of servers being connected by a network;
one or more tables which correlate location information for one or more of said plurality of clients with said network address; and
a source of a warning or public announcement which electronically provides a warning or public announcement to at least a portion of said plurality of clients, without action being taken by said portion of said plurality of clients, using at least a portion of said plurality of servers and at least one of said one or more tables based on said location information.
14. The network-based warning or public announcement system of claim 13, wherein said warning or public announcement electronically provided by said source causes at least one of a visual, textual or audible signal to be reproduced at at least one client of said plurality of clients.
15. The network-based warning or public announcement system of claim 13, wherein said one or more tables and said plurality of servers function to transmit said warning or public announcement only to a select portion of said plurality of clients based on said location information.
16. The network-based warning or public announcement system of claim 13, wherein said network address is an IP address of said client.
17. The network-based warning or public announcement system of claim 13, wherein said network address is a GPS coordinate of said client.
18. The network-based warning or public announcement system of claim 13, wherein said network address is the identity of an access point to which said client is identified.
US12/048,316 2005-03-11 2008-03-14 Method and system for rapid dissemination of public announcements Abandoned US20080162667A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US11/077,146 US7529850B2 (en) 2005-03-11 2005-03-11 Method and system for rapid dissemination of public announcements
US12/048,316 US20080162667A1 (en) 2005-03-11 2008-03-14 Method and system for rapid dissemination of public announcements

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12/048,316 US20080162667A1 (en) 2005-03-11 2008-03-14 Method and system for rapid dissemination of public announcements

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/077,146 Continuation US7529850B2 (en) 2005-03-11 2005-03-11 Method and system for rapid dissemination of public announcements

Publications (1)

Publication Number Publication Date
US20080162667A1 true US20080162667A1 (en) 2008-07-03

Family

ID=36972311

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/077,146 Expired - Fee Related US7529850B2 (en) 2005-03-11 2005-03-11 Method and system for rapid dissemination of public announcements
US12/048,316 Abandoned US20080162667A1 (en) 2005-03-11 2008-03-14 Method and system for rapid dissemination of public announcements

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/077,146 Expired - Fee Related US7529850B2 (en) 2005-03-11 2005-03-11 Method and system for rapid dissemination of public announcements

Country Status (1)

Country Link
US (2) US7529850B2 (en)

Cited By (71)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090163170A1 (en) * 2007-12-21 2009-06-25 Koninklijke Kpn N.V. Emergency system and method
US20090248786A1 (en) * 2008-03-31 2009-10-01 Richardson David R Request routing based on class
US20100146541A1 (en) * 2008-12-08 2010-06-10 At&T Intellectual Property I, L.P. Emergency Alert Representation
US7970820B1 (en) 2008-03-31 2011-06-28 Amazon Technologies, Inc. Locality based content distribution
US7991910B2 (en) * 2008-11-17 2011-08-02 Amazon Technologies, Inc. Updating routing information based on client location
US8028090B2 (en) 2008-11-17 2011-09-27 Amazon Technologies, Inc. Request routing utilizing client location information
US8060616B1 (en) 2008-11-17 2011-11-15 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US8065417B1 (en) 2008-11-17 2011-11-22 Amazon Technologies, Inc. Service provider registration by a content broker
US8073940B1 (en) 2008-11-17 2011-12-06 Amazon Technologies, Inc. Managing content delivery network service providers
US8122098B1 (en) 2008-11-17 2012-02-21 Amazon Technologies, Inc. Managing content delivery network service providers by a content broker
US8156243B2 (en) 2008-03-31 2012-04-10 Amazon Technologies, Inc. Request routing
US8239571B2 (en) 2008-06-30 2012-08-07 Amazon Technologies, Inc. Request routing using network computing components
US8321568B2 (en) 2008-03-31 2012-11-27 Amazon Technologies, Inc. Content management
US8397073B1 (en) 2009-09-04 2013-03-12 Amazon Technologies, Inc. Managing secure content in a content delivery network
US8412823B1 (en) 2009-03-27 2013-04-02 Amazon Technologies, Inc. Managing tracking information entries in resource cache components
US8447831B1 (en) 2008-03-31 2013-05-21 Amazon Technologies, Inc. Incentive driven content delivery
US8452874B2 (en) 2010-11-22 2013-05-28 Amazon Technologies, Inc. Request routing processing
US8463877B1 (en) 2009-03-27 2013-06-11 Amazon Technologies, Inc. Dynamically translating resource identifiers for request routing using popularitiy information
US8468247B1 (en) 2010-09-28 2013-06-18 Amazon Technologies, Inc. Point of presence management in request routing
US8521851B1 (en) 2009-03-27 2013-08-27 Amazon Technologies, Inc. DNS query processing using resource identifiers specifying an application broker
US8533293B1 (en) 2008-03-31 2013-09-10 Amazon Technologies, Inc. Client side cache management
US8543702B1 (en) 2009-06-16 2013-09-24 Amazon Technologies, Inc. Managing resources using resource expiration data
US8577992B1 (en) 2010-09-28 2013-11-05 Amazon Technologies, Inc. Request routing management based on network components
US8601090B1 (en) 2008-03-31 2013-12-03 Amazon Technologies, Inc. Network resource identification
US8606996B2 (en) 2008-03-31 2013-12-10 Amazon Technologies, Inc. Cache optimization
US8626950B1 (en) 2010-12-03 2014-01-07 Amazon Technologies, Inc. Request routing processing
US8732309B1 (en) 2008-11-17 2014-05-20 Amazon Technologies, Inc. Request routing utilizing cost information
US8756341B1 (en) 2009-03-27 2014-06-17 Amazon Technologies, Inc. Request routing utilizing popularity information
US8819283B2 (en) 2010-09-28 2014-08-26 Amazon Technologies, Inc. Request routing in a networked environment
US8924528B1 (en) 2010-09-28 2014-12-30 Amazon Technologies, Inc. Latency measurement in resource requests
US8930513B1 (en) 2010-09-28 2015-01-06 Amazon Technologies, Inc. Latency measurement in resource requests
US8938526B1 (en) 2010-09-28 2015-01-20 Amazon Technologies, Inc. Request routing management based on network components
US9003035B1 (en) 2010-09-28 2015-04-07 Amazon Technologies, Inc. Point of presence management in request routing
US9083743B1 (en) 2012-03-21 2015-07-14 Amazon Technologies, Inc. Managing request routing information utilizing performance information
US9135048B2 (en) 2012-09-20 2015-09-15 Amazon Technologies, Inc. Automated profiling of resource usage
US9154551B1 (en) 2012-06-11 2015-10-06 Amazon Technologies, Inc. Processing DNS queries to identify pre-processing information
US9246776B2 (en) 2009-10-02 2016-01-26 Amazon Technologies, Inc. Forward-based resource delivery network management techniques
US9251112B2 (en) 2008-11-17 2016-02-02 Amazon Technologies, Inc. Managing content delivery network service providers
US9294391B1 (en) 2013-06-04 2016-03-22 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US9323577B2 (en) 2012-09-20 2016-04-26 Amazon Technologies, Inc. Automated profiling of resource usage
US9391949B1 (en) 2010-12-03 2016-07-12 Amazon Technologies, Inc. Request routing processing
US9407681B1 (en) 2010-09-28 2016-08-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9495338B1 (en) 2010-01-28 2016-11-15 Amazon Technologies, Inc. Content distribution network
US9525659B1 (en) 2012-09-04 2016-12-20 Amazon Technologies, Inc. Request routing utilizing point of presence load information
US9628554B2 (en) 2012-02-10 2017-04-18 Amazon Technologies, Inc. Dynamic content delivery
US9641692B2 (en) 2013-06-25 2017-05-02 Siemens Schweiz Ag Incident-centric mass notification system
US9712484B1 (en) 2010-09-28 2017-07-18 Amazon Technologies, Inc. Managing request routing information utilizing client identifiers
US9742795B1 (en) 2015-09-24 2017-08-22 Amazon Technologies, Inc. Mitigating network attacks
US9774619B1 (en) 2015-09-24 2017-09-26 Amazon Technologies, Inc. Mitigating network attacks
US9787775B1 (en) 2010-09-28 2017-10-10 Amazon Technologies, Inc. Point of presence management in request routing
US9794281B1 (en) 2015-09-24 2017-10-17 Amazon Technologies, Inc. Identifying sources of network attacks
US9819567B1 (en) 2015-03-30 2017-11-14 Amazon Technologies, Inc. Traffic surge management for points of presence
US9832141B1 (en) 2015-05-13 2017-11-28 Amazon Technologies, Inc. Routing based request correlation
US9887932B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9887931B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9912740B2 (en) 2008-06-30 2018-03-06 Amazon Technologies, Inc. Latency measurement in resource requests
US9992086B1 (en) 2016-08-23 2018-06-05 Amazon Technologies, Inc. External health checking of virtual private cloud network environments
US10021179B1 (en) 2012-02-21 2018-07-10 Amazon Technologies, Inc. Local resource delivery network
US10033691B1 (en) 2016-08-24 2018-07-24 Amazon Technologies, Inc. Adaptive resolution of domain name requests in virtual private cloud network environments
US10033627B1 (en) 2014-12-18 2018-07-24 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10049051B1 (en) 2015-12-11 2018-08-14 Amazon Technologies, Inc. Reserved cache space in content delivery networks
US10075551B1 (en) 2016-06-06 2018-09-11 Amazon Technologies, Inc. Request management for hierarchical cache
US10091096B1 (en) 2014-12-18 2018-10-02 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10097448B1 (en) 2014-12-18 2018-10-09 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10097566B1 (en) 2015-07-31 2018-10-09 Amazon Technologies, Inc. Identifying targets of network attacks
US10110694B1 (en) 2016-06-29 2018-10-23 Amazon Technologies, Inc. Adaptive transfer rate for retrieving content from a server
US10136276B2 (en) 2013-06-25 2018-11-20 Siemens Schweiz Ag Modality-centric mass notification system
US10205698B1 (en) 2012-12-19 2019-02-12 Amazon Technologies, Inc. Source-dependent address resolution
US10225326B1 (en) 2015-03-23 2019-03-05 Amazon Technologies, Inc. Point of presence based data uploading
US10257307B1 (en) 2015-12-11 2019-04-09 Amazon Technologies, Inc. Reserved cache space in content delivery networks
US10270878B1 (en) 2015-11-10 2019-04-23 Amazon Technologies, Inc. Routing for origin-facing points of presence

Families Citing this family (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8868659B2 (en) 2001-05-15 2014-10-21 Avaya Inc. Method and apparatus for automatic notification and response
US8102974B2 (en) * 2003-07-01 2012-01-24 Avaya Inc. Method and apparatus for event notification based on the identity of a calling party
US7734731B2 (en) 2004-03-18 2010-06-08 Avaya Inc. Method and apparatus for a publish-subscribe system with third party subscription delivery
US7603432B2 (en) * 2005-06-06 2009-10-13 Aa, Llc Locality based alert method and apparatus
US7933385B2 (en) * 2005-08-26 2011-04-26 Telecommunication Systems, Inc. Emergency alert for voice over internet protocol (VoIP)
KR100905593B1 (en) * 2005-10-18 2009-07-02 삼성전자주식회사 Digital multimedia broadcasting system and method for broadcasting user report
US8285694B1 (en) 2006-10-17 2012-10-09 At&T Mobility Ii Llc Distribution of enterprise related alerts via the emergency alert system
US7894827B2 (en) * 2006-10-20 2011-02-22 Adc Telecommunications, Inc. Method of identifying a device by GPS coordinates
CA2630481A1 (en) * 2007-05-06 2008-11-06 Contec Innovations, Inc. Method and system for managing information feed delivery to a communications device
US7900149B2 (en) * 2007-06-08 2011-03-01 Apple Inc. Methods and systems for editing of web pages in an application capable of displaying web page content
US8620288B2 (en) * 2007-11-16 2013-12-31 Alcatel Lucent Targeted mobile content insertion and/or replacement
US20090150925A1 (en) * 2007-12-06 2009-06-11 At&T Labs, Inc. System and Method of Providing An Alert
US8543667B2 (en) 2008-01-14 2013-09-24 Akamai Technologies, Inc. Policy-based content insertion
US8825092B2 (en) * 2008-03-27 2014-09-02 At&T Mobility Ii Llc Multi-mode provision of emergency alerts
US8655382B2 (en) * 2008-04-10 2014-02-18 Sharp Laboratories Of America, Inc. Wireless event notification system and methods for use therein
JP5262371B2 (en) * 2008-07-11 2013-08-14 日本電気株式会社 Notifying device, notification system, data processing method notification apparatus, and program
US20110219109A1 (en) * 2008-10-28 2011-09-08 Cotendo, Inc. System and method for sharing transparent proxy between isp and cdn
US20120209942A1 (en) * 2008-10-28 2012-08-16 Cotendo, Inc. System combining a cdn reverse proxy and an edge forward proxy with secure connections
US8868649B2 (en) * 2010-05-18 2014-10-21 Verizon Patent And Licensing Inc. Broadcasting events affecting public safety
US9183560B2 (en) 2010-05-28 2015-11-10 Daniel H. Abelow Reality alternate
EP2426655A1 (en) * 2010-09-06 2012-03-07 Alcatel Lucent Internet alert broadcaster
US8706743B2 (en) 2011-03-08 2014-04-22 Bank Of America Corporation Alert notification distribution tool
US8310361B1 (en) 2011-06-13 2012-11-13 Google Inc. Creating and monitoring alerts for a geographical area
US20120327837A1 (en) * 2011-06-24 2012-12-27 Velleros, Inc. Method, apparatus and system for providing emergency alerts to mobile devices
US9144008B2 (en) 2012-01-15 2015-09-22 Google Inc. Providing hotspots to user devices within server-controlled zones
US9325797B2 (en) 2012-02-29 2016-04-26 Google Inc. System and method for requesting an updated user location
US9104838B2 (en) 2012-11-14 2015-08-11 Google Inc. Client token storage for cross-site request forgery protection
US9191777B2 (en) * 2013-01-22 2015-11-17 Airsense Wireless Ltd. Clientless method for context driven wireless interactions
US9341479B2 (en) 2013-03-05 2016-05-17 Google Inc. Configurable point of interest alerts
US9083668B2 (en) * 2013-03-15 2015-07-14 Amatra Technologies, Inc. Adaptor based communications systems, apparatus, and methods
CN103220376B (en) * 2013-03-30 2014-07-16 清华大学 Method for positioning IP (Internet Protocol) by position data of mobile terminal
US8755824B1 (en) 2013-06-28 2014-06-17 Google Inc. Clustering geofence-based alerts for mobile devices
US9986375B2 (en) 2014-02-12 2018-05-29 Google Llc Energy-efficient location determination

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6329904B1 (en) * 1999-06-11 2001-12-11 Safety Through Cellular, Inc. Apparatus and method for providing weather and other alerts
US6594345B1 (en) * 1999-09-30 2003-07-15 Bellsouth Intellectual Property Corporation Targeted disaster warning system and apparatus
US6816878B1 (en) * 2000-02-11 2004-11-09 Steven L. Zimmers Alert notification system
US20050007999A1 (en) * 2003-06-25 2005-01-13 Gary Becker Universal emergency number ELIN based on network address ranges
US7277018B2 (en) * 2004-09-17 2007-10-02 Incident Alert Systems, Llc Computer-enabled, networked, facility emergency notification, management and alarm system
US7370364B2 (en) * 2000-07-31 2008-05-06 Ellacoya Networks, Inc. Managing content resources
US7376714B1 (en) * 2003-04-02 2008-05-20 Gerken David A System and method for selectively acquiring and targeting online advertising based on user IP address
US7389104B2 (en) * 2003-01-31 2008-06-17 Qwest Communications International Inc. Methods, systems and apparatus for providing urgent public information
US7403978B2 (en) * 1999-05-03 2008-07-22 Digital Envoy, Inc. Systems and methods for determining, collecting, and using geographic locations of internet users

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7403978B2 (en) * 1999-05-03 2008-07-22 Digital Envoy, Inc. Systems and methods for determining, collecting, and using geographic locations of internet users
US6329904B1 (en) * 1999-06-11 2001-12-11 Safety Through Cellular, Inc. Apparatus and method for providing weather and other alerts
US6594345B1 (en) * 1999-09-30 2003-07-15 Bellsouth Intellectual Property Corporation Targeted disaster warning system and apparatus
US6816878B1 (en) * 2000-02-11 2004-11-09 Steven L. Zimmers Alert notification system
US7370364B2 (en) * 2000-07-31 2008-05-06 Ellacoya Networks, Inc. Managing content resources
US7389104B2 (en) * 2003-01-31 2008-06-17 Qwest Communications International Inc. Methods, systems and apparatus for providing urgent public information
US7376714B1 (en) * 2003-04-02 2008-05-20 Gerken David A System and method for selectively acquiring and targeting online advertising based on user IP address
US20050007999A1 (en) * 2003-06-25 2005-01-13 Gary Becker Universal emergency number ELIN based on network address ranges
US7277018B2 (en) * 2004-09-17 2007-10-02 Incident Alert Systems, Llc Computer-enabled, networked, facility emergency notification, management and alarm system

Cited By (168)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10027582B2 (en) 2007-06-29 2018-07-17 Amazon Technologies, Inc. Updating routing information based on client location
US20130268633A1 (en) * 2007-06-29 2013-10-10 Amazon Technologies, Inc. Request routing utilizing client location information
US20130205045A1 (en) * 2007-06-29 2013-08-08 Amazon Technologies, Inc. Updating routing information based on client location
US9021129B2 (en) * 2007-06-29 2015-04-28 Amazon Technologies, Inc. Request routing utilizing client location information
US9021127B2 (en) * 2007-06-29 2015-04-28 Amazon Technologies, Inc. Updating routing information based on client location
US9992303B2 (en) 2007-06-29 2018-06-05 Amazon Technologies, Inc. Request routing utilizing client location information
US20090163170A1 (en) * 2007-12-21 2009-06-25 Koninklijke Kpn N.V. Emergency system and method
US9747784B2 (en) * 2007-12-21 2017-08-29 Koninklijke Kpn N.V. Emergency system and method
US8639817B2 (en) 2008-03-31 2014-01-28 Amazon Technologies, Inc. Content management
US9621660B2 (en) 2008-03-31 2017-04-11 Amazon Technologies, Inc. Locality based content distribution
US8713156B2 (en) 2008-03-31 2014-04-29 Amazon Technologies, Inc. Request routing based on class
US9571389B2 (en) 2008-03-31 2017-02-14 Amazon Technologies, Inc. Request routing based on class
US8135820B2 (en) 2008-03-31 2012-03-13 Amazon Technologies, Inc. Request routing based on class
US8156243B2 (en) 2008-03-31 2012-04-10 Amazon Technologies, Inc. Request routing
US9544394B2 (en) 2008-03-31 2017-01-10 Amazon Technologies, Inc. Network resource identification
US9888089B2 (en) 2008-03-31 2018-02-06 Amazon Technologies, Inc. Client side cache management
US8060561B2 (en) 2008-03-31 2011-11-15 Amazon Technologies, Inc. Locality based content distribution
US8275874B2 (en) 2008-03-31 2012-09-25 Amazon Technologies, Inc. Locality based content distribution
US9479476B2 (en) 2008-03-31 2016-10-25 Amazon Technologies, Inc. Processing of DNS queries
US9407699B2 (en) 2008-03-31 2016-08-02 Amazon Technologies, Inc. Content management
US9332078B2 (en) 2008-03-31 2016-05-03 Amazon Technologies, Inc. Locality based content distribution
US9954934B2 (en) 2008-03-31 2018-04-24 Amazon Technologies, Inc. Content delivery reconciliation
US8346937B2 (en) 2008-03-31 2013-01-01 Amazon Technologies, Inc. Content management
US8352613B2 (en) 2008-03-31 2013-01-08 Amazon Technologies, Inc. Content management
US8352614B2 (en) 2008-03-31 2013-01-08 Amazon Technologies, Inc. Content management
US7970820B1 (en) 2008-03-31 2011-06-28 Amazon Technologies, Inc. Locality based content distribution
US8386596B2 (en) 2008-03-31 2013-02-26 Amazon Technologies, Inc. Request routing based on class
US9210235B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Client side cache management
US8402137B2 (en) 2008-03-31 2013-03-19 Amazon Technologies, Inc. Content management
US9208097B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Cache optimization
US8321568B2 (en) 2008-03-31 2012-11-27 Amazon Technologies, Inc. Content management
US8438263B2 (en) 2008-03-31 2013-05-07 Amazon Technologies, Inc. Locality based content distribution
US8447831B1 (en) 2008-03-31 2013-05-21 Amazon Technologies, Inc. Incentive driven content delivery
US10157135B2 (en) 2008-03-31 2018-12-18 Amazon Technologies, Inc. Cache optimization
US10158729B2 (en) 2008-03-31 2018-12-18 Amazon Technologies, Inc. Locality based content distribution
US8756325B2 (en) 2008-03-31 2014-06-17 Amazon Technologies, Inc. Content management
US9026616B2 (en) 2008-03-31 2015-05-05 Amazon Technologies, Inc. Content delivery reconciliation
US8606996B2 (en) 2008-03-31 2013-12-10 Amazon Technologies, Inc. Cache optimization
US7962597B2 (en) 2008-03-31 2011-06-14 Amazon Technologies, Inc. Request routing based on class
US8601090B1 (en) 2008-03-31 2013-12-03 Amazon Technologies, Inc. Network resource identification
US20090248786A1 (en) * 2008-03-31 2009-10-01 Richardson David R Request routing based on class
US9009286B2 (en) 2008-03-31 2015-04-14 Amazon Technologies, Inc. Locality based content distribution
US8930544B2 (en) 2008-03-31 2015-01-06 Amazon Technologies, Inc. Network resource identification
US8352615B2 (en) 2008-03-31 2013-01-08 Amazon Technologies, Inc. Content management
US9894168B2 (en) 2008-03-31 2018-02-13 Amazon Technologies, Inc. Locality based content distribution
US8533293B1 (en) 2008-03-31 2013-09-10 Amazon Technologies, Inc. Client side cache management
US8458250B2 (en) 2008-06-30 2013-06-04 Amazon Technologies, Inc. Request routing using network computing components
US9608957B2 (en) 2008-06-30 2017-03-28 Amazon Technologies, Inc. Request routing using network computing components
US9912740B2 (en) 2008-06-30 2018-03-06 Amazon Technologies, Inc. Latency measurement in resource requests
US9021128B2 (en) 2008-06-30 2015-04-28 Amazon Technologies, Inc. Request routing using network computing components
US8239571B2 (en) 2008-06-30 2012-08-07 Amazon Technologies, Inc. Request routing using network computing components
US8301748B2 (en) 2008-11-17 2012-10-30 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US9515949B2 (en) 2008-11-17 2016-12-06 Amazon Technologies, Inc. Managing content delivery network service providers
US8321588B2 (en) 2008-11-17 2012-11-27 Amazon Technologies, Inc. Request routing utilizing client location information
US8583776B2 (en) 2008-11-17 2013-11-12 Amazon Technologies, Inc. Managing content delivery network service providers
US8732309B1 (en) 2008-11-17 2014-05-20 Amazon Technologies, Inc. Request routing utilizing cost information
US9251112B2 (en) 2008-11-17 2016-02-02 Amazon Technologies, Inc. Managing content delivery network service providers
US9787599B2 (en) 2008-11-17 2017-10-10 Amazon Technologies, Inc. Managing content delivery network service providers
US7991910B2 (en) * 2008-11-17 2011-08-02 Amazon Technologies, Inc. Updating routing information based on client location
US8788671B2 (en) 2008-11-17 2014-07-22 Amazon Technologies, Inc. Managing content delivery network service providers by a content broker
US8122098B1 (en) 2008-11-17 2012-02-21 Amazon Technologies, Inc. Managing content delivery network service providers by a content broker
US8301778B2 (en) 2008-11-17 2012-10-30 Amazon Technologies, Inc. Service provider registration by a content broker
US8028090B2 (en) 2008-11-17 2011-09-27 Amazon Technologies, Inc. Request routing utilizing client location information
US9985927B2 (en) 2008-11-17 2018-05-29 Amazon Technologies, Inc. Managing content delivery network service providers by a content broker
US8423667B2 (en) * 2008-11-17 2013-04-16 Amazon Technologies, Inc. Updating routing information based on client location
US9734472B2 (en) 2008-11-17 2017-08-15 Amazon Technologies, Inc. Request routing utilizing cost information
US8495220B2 (en) 2008-11-17 2013-07-23 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US8060616B1 (en) 2008-11-17 2011-11-15 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US8065417B1 (en) 2008-11-17 2011-11-22 Amazon Technologies, Inc. Service provider registration by a content broker
US8073940B1 (en) 2008-11-17 2011-12-06 Amazon Technologies, Inc. Managing content delivery network service providers
US8510448B2 (en) 2008-11-17 2013-08-13 Amazon Technologies, Inc. Service provider registration by a content broker
US10116584B2 (en) 2008-11-17 2018-10-30 Amazon Technologies, Inc. Managing content delivery network service providers
US9590946B2 (en) 2008-11-17 2017-03-07 Amazon Technologies, Inc. Managing content delivery network service providers
US9444759B2 (en) 2008-11-17 2016-09-13 Amazon Technologies, Inc. Service provider registration by a content broker
US8239514B2 (en) 2008-11-17 2012-08-07 Amazon Technologies, Inc. Managing content delivery network service providers
US8234403B2 (en) 2008-11-17 2012-07-31 Amazon Technologies, Inc. Updating routing information based on client location
US9451046B2 (en) 2008-11-17 2016-09-20 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US8458360B2 (en) 2008-11-17 2013-06-04 Amazon Technologies, Inc. Request routing utilizing client location information
US9038099B2 (en) 2008-12-08 2015-05-19 At&T Intellectual Property I, Lp Emergency alert representation
US20100146541A1 (en) * 2008-12-08 2010-06-10 At&T Intellectual Property I, L.P. Emergency Alert Representation
US8898697B2 (en) 2008-12-08 2014-11-25 At&T Intellectual Property I, Lp Emergency alert representation
US10264062B2 (en) 2009-03-27 2019-04-16 Amazon Technologies, Inc. Request routing using a popularity identifier to identify a cache component
US9083675B2 (en) 2009-03-27 2015-07-14 Amazon Technologies, Inc. Translation of resource identifiers using popularity information upon client request
US8463877B1 (en) 2009-03-27 2013-06-11 Amazon Technologies, Inc. Dynamically translating resource identifiers for request routing using popularitiy information
US8521885B1 (en) 2009-03-27 2013-08-27 Amazon Technologies, Inc. Dynamically translating resource identifiers for request routing using popularity information
US9191458B2 (en) 2009-03-27 2015-11-17 Amazon Technologies, Inc. Request routing using a popularity identifier at a DNS nameserver
US8756341B1 (en) 2009-03-27 2014-06-17 Amazon Technologies, Inc. Request routing utilizing popularity information
US8412823B1 (en) 2009-03-27 2013-04-02 Amazon Technologies, Inc. Managing tracking information entries in resource cache components
US10230819B2 (en) 2009-03-27 2019-03-12 Amazon Technologies, Inc. Translation of resource identifiers using popularity information upon client request
US9237114B2 (en) 2009-03-27 2016-01-12 Amazon Technologies, Inc. Managing resources in resource cache components
US8688837B1 (en) 2009-03-27 2014-04-01 Amazon Technologies, Inc. Dynamically translating resource identifiers for request routing using popularity information
US8996664B2 (en) 2009-03-27 2015-03-31 Amazon Technologies, Inc. Translation of resource identifiers using popularity information upon client request
US8521851B1 (en) 2009-03-27 2013-08-27 Amazon Technologies, Inc. DNS query processing using resource identifiers specifying an application broker
US9176894B2 (en) 2009-06-16 2015-11-03 Amazon Technologies, Inc. Managing resources using resource expiration data
US8782236B1 (en) 2009-06-16 2014-07-15 Amazon Technologies, Inc. Managing resources using resource expiration data
US8543702B1 (en) 2009-06-16 2013-09-24 Amazon Technologies, Inc. Managing resources using resource expiration data
US10135620B2 (en) 2009-09-04 2018-11-20 Amazon Technologis, Inc. Managing secure content in a content delivery network
US8397073B1 (en) 2009-09-04 2013-03-12 Amazon Technologies, Inc. Managing secure content in a content delivery network
US9712325B2 (en) 2009-09-04 2017-07-18 Amazon Technologies, Inc. Managing secure content in a content delivery network
US9130756B2 (en) 2009-09-04 2015-09-08 Amazon Technologies, Inc. Managing secure content in a content delivery network
US10218584B2 (en) 2009-10-02 2019-02-26 Amazon Technologies, Inc. Forward-based resource delivery network management techniques
US9893957B2 (en) 2009-10-02 2018-02-13 Amazon Technologies, Inc. Forward-based resource delivery network management techniques
US9246776B2 (en) 2009-10-02 2016-01-26 Amazon Technologies, Inc. Forward-based resource delivery network management techniques
US9495338B1 (en) 2010-01-28 2016-11-15 Amazon Technologies, Inc. Content distribution network
US8819283B2 (en) 2010-09-28 2014-08-26 Amazon Technologies, Inc. Request routing in a networked environment
US9106701B2 (en) 2010-09-28 2015-08-11 Amazon Technologies, Inc. Request routing management based on network components
US8930513B1 (en) 2010-09-28 2015-01-06 Amazon Technologies, Inc. Latency measurement in resource requests
US9497259B1 (en) 2010-09-28 2016-11-15 Amazon Technologies, Inc. Point of presence management in request routing
US8468247B1 (en) 2010-09-28 2013-06-18 Amazon Technologies, Inc. Point of presence management in request routing
US9160703B2 (en) 2010-09-28 2015-10-13 Amazon Technologies, Inc. Request routing management based on network components
US10225322B2 (en) 2010-09-28 2019-03-05 Amazon Technologies, Inc. Point of presence management in request routing
US10015237B2 (en) 2010-09-28 2018-07-03 Amazon Technologies, Inc. Point of presence management in request routing
US9003035B1 (en) 2010-09-28 2015-04-07 Amazon Technologies, Inc. Point of presence management in request routing
US9712484B1 (en) 2010-09-28 2017-07-18 Amazon Technologies, Inc. Managing request routing information utilizing client identifiers
US9191338B2 (en) 2010-09-28 2015-11-17 Amazon Technologies, Inc. Request routing in a networked environment
US8938526B1 (en) 2010-09-28 2015-01-20 Amazon Technologies, Inc. Request routing management based on network components
US9407681B1 (en) 2010-09-28 2016-08-02 Amazon Technologies, Inc. Latency measurement in resource requests
US8924528B1 (en) 2010-09-28 2014-12-30 Amazon Technologies, Inc. Latency measurement in resource requests
US10079742B1 (en) 2010-09-28 2018-09-18 Amazon Technologies, Inc. Latency measurement in resource requests
US8577992B1 (en) 2010-09-28 2013-11-05 Amazon Technologies, Inc. Request routing management based on network components
US9787775B1 (en) 2010-09-28 2017-10-10 Amazon Technologies, Inc. Point of presence management in request routing
US9794216B2 (en) 2010-09-28 2017-10-17 Amazon Technologies, Inc. Request routing in a networked environment
US8676918B2 (en) 2010-09-28 2014-03-18 Amazon Technologies, Inc. Point of presence management in request routing
US9800539B2 (en) 2010-09-28 2017-10-24 Amazon Technologies, Inc. Request routing management based on network components
US10097398B1 (en) 2010-09-28 2018-10-09 Amazon Technologies, Inc. Point of presence management in request routing
US9253065B2 (en) 2010-09-28 2016-02-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9185012B2 (en) 2010-09-28 2015-11-10 Amazon Technologies, Inc. Latency measurement in resource requests
US9003040B2 (en) 2010-11-22 2015-04-07 Amazon Technologies, Inc. Request routing processing
US8452874B2 (en) 2010-11-22 2013-05-28 Amazon Technologies, Inc. Request routing processing
US9930131B2 (en) 2010-11-22 2018-03-27 Amazon Technologies, Inc. Request routing processing
US9391949B1 (en) 2010-12-03 2016-07-12 Amazon Technologies, Inc. Request routing processing
US8626950B1 (en) 2010-12-03 2014-01-07 Amazon Technologies, Inc. Request routing processing
US9628554B2 (en) 2012-02-10 2017-04-18 Amazon Technologies, Inc. Dynamic content delivery
US10021179B1 (en) 2012-02-21 2018-07-10 Amazon Technologies, Inc. Local resource delivery network
US9083743B1 (en) 2012-03-21 2015-07-14 Amazon Technologies, Inc. Managing request routing information utilizing performance information
US9172674B1 (en) 2012-03-21 2015-10-27 Amazon Technologies, Inc. Managing request routing information utilizing performance information
US10225362B2 (en) 2012-06-11 2019-03-05 Amazon Technologies, Inc. Processing DNS queries to identify pre-processing information
US9154551B1 (en) 2012-06-11 2015-10-06 Amazon Technologies, Inc. Processing DNS queries to identify pre-processing information
US9525659B1 (en) 2012-09-04 2016-12-20 Amazon Technologies, Inc. Request routing utilizing point of presence load information
US9135048B2 (en) 2012-09-20 2015-09-15 Amazon Technologies, Inc. Automated profiling of resource usage
US10015241B2 (en) 2012-09-20 2018-07-03 Amazon Technologies, Inc. Automated profiling of resource usage
US9323577B2 (en) 2012-09-20 2016-04-26 Amazon Technologies, Inc. Automated profiling of resource usage
US10205698B1 (en) 2012-12-19 2019-02-12 Amazon Technologies, Inc. Source-dependent address resolution
US9929959B2 (en) 2013-06-04 2018-03-27 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US9294391B1 (en) 2013-06-04 2016-03-22 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US9641692B2 (en) 2013-06-25 2017-05-02 Siemens Schweiz Ag Incident-centric mass notification system
US10136276B2 (en) 2013-06-25 2018-11-20 Siemens Schweiz Ag Modality-centric mass notification system
US10091096B1 (en) 2014-12-18 2018-10-02 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10097448B1 (en) 2014-12-18 2018-10-09 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10033627B1 (en) 2014-12-18 2018-07-24 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10225326B1 (en) 2015-03-23 2019-03-05 Amazon Technologies, Inc. Point of presence based data uploading
US9887931B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9819567B1 (en) 2015-03-30 2017-11-14 Amazon Technologies, Inc. Traffic surge management for points of presence
US9887932B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9832141B1 (en) 2015-05-13 2017-11-28 Amazon Technologies, Inc. Routing based request correlation
US10180993B2 (en) 2015-05-13 2019-01-15 Amazon Technologies, Inc. Routing based request correlation
US10097566B1 (en) 2015-07-31 2018-10-09 Amazon Technologies, Inc. Identifying targets of network attacks
US10200402B2 (en) 2015-09-24 2019-02-05 Amazon Technologies, Inc. Mitigating network attacks
US9742795B1 (en) 2015-09-24 2017-08-22 Amazon Technologies, Inc. Mitigating network attacks
US9774619B1 (en) 2015-09-24 2017-09-26 Amazon Technologies, Inc. Mitigating network attacks
US9794281B1 (en) 2015-09-24 2017-10-17 Amazon Technologies, Inc. Identifying sources of network attacks
US10270878B1 (en) 2015-11-10 2019-04-23 Amazon Technologies, Inc. Routing for origin-facing points of presence
US10257307B1 (en) 2015-12-11 2019-04-09 Amazon Technologies, Inc. Reserved cache space in content delivery networks
US10049051B1 (en) 2015-12-11 2018-08-14 Amazon Technologies, Inc. Reserved cache space in content delivery networks
US10075551B1 (en) 2016-06-06 2018-09-11 Amazon Technologies, Inc. Request management for hierarchical cache
US10110694B1 (en) 2016-06-29 2018-10-23 Amazon Technologies, Inc. Adaptive transfer rate for retrieving content from a server
US9992086B1 (en) 2016-08-23 2018-06-05 Amazon Technologies, Inc. External health checking of virtual private cloud network environments
US10033691B1 (en) 2016-08-24 2018-07-24 Amazon Technologies, Inc. Adaptive resolution of domain name requests in virtual private cloud network environments

Also Published As

Publication number Publication date
US7529850B2 (en) 2009-05-05
US20060206568A1 (en) 2006-09-14

Similar Documents

Publication Publication Date Title
US7685315B2 (en) System and method for conveying terminal capability and user preferences-dependent content characteristics for content adaptation
US9542830B2 (en) Alert gateway, systems and methods
US9503533B2 (en) Network manager system for location-aware mobile communication devices
EP1413102B1 (en) Method and apparatus for obtaining data information
US6115754A (en) System and method for appending location information to a communication sent from a mobile terminal operating in a wireless communication system to an internet server
US6798358B2 (en) Location-based content delivery
EP1161049B1 (en) Method and apparatus for providing an internet third part data channel
EP1576789B1 (en) Transmission of application information and commands using presence technology
US8490129B2 (en) Methods, systems and apparatus for selectively distributing urgent public information
EP1941702B1 (en) Dynamic resource matching system
US8190118B2 (en) Integration of emergency alert information
US7721337B2 (en) System and method for providing a push of background data
EP1397923B1 (en) Mobile instant messaging and presence service
US7890572B2 (en) Pub/sub message invoking a subscribers client application program
US8526405B2 (en) Routing network requests based on requesting device characteristics
CA2444720C (en) Communications network
JP5073634B2 (en) Filtering application services at the intermediate apparatus in a communication channel
US7587459B2 (en) Remote application publication and communication system
EP1379971B1 (en) Schemas for a notification platform and related information services
US8195196B2 (en) Mobility based service in wireless environment
US8150416B2 (en) System and method for providing communication services to mobile device users incorporating proximity determination
US6708217B1 (en) Method and system for receiving and demultiplexing multi-modal document content
CN1561631B (en) Method for providing communication information of a communication unit and devices for carrying out said method
CA2547240C (en) Electronic message forwarding
US20070282621A1 (en) Mobile dating system incorporating user location information