JP7230065B2 - Transmit location information to devices along with wireless emergency alert messages via cell broadcast - Google Patents

Description

background

[field]
Various communication systems exist that benefit from the provision of pertinent location information. For example, in certain wireless communication systems, it may be advantageous to transmit location information to devices along with wireless emergency alert messages via cell broadcast.

[Description of related technology]
One aspect of wireless technology relates to transmitting emergency alert notifications to mobile devices over a Commercial Mobile Service Provider (CMSP) Fourth Generation (4G) network/Long Term Evolution (LTE) infrastructure.

Part of the network functionality associated with the broadcasting of wireless emergency alert (WEA) text messages is owned and controlled by the government. Also, part of the network functionality related to broadcasting WEA text messages belongs to the CMSP.

FIG. 1 shows an end-to-end architecture for WEA message broadcasting to mobile devices in LTE. As shown in FIG. 1, an alarm source (which may be some government agency) can generate a WEA text message to identify the disaster area. The WEA text message, along with the disaster site, is sent over the A interface to the Alert Aggregator and then over the B interface to the Federal Alert Gateway. The Federal Alert Gateway sends the WEA text message with the disaster area to the CMSP Gateway over the C interface. The CMSP gateway sends the WEA text message with the disaster site over the D interface to the CMSP infrastructure. The CMSP infrastructure broadcasts WEA text messages over the E-interface to mobile devices within the disaster cell/sector. The method used in such broadcasting is known as Cell Broadcast Service (CBS).

Within the CMSP infrastructure, a Cell Broadcast Center (CBC) identifies cells/sectors within the disaster area and distributes WEA text messages to the MMEs/eNBs corresponding to those cells/sectors. The eNB uses System Information Block (SIB) messages to broadcast WEA text messages to mobile devices in the disaster cell/sector.

As shown in FIG. 1, some of the network functional nodes involved in the broadcasting of WEA text messages are owned and controlled by the government. Also, some of the network function nodes involved in broadcasting WEA text messages belong to the CMSP. The Alliance for Telecommunications Industry Solutions (ATIS) has standardized the details of the LTE C, D, and E interfaces. The 3GPP specifications define details for SBc, S1-MME and E-UTRAN-Uu.

Summary

According to some exemplary embodiments, the method may include the access node receiving coordinates for the alert area of the wireless emergency alert target. The method may further comprise transmitting the coordinates from the access node to user equipment. The method may further comprise transmitting the wireless emergency alert to the user equipment.

According to some exemplary embodiments, the apparatus may comprise means for receiving coordinates for the alert area of the wireless emergency alert target. The apparatus may further comprise means for transmitting said coordinates to a user equipment. The apparatus may further comprise means for transmitting said wireless emergency alert to said user equipment.

According to some exemplary embodiments, an apparatus may comprise at least one processor and at least one memory containing computer program code. The at least one memory and the computer program code may be configured by the at least one processor to cause the device to receive at least coordinates for an alert area of a wireless emergency alert target. The at least one memory and the computer program code may be further configured, by the at least one processor, to cause the device to at least transmit the coordinates to user equipment. The at least one memory and the computer program code may be further configured to cause the at least one processor to cause the device to at least transmit the wireless emergency alert to the user equipment.

According to some exemplary embodiments, a non-transitory computer-readable medium may be encoded with instructions that may perform the method when executed in hardware. The method may include receiving coordinates for an alert area of a wireless emergency alert target. The method may further comprise transmitting the coordinates to user equipment. The method may further comprise transmitting the wireless emergency alert to the user equipment.

According to some exemplary embodiments, a computer program product may perform the method. The method may include receiving coordinates for an alert area of a wireless emergency alert target. The method may further comprise transmitting the coordinates to user equipment. The method may further comprise transmitting the wireless emergency alert to the user equipment.

According to some exemplary embodiments, the apparatus may comprise circuitry configured to receive coordinates for the alert area of the wireless emergency alert target. The apparatus may further comprise circuitry configured to transmit said coordinates to user equipment. The apparatus may further comprise circuitry configured to transmit the wireless emergency alert to the user equipment.

According to some exemplary embodiments, the method may include the user equipment receiving coordinates for the alert area of the wireless emergency alert target. The method may further comprise the user equipment determining whether the user equipment is within the alert area based on the coordinates. The method may further include the user equipment processing the wireless emergency alert based on the determination.

According to some exemplary embodiments, the apparatus may comprise means for receiving coordinates for the alert area of the wireless emergency alert target. The device may further comprise means for determining whether the device is within the warning area based on the coordinates. The apparatus may further comprise means for processing said wireless emergency alert based on said determination.

According to some exemplary embodiments, an apparatus may comprise at least one processor and at least one memory containing computer program code. The at least one memory and the computer program code may be configured by the at least one processor to cause the device to receive at least coordinates for an alert area of a wireless emergency alert target. The apparatus comprises at least one memory and computer program code configured to cause the at least one processor to cause the apparatus to at least determine if the apparatus is within the alert area based on the coordinates. may be further provided. The apparatus may further comprise at least one memory and computer program code configured by the at least one processor to cause the apparatus to process at least the wireless emergency alert based on the determination.

According to some exemplary embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, may perform the method. The method may include receiving coordinates for an alert area of a wireless emergency alert target. The method may further comprise determining if user equipment is within the alert area based on the coordinates. The method may further include the user equipment processing the wireless emergency alert based on the determination.

According to some exemplary embodiments, a computer program embodied on a non-transitory computer-readable medium, when executed by a processor, causes the processor to perform the method. The method may include receiving coordinates for an alert area of a wireless emergency alert target. The method may further comprise determining if user equipment is within the alert area based on the coordinates. The method may further include the user equipment processing the wireless emergency alert based on the determination.

According to some exemplary embodiments, the apparatus may comprise circuitry configured to receive coordinates for the alert area of the wireless emergency alert target. The device may further comprise circuitry configured to determine if the device is within the warning area based on the coordinates. The apparatus may further comprise circuitry configured to process the wireless emergency alert based on the determination.

For a proper understanding of the invention, reference should be made to the following figures.

1 illustrates an end-to-end architecture for sending WEA message broadcasts to mobile devices in LTE.

Overshoot and undershoot are shown.

Figure 3 shows the current handling of SIB12 in the mobile device logic.

FIG. 10 illustrates improved handling of system information blocks (SIB12 or new SIB) carrying WEA area coordinates at a conceptual level, according to certain embodiments; FIG.

4 shows a table showing various fields of a WRWR message, according to certain embodiments.

4 illustrates how a WEA area coordinate field is added to SIB 12, according to certain embodiments.

FIG. 4 shows pseudo code for handling SIB12, according to certain embodiments. FIG.

2 shows a comparison of two exemplary structures, according to certain embodiments;

1 illustrates a system according to certain embodiments;

2 illustrates an example flow chart of a method according to certain embodiments.

4 illustrates an example flowchart of another method, in accordance with certain embodiments.

Detailed explanation

In CBS, the CBC sends a text message (via MME) to the eNB corresponding to the area. Areas are identified by the CBC as cells/sectors. All mobile devices within the cell/sector can receive the CBS text message.

However, the Federal Communications Commission is unhappy with the process. This is because in some situations the alert may be valid only for a portion of the cell or sector. Also, depending on the method used to select the cell/sector, alert messages may occasionally reach mobile devices outside the coverage area (called overshoot). There may also be situations where the alert does not reach the mobile device that should have received it (called an undershoot).

FIG. 2 shows overshoots and undershoots. Specifically, FIG. 2 shows an example in which a disaster area corresponding to WEA is identified by polygons. A polygon may cover multiple cells/sectors. However, FIG. 2 focuses on a single cell, designated cell 1 in the figure. A cell includes three sectors, labeled A, B, and C in the figure.

As shown on the far left of FIG. 2, the alert polygon covers the entirety of sector B of cell 1 while partially covering sectors A and C of cell 1 . What the FCC wants in this exemplary situation is to broadcast WEA text messages only to mobile devices in sector B, and mobile devices in portions of sectors A and C, from the perspective of cell 1. . However, such targeted delivery is beyond the reach of current cell broadcast technology. The reason lies in the limitations on how to identify cells/sectors.

There may be many techniques by which a cell/sector can be identified. Two examples are shown in FIG. One notification rule in the first example could be to notify all mobile devices in a sector if the polygon contains the center of the cell (or eNB). As a result of this rule, all mobile devices in sectors A, B, and C will be notified because the center of cell 1 is contained within the polygon. It is clear that some mobile devices outside the polygon in sectors A and C will also receive the alert. This is called an overshoot state.

Another notification rule in the second example could be to notify all mobile devices within a sector if the polygon contains the center of the sector. As a result, all mobile devices in sectors A and B will be notified, and no Not notified. However, it is clear that some mobile devices in sector A are outside the polygon and some mobile devices in sector C are inside the polygon. In sector A, devices outside the polygon also receive an alert (overshoot condition), and in sector C, mobile devices inside the polygon do not receive an alert. The latter is called an undershoot state.

In a cell broadcast service architecture, alert text messages are sent to mobile devices as cell broadcast (CB) data, and within the SIB, the CB data is specified as the content of the alert message. The mobile device displays the alert text within the alert message content on the display screen. For LTE devices, the maximum number of display characters that can be included in a WEA text message is 360 characters.

Particular embodiments send the WEA area coordinates as a separate field in the system information block and use the coordinates from the separate field to determine if the device application is within the WEA area before displaying the message. based on the idea of modifying the According to this idea, mobile devices can use existing logic to perform message display, duplicate detection, and can use existing message identifier values. The alerter could use all 360 characters to compose the display text.

In order to send WEA messages with WEA area coordinates, SIB12 (SystemInformationBlockType12) may be improved or a new SIB may be visualized for this purpose. FIG. 3 shows the current handling of SIB12 in the mobile device logic. Specifically, FIG. 3 shows the current handling of SIB12 and upper layer processing of WEA messages at a conceptual level.

The first half of the flowchart shown in FIG. 3 is based on the pseudocode specified in 3GPP TS 36.331. The second half of the flow chart shown in FIG. 3 shows a high-level conceptualization of upper-layer processing of WEA messages. Upper layer processing first checks to see if the WEA text has been previously displayed. The mobile device discards the message if it has been previously displayed. If not, the device can display the text on the screen and treat the message as displayed.

FIG. 4 illustrates, at a conceptual level, improved handling of system information blocks (SIB12 or new SIB) carrying WEA area coordinates, according to certain embodiments. The first half of the flow chart shown in FIG. 4 basically follows the pseudo code for SIB12 handling, with one modification. That is, this SIB can expect to receive WEA area coordinates and pass the WEA area coordinates up for processing. The second half of the flow chart of FIG. 4 shows more refined upper layer processing of WEA messages.

This improved upper layer processing may be constant regardless of which SIB is used to send the WEA message from the eNB to the mobile device. That is, improvements may be based on changes to upper layer processing of current WEA messages.

As shown in this flow chart, if the message has not been displayed before, the refinement can first check if there are WEA area coordinates. If not, the mobile device can display the WEA text on the device screen according to current logic. With the WEA area coordinates, the mobile device can ascertain its current location and determine if it is within the WEA area coordinates. Once the mobile device confirms it is within the WEA area coordinates, it can display the WEA text on the device screen, record the message identifier/serial number, and enable duplicate detection logic for subsequently received SIBs, according to current logic. . The mobile device can discard the message once it sees that it is not within the WEA area coordinates.

According to this approach, the mobile device may move into the WEA area at some later time, in which case, upon repeated messages by the eNB, the improved upper layer processing of FIG. Allow the mobile device to display WEA text on the device screen as it is currently within the WEA area (by being out of range).

The CBC, MME, eNB, and mobile device may be modified to implement certain embodiments. Also, the WRWR message may be modified to send WEA coordinates, and SIB12 may be modified or a new SIB defined to send WEA area coordinates.

Modifications to the WRWR message may include adding new fields to add WEA area coordinates. FIG. 5 is a table illustrating various fields of a WRWR message, according to certain embodiments.

In current WEA implementations, the Federal Alert Gateway can send the WEA area coordinates to the CMSP GW as shown in FIG. However, in current practice, WEA areas can also be specified by geocode. Perhaps as a prerequisite, the C interface specification may be based on the existence of WEA area coordinates. The CMSP GW can send the WEA coordinates to the CBC along with an indication requesting the CBC to pass the WEA area coordinates to the mobile device.

In current implementations, the CBC uses WEA area coordinates (or geocodes) to determine the TA list and alert area list. The CBC can then send the WEA area coordinates to the MME in a WRWR message.

The MME may include the WEA area coordinates from the WRWR message received from the CBC in the WRWR message it sends to the eNB.

The eNB can receive the WEA area coordinates in the WRWR message and populate the WEA area coordinates into the system information block.

New fields of WEA area coordinates can be added to SIB12. FIG. 6 illustrates how the WEA area coordinate field is added to SIB 12, according to certain embodiments.

Instead of adding the WEA area coordinates (weaAreaCoordinates) to SIB12, a new SIB can be defined that inherits all the parameters from SIB12 and also sends the WEA area coordinates. ASN. Given the original definition of SIB12 (the presence of "..."), it would be possible to add new fields to SIB12 without causing backward compatibility problems. Using a new SIB can be more expensive.

FIG. 7 illustrates pseudocode for handling of SIB12, according to certain embodiments. If a new SIB is used, the pseudocode in Figure 7 can be the pseudocode for that new SIB.

Upper layer processing is not defined in the 3GPP standard. It is possible to modify the Alliance for Telecommunications Industry Solutions (ATIS) standard for mobile device standards of conduct to reflect the changes in FIG.

Another approach is to embed the WEA area coordinates within the WEA text message. Sending the WEA coordinates to the mobile device as part of the WEA text message requires no changes to the Federal Warning GW, CMSP GW, CBC, MME, eNB. Constructing the WEA area coordinates within the WEA text message can be part of the work of the alerter.

However, the inclusion of WEA area coordinates would have a greater impact on 3GPP usage as it would require adding a new message identifier and also defining the structure of the alarm content. For example, FIG. 8 shows two exemplary structures according to certain embodiments. In this approach, it may be assumed that 30 new message identifier values are added.

As shown in FIG. 8, in this specific method, the number of displayable characters is changed from 360 to 360-X. X indicates the number of characters required to populate the WEA area coordinates. WEA area coordinates may be included in the first CB page. A mobile device can read characters from the first CB page and use those characters as WEA area coordinates. Additionally, the WEA area coordinates may include information that tells the mobile device how to extract the WEA area coordinates from the displayed characters.

FIG. 8 assumes that the same script is used for the WEA area coordinates and the displayed text. However, to represent the WEA area coordinates in compressed form and the GSM 7-bit display text, other methods may need to be considered. This approach becomes more complicated to send such multiple formats to the mobile device.

The number of SIB segments required to send a 360 character message can also be changed to include the WEA area coordinates. The current state is that 12 to 14 octets (ATIS-0700023) are used to send the following SIB12 header information. Specifically, 2 octets for the message identifier, 2 octets for the serial number, 1 octet for the data encoding scheme, and 8 octets for other (including alarm message segment type, alarm message segment number, and previous non-critical extensions). .

When DCI type 1C is used (see 3GPP TS 36.331), each SIB segment can carry up to 217 octets of data. Since 14 octets are used for overhead, approximately 203 octets are available to carry the content of the alert message.

A 360 character WEA text message requires 4CB pages. A WEA message for 4 CB pages requires 333 octets (84+83+83+83). Two Type 1C SIB segments are required to send 333 octets of CB data. Assuming that the first segment can send 217 octets (ie, 203 octets of CB data), the remaining 130 octets of CB data will be sent in the second segment. The 130 octets of display text in the latter segment require approximately 144 octets. Therefore, the number of characters in the two segments is as follows. 217 for the first segment (14 for header + 203 for CB data), 144 for the second segment (14 for header + 130 for CB data).

In some areas, 217 octets of data may not be sent in an SIB segment. In such cases, an additional SIB segment is required to send the 360 character WEA message.

According to the improved SIB12, the WEA area coordinates can be sent as separate elements. Therefore, more octets may be required for overhead. To understand the impact, we need to make an assumption about the number of octets reserved for WEA area coordinates. Assuming a maximum of 32 octets to send WEA coordinates, the number of overhead octets varies from 14 to 46. That is, for Type 1C, a total of 169 (217-46) octets are available for sending CB data for each segment.

To send 333 octets of CB data, two Type 1C SIB segments are required. Assuming that the first segment can send 217 octets (ie, 169 octets of CB data), the remaining 164 octets of CB data will be sent in the second segment. The 164 octets of display text in the latter segment requires approximately 210 octets. Therefore, the number of characters in the two segments is as follows. 217 in the first segment (46 in header + 169 in CB data), 210 in the second segment (46 in header + 164 in CB data).

Alternatively, the SIB12 segments may be defined such that the WEA area coordinates are only sent in the first segment. According to this approach, the second segment only requires 14 octets (according to current methods) to send overhead data. To implement this arbitrary approach, perhaps ASN. No changes to the definition of 1 will be necessary. This is because new WEA area coordinates (weaAreaCoordinates) can be introduced with the "any" tag.

As a further alternative, it is possible to define the SIB12 segment such that the WEA area coordinates are sent only in the second segment. According to this approach, the first segment only requires 14 octets (according to current methods) to send overhead data. In the current method, of the available 203 octets, only 130 octets of the second segment are used to send the CB data (see paragraph 0061 ), so approximately 73 octets are available to send the WEA coordinates. can be assumed to exist. To implement this arbitrary approach, perhaps ASN. No changes to the definition of 1 will be necessary. This is because new area coordinates (newAreaCoordinates) can be introduced with the "any" tag.

According to this alternative approach, shown in paragraph 0055 , no elements are added to the SIB, and the WEA area coordinates are sent by display character reduction. The impact on SIB segment utilization will remain the same as the current CB data totals.

On the other hand, if this alternative approach (paragraph 0055 ) were further refined to send up to 360 display characters in addition to the WEA area coordinates, the number of CB pages required would also increase, affecting segment utilization.

For example, considering the same example as in paragraph 0063 , if the WEA area coordinates are specified with a maximum of 32 octets of data, then 32 octets of WEA area coordinates (i.e. approximately 37 characters of GSM 7-bit format) and 360 characters of display text The total number of GSM 7-bit characters to send is 397 (360+37). To send a 397 GSM 7-bit character requires 416 octets of CB data (ATIS-0700023). To send 416 octets of CB data, for Type 1C, three SIB12 segments are required with the following configuration. 217 for the first segment (14 for header + 203 for CB data), 217 for the second segment (14 for header + 203 for CB data), 24 for the third segment (14 for header + 10 for CB data).

Adding segments can affect the time delay. This is because it takes longer to broadcast the added segments.

FIG. 9 shows a system according to certain embodiments of the invention. It will be appreciated that each block in the flowchart of FIG. 4 may be implemented by various means or combinations thereof, such as hardware, software, firmware, one or more processors and/or circuits. In one embodiment, a system may include multiple devices such as, for example, a network component 910 and a user equipment (UE) or user device 920 . The system may include two or more UEs 920 and two or more network components 910, although only one of each is shown for purposes of illustration. A network element may be an access point, a base station, an eNodeB (eNB), or any other network element.

Each of these devices may comprise at least one processor or control unit or module, shown as 914, 924 respectively. Each device may be provided with at least one memory, shown as 915 and 925 respectively. This memory may include computer program instructions or computer code stored therein, for example, for performing the above-described embodiments. One or more transceivers 916, 926 may be provided and each device may further comprise an antenna, shown as 917, 927 respectively. Although only one antenna is shown for each, multiple antennas and multiple antenna components may be provided for each device. For example, other configurations of these devices may be provided. For example, network component 910 and UE 920 may be further configured for wired as well as wireless communication, in which case antennas 917 and 927 may be any form of communication, not just limited to antennas. Hardware can be shown.

Each transceiver 916, 926 may independently be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device configured for transmission and reception. The transmitter and/or receiver (as far as radio components are concerned) may also be implemented as a remote radio head, for example not located on the device itself, but on a pylon. Further, it should be appreciated that the operations and functionality may be flexibly implemented in various entities, such as nodes, hosts, or servers, in accordance with the "liquid" radio or flexible radio concept. In other words, the division of duties may differ from case to case. One possible use is to have network components deliver local content. One or more of the functionality may also be implemented as a virtual application provided as software executable on a server.

The user device or user equipment 920 includes a mobile station such as a mobile phone or a smartphone (Mobile Station: MS), a multimedia device, a computer with a wireless communication function such as a tablet, a mobile information terminal with a wireless communication function (Personal Data/Digital Assistant (PDA), vehicle with wireless communication capability, portable media player, digital camera, pocket video camera, navigation unit, or any combination thereof. User device or user equipment 920 may be a sensor or smart meter, or other device that may typically be configured for a single location.

In an exemplary embodiment, an apparatus such as a node or user device may comprise means for performing the embodiments described above with respect to FIG.

Processors 914, 924 can be any computer or data processing device, such as a Central Processing Unit (CPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC). , a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a digitally enhanced circuit, equivalent devices, or combinations thereof. A processor may be implemented as a single controller or as multiple controllers or processors. Additionally, processors may be implemented as a collection of processors in a local configuration, a cloud configuration, or a combination thereof. The term "circuit" may refer to one or more electrical or electronic circuits. The term "processor" may refer to a circuit, such as a logic circuit, that responds to and processes instructions to drive a computer.

For firmware or software, an implementation may include at least one chipset (eg, procedure, function, etc.) module or unit. Memories 915, 925 may independently be any storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. These memories may be combined into one integrated circuit as the processor, or may be provided separately. Moreover, the computer program instructions that may be stored in memory and processed by a processor may be any computer program code, such as, for example, a compiled or interpreted computer program written in any suitable programming language. can do. The memory or data storage entity is typically self-contained, but may be provided externally or a combination thereof, eg, where additional memory capability is obtained from a service provider. The memory may be fixed or removable.

The memory and computer program instructions may execute any of the processes described above (see, eg, FIGS. 1, 10, 11) to hardware devices such as network component 910 and/or UE 920 by a processor for a particular device. It may be configured to be implemented. Thus, in certain embodiments, a non-transitory computer-readable medium is computer instructions or one or more instructions that, when executed in hardware, can perform a process, such as one of the processes described herein. computer programs (additional or updated software routines, applets, macros, etc.). Computer programs may be coded in a programming language, which may be a high-level programming language such as Objective C, C, C++, C#, Java, or a low-level programming language such as machine language or assembler. Alternatively, certain embodiments of the invention may be implemented entirely in hardware.

Further, although FIG. 9 shows a system including network component 910 and UE 920, embodiments of the present invention apply to other configurations and configurations with additional components shown and described herein. can be For example, there may be multiple user equipment devices and multiple network components, and there may be other nodes that provide similar functionality, such as nodes that combine the functionality of user equipment and access points, such as relay nodes. You may

FIG. 10 shows an example flowchart of a method according to certain embodiments. In certain embodiments, the flowchart of FIG. 10 may be performed by a network entity, network node, or access node in a 3GPP system, such as LTE or 5G New Radio (NR). For example, in some exemplary embodiments the method of FIG. 10 may be performed by a base station or access node, eNB, or gNB.

In an exemplary embodiment, the method of FIG. 10 may first include, at 100, the access node receiving coordinates for the alert area of the wireless emergency alert target. The method may further include, at 105, transmitting coordinates from the access node to the user equipment. The method may further include transmitting a wireless emergency alert to the user equipment at 110 . According to certain exemplary embodiments, said coordinates may be transmitted within a system information block. In another exemplary embodiment, the coordinates may be transmitted with the wireless emergency alert.

FIG. 11 shows an example flowchart of another method in accordance with certain embodiments. In certain exemplary embodiments, the flowchart of FIG. 11 may be executed, for example, by mobile stations and/or UEs. In an exemplary embodiment, the method of FIG. 11 may first include, at 200, the user equipment receiving coordinates for the alert area of the wireless emergency alert target. The method may include, at 205, the user equipment determining if the user equipment is within the alert area based on the coordinates. The method may further include, at 210, the user equipment processing the wireless emergency alert based on the determination. In certain exemplary embodiments, the coordinates may be received within a system information block. In another exemplary embodiment, the coordinates may be received with the wireless emergency alert.

It will be apparent to those skilled in the art that the invention described above may be implemented using other sequences of steps and/or using different configurations of hardware components than those disclosed. . Thus, although the present invention has been described with reference to preferred embodiments, those skilled in the art will appreciate that certain modifications, changes, and alternative constructions are possible without departing from the spirit and scope of the invention. would be self-explanatory.

[Cross reference to related applications]
This application claims priority to US Provisional Patent Application No. 62/630,067, filed February 13, 2018, which is incorporated herein in its entirety.

[list of abbreviations]
3GPP (3rd Generation Partnership Project) 4G (4th Generation) 4th Generation ATIS (Alliance for Telecommunications Industry Solutions) CBC (Cell Broadcast Center) Cell Broadcast Center CBS (Cell Broadcast Service) Cell Broadcast service DCI (Downlink Control Information) Downlink control information eNB (enhanced nodeB) Evolved NodeB
ETWS (Earthquake and Tsunami Warning System) Earthquake and tsunami warning system E-UTRAN (Evolved Universal Terrestrial Radio Access Network) Radio network for providing high-speed communication standard LTE FCC (Federal Communications Commission) Federal Communications Commission ID (Identity or identifier) Identifier Id (Identity or identifier) LTE (Long Term Evolution) Long Term Evolution MME (Mobility Management Entity) Mobility Management Entity OMC (Operations Maintenance Center) Operations Management Center PWS (Public Warning System) Public Warning System SIB (System Information Block) System information block TA (Tracking Area) Tracking area TS (Technical Specification) WEA (Wireless Emergency Alarm) WRWR (Write Replace Warning Request) Rewrite alarm request

Claims (14)

receiving coordinates for an access node to identify an alert area for wireless emergency alerts ;
transmitting the coordinates from the access node to a user equipment;
transmitting the wireless emergency alert to the user equipment;
wherein the coordinates are ASN. A method, sent after an ellipsis of 1. 2. The method of claim 1, wherein said coordinates are transmitted with said wireless emergency alert. Receiving coordinates for user equipment to identify an alert area for wireless emergency alerts ;
determining whether the user device is within the alert area based on the coordinates;
the user equipment processing the wireless emergency alert based on the determination;
wherein the coordinates are ASN. Received after 1 ellipsis, method 4. The method of claim 3, wherein said coordinates are received with said wireless emergency alert. means for receiving coordinates for identifying an alert area for wireless emergency alert ;
means for transmitting said coordinates to a user equipment;
means for transmitting said wireless emergency alert to said user equipment;
, wherein the coordinates are ASN. A device that is sent after an ellipsis of 1. 6. The apparatus of claim 5, wherein said coordinates are transmitted with said wireless emergency alert. a device,
means for receiving coordinates for identifying an alert area for wireless emergency alert ;
means for determining whether the device is within the warning area based on the coordinates;
means for processing the wireless emergency alert based on the determination;
and said coordinates are ASN. Device received after 1 ellipsis. 8. The apparatus of claim 7, wherein said coordinates are received with said wireless emergency alert. Apparatus comprising processing means and storage means, said storage means storing program instructions which, when executed by said processing means, cause said apparatus to perform a method according to claim 1 or 2. A device configured to perform. means for receiving coordinates for identifying an alert area for wireless emergency alert;
means for transmitting said coordinates to a user equipment;
means for transmitting said wireless emergency alert to said user equipment;
wherein the coordinates are ASN. A circuit that is sent after an ellipsis of 1. A computer program comprising program instructions adapted to perform a method according to claim 1 or 2 in a device when executed on processing means of the device. Apparatus comprising processing means and storage means, said storage means storing program instructions which, when executed by said processing means, cause said apparatus to perform a method according to claim 3 or 4. A device configured to perform. a circuit,
means for receiving coordinates for identifying an alert area for wireless emergency alert;
means for determining whether there is a device comprising the circuit within the alert area based on the coordinates;
means for processing the wireless emergency alert based on the determination;
and said coordinates are ASN. A circuit, received after an ellipsis of 1. A computer program comprising program instructions adapted to perform a method according to claim 3 or 4 in said apparatus when executed on processing means of the apparatus.

Images