Techniques for delivering emergency payloads for non-voice emergency services

• US 9,143,253 B2
• Filed: 03/14/2013
• Issued: 09/22/2015
• Est. Priority Date: 05/11/2012
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Venkatachalam, Muthaiah, Siow, Eric, Jain, Puneet K.
• Primary Examiner(s): WASHINGTON, ERIKA ALISE
• Application Number:
  US13/828,973
• Publication Number:
  US 20130303104A1
• Time in Patent Office: 922 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04B 1/56 with provision for simultaneous communication in two directions
• CPC Class Codes: H04B 15/00 Suppression or limitation of noise or interference by means associated with receiver H04B1/10
• CPC Class Codes: H04B 7/024 Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
• CPC Class Codes: H04B 7/0417 Feedback systems
• CPC Class Codes: H04B 7/0456 Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
• CPC Class Codes: H04B 7/0473 taking constraints in layer or codeword to antenna mapping into account
• CPC Class Codes: H04B 7/0486 taking channel rank into account
• CPC Class Codes: H04B 7/0626 Channel coefficients, e.g. channel state information [CSI]
• CPC Class Codes: H04B 7/063 Parameters other than those covered in groups H04B7/0623 - H04B7/0634, e.g. channel matrix rank or transmit mode selection
• CPC Class Codes: H04B 7/0632 Channel quality parameters, e.g. channel quality indicator [CQI]
• CPC Class Codes: H04B 7/0639 Using selective indices, e.g. of a codebook, e.g. pre-distortion matrix index [PMI] or for beam selection
• CPC Class Codes: H04B 7/0647 Variable feedback rate
• CPC Class Codes: H04B 7/065 Variable contents, e.g. long-term or short-short
• CPC Class Codes: H04B 7/26 at least one of which is mobile
• CPC Class Codes: H04J 3/00 Time-division multiplex systems H04J14/00 takes precedence; relay systems H04B7/14; selecting techniques H04Q
• CPC Class Codes: H04J 3/1694 Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers Passive Optical Networks H04Q11/0062
• CPC Class Codes: H04J 3/26 in which the information and the address are simultaneously transmitted
• CPC Class Codes: H04L 1/0026 Transmission of channel quality indication
• CPC Class Codes: H04L 1/1803 Stop-and-wait protocols
• CPC Class Codes: H04L 1/1822 involving configuration of automatic repeat request [ARQ] with parallel processes
• CPC Class Codes: H04L 27/2627 : Modulators
• CPC Class Codes: H04L 5/0007 : the frequencies being orthogonal, e.g. OFDM(A), DMT
• CPC Class Codes: H04L 5/001 : the frequencies being arranged in component carriers
• CPC Class Codes: H04L 5/0035 : Resource allocation in a cooperative multipoint environment
• CPC Class Codes: H04L 5/0053 : Allocation of signaling, i.e. of overhead other than pilot signals
• CPC Class Codes: H04L 5/0073 : Allocation arrangements that take into account other cell interferences for intercell interference mitigation or co-ordination in orthogonal multiplex systems H04J11/005
• CPC Class Codes: H04L 5/0096 : Indication of changes in allocation
• CPC Class Codes: H04L 5/14 : Two-way operation using the same type of signal, i.e. duplex
• CPC Class Codes: H04L 5/1469 : using time-sharing
• CPC Class Codes: H04L 65/00 : Network arrangements, protocols or services for supporting real-time applications in data packet communication real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00
• CPC Class Codes: H04L 69/22 : Parsing or analysis of headers
• CPC Class Codes: H04L 69/324 : in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: H04W 16/14 : Spectrum sharing arrangements between different networks
• CPC Class Codes: H04W 24/02 : Arrangements for optimising operational condition
• CPC Class Codes: H04W 24/10 : Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 36/00 : Hand-off or reselection arrangements
• CPC Class Codes: H04W 36/0055 : Transmission or use of information for re-establishing the radio link
• CPC Class Codes: H04W 36/0061 : of neighbour cell information
• CPC Class Codes: H04W 36/0088 : Scheduling hand-off measurements
• CPC Class Codes: H04W 36/0094 : Definition of hand-off measurement parameters
• CPC Class Codes: H04W 36/04 : Reselecting a cell layer in multi-layered cells
• CPC Class Codes: H04W 36/16 : Performing reselection for specific purposes
• CPC Class Codes: H04W 36/18 : for allowing seamless reselection, e.g. soft reselection
• CPC Class Codes: H04W 36/22 : for handling the traffic
• CPC Class Codes: H04W 36/30 : by measured or perceived connection quality data
• CPC Class Codes: H04W 36/32 : by location or mobility data, e.g. speed data
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/023 : using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/06 : Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
• CPC Class Codes: H04W 4/16 : Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 4/90 : Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 48/20 : Selecting an access point
• CPC Class Codes: H04W 52/0209 : in terminal devices terminal devices per se H04W88/02
• CPC Class Codes: H04W 52/0212 : managed by the network, e.g. network or access point is master and terminal is slave
• CPC Class Codes: H04W 52/0216 : using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/0225 : using monitoring of external events, e.g. the presence of a signal
• CPC Class Codes: H04W 52/0229 : where the received signal is a wanted signal
• CPC Class Codes: H04W 52/0235 : where the received signal is a power saving command
• CPC Class Codes: H04W 52/0251 : using monitoring of local events, e.g. events related to user activity
• CPC Class Codes: H04W 56/00 : Synchronisation arrangements
• CPC Class Codes: H04W 56/001 : Synchronization between nodes
• CPC Class Codes: H04W 72/02 : Selection of wireless resources by user or terminal
• CPC Class Codes: H04W 72/044 : based on the type of the allocated resource
• CPC Class Codes: H04W 72/12 : Wireless traffic scheduling
• CPC Class Codes: H04W 72/1215 : for collaboration of different radio technologies
• CPC Class Codes: H04W 72/21 : in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/27 : between access points
• CPC Class Codes: H04W 72/30 : Resource management for broadcast services
• CPC Class Codes: H04W 72/51 : based on terminal or device properties
• CPC Class Codes: H04W 72/54 : based on quality criteria
• CPC Class Codes: H04W 72/541 : using the level of interference
• CPC Class Codes: H04W 72/542 : using measured or perceived quality
• CPC Class Codes: H04W 72/56 : based on priority criteria
• CPC Class Codes: H04W 76/14 : Direct-mode setup
• CPC Class Codes: H04W 76/18 : Management of setup rejection or failure
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Examples are disclosed for delivering, at user equipment (UE) such as a wireless device, emergency payloads for non-voice emergency services (NOVES). The examples include receiving, at a UE, an emergency payload associated with a NOVES that may include an emergency indicator, a voice message, a video or a text message. An attempt may be made to deliver the emergency payload to a public service answering point (PSAP) and if the attempt is not successful, the emergency payload may be stored at the UE. A number of reattempts may be made to deliver the emergency payload to the PSAP if the attempt is not successful. Based on an acknowledgement of delivery of the emergency payload to the PSAP or aborting reattempts to deliver the emergency payload, the stored emergency payload may be removed from the UE. Other examples are described and claimed.

Claims

1. A computer-implemented method comprising:

receiving, at user equipment (UE) capable of operating in compliance with one or more 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards, an emergency payload associated with a non-voice emergency service (NOVES), the emergency payload to include at least one of an emergency indicator, a voice message, a video or a text message;

attempting to transmit the emergency payload to a public service answering point (PSAP) via a wireless communication network;

storing the emergency payload at the UE responsive to an unsuccessful attempt to transmit the emergency payload to the PSAP; and

reattempting to transmit the emergency payload until a successful attempt to transmit the emergency payload has occurred or the NOVES has been aborted.

2. The computer-implemented method of claim 1, comprising purging the emergency payload from the UE responsive to an acknowledgement from the PSAP of receipt of the emergency payload or responsive to the NOVES being aborted.

3. The computer-implemented method of claim 1, comprising reattempting to transmit the stored emergency payload for a configurable number of times, the NOVES to be aborted based on a number of reattempts exceeding the configurable number of times.

4. The computer-implemented method of claim 1, comprising the unsuccessful attempt to transmit the emergency payload to the PSAP is caused by one of inadequate signal quality to attach to the wireless communication network, the wireless communication network is temporarily inoperable, or the wireless communication network is congested or overloaded.

5. The computer-implemented method of claim 1, comprising storing the emergency payload with a timestamp to indicate a time when the NOVES was invoked to indicate an emergency or location information to indicate the location of the UE at the time when the NOVES was invoked.

6. The computer-implemented method of claim 1, the emergency indicator comprises a home intruder alert, a burglary in progress alert, a medical emergency, a vehicle accident, a lost person, an abduction alert or a workplace violence alert.

7. The computer-implemented method of claim 1, comprising the UE including an emergency call handling application to receive the emergency payload associated with the NOVES, to attempt to transmit the emergency payload to the PSAP, to store the emergency payload responsive to the unsuccessful attempt, to reattempt to transmit the stored emergency payload, or to purge the emergency payload from the UE responsive to the acknowledgement or responsive to the NOVES being aborted.

8. The computer-implemented method of claim 7, comprising a non-access stratum (NAS) layer of a 3GPP protocol stack executed by a processor circuit of the UE, the NAS layer to receive the emergency payload associated with the NOVES, to attempt to transmit the emergency payload to the PSAP, to store the emergency payload responsive to the unsuccessful attempt, to reattempt to transmit the stored emergency payload, or to purge the emergency payload from the UE responsive to the acknowledgement or responsive to the NOVES being aborted.

9. The computer-implemented method of claim 1, comprising a radio resource control (RRC) layer of a 3GPP protocol stack executed by a processor circuit of the UE, the RRC layer to receive the emergency payload associated with the NOVES, to attempt to transmit the emergency payload to the PSAP, to store the emergency payload responsive to the unsuccessful attempt, to reattempt to transmit the stored emergency payload, or to purge the emergency payload from the UE responsive to the acknowledgement or responsive to the NOVES being aborted.

10. The computer-implemented method of claim 1, comprising an emergency store and forward layer of a 3GPP protocol stack executed by a processor circuit of the UE, the emergency store and forward layer to receive the emergency payload associated with the NOVES, to attempt to transmit the emergency payload to the PSAP, to store the emergency payload responsive to the unsuccessful attempt, to reattempt to transmit the stored emergency payload, or to purge the emergency payload from the UE responsive to the acknowledgement or responsive to the NOVES being aborted.

11. An apparatus comprising:

a processor circuit for user equipment (UE) capable of operating in compliance with one or more 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards; and

a non-access stratum (NAS) layer of a 3GPP protocol stack for execution by the processor circuit, the NAS layer to include;

a payload component to receive an emergency payload associated with a non-voice emergency service (NOVES), the emergency payload to include at least one of an emergency indicator, a voice message, a video or a text message;

an attempt component to attempt to initiate an emergency session as part of an evolved packet system (EPS) mobility management (EMM) or EPS session management (ESM) procedure with a mobility management entity (MME), the emergency session initiated to deliver the emergency payload to a public service answering point (PSAP);

a store component to store the emergency payload at the UE responsive to a failure to initiate the emergency session;

a reattempt component to reattempt to initiate the emergency session to deliver the emergency payload to the PSAP; and

an acknowledgement component to receive an acknowledgement of delivery of the emergency payload to the PSAP following a successful attempt to initiate the emergency session, the emergency payload removed from the UE based on receiving the acknowledgement.

12. The apparatus of claim 11, comprising the NAS layer to also include:

an abort component to cause the reattempt component to abort reattempts to initiate the emergency session based on a number of reattempts exceeding a set number of reattempts; and

a purge component to remove the emergency payload from the UE.

13. The apparatus of claim 11, the store component to store the emergency payload with a timestamp to indicate a time when the NOVES was invoked to indicate an emergency or location information to indicate the location of the UE at the time when the NOVES was invoked.

14. The apparatus of claim 11, the failure to initiate the emergency session is caused by one of inadequate signal quality to initiate the emergency session with the MME, a wireless communication network managed by the MME is temporarily inoperable or the wireless communication network managed by the MME is congested or overloaded.

15. The apparatus of claim 11, the attempt component to attempt to initiate the emergency session as part of the EMM procedure and the NAS layer to also include a deliver component to deliver the emergency payload via an emergency attach to the MME.

16. The apparatus of claim 15, the store component to store the emergency payload responsive to the failure to initiate the emergency session comprises storing the emergency payload in an EMM context table along with a timestamp to indicate a time when the NOVES was invoked to indicate an emergency, the deliver component to deliver the stored emergency payload with the timestamp responsive to a successful reattempt to initiate the emergency session.

17. The apparatus of claim 11, the attempt component to attempt to initiate the emergency session as part of the ESM procedure comprising a deliver component for execution by the processor circuit to deliver the emergency payload upon initiation of the emergency session via one or more uplink generic NAS transport messages routed through the MME.

18. The apparatus of claim 17, the store component to store the emergency payload responsive to the failure to initiate the emergency session comprises storing the emergency payload in an ESM context table along with a timestamp to indicate a time when the NOVES was invoked to indicate an emergency, the deliver component to deliver the stored emergency payload with the timestamp responsive to a successful reattempt to initiate the emergency session.

19. The apparatus of claim 17, the one or more uplink generic NAS transport messages routed through the MME to an emergency interworking function (IWF) acting as a service center for the PSAP and to translate the one or more uplink generic NAS transport messages to deliver the emergency payload to the PSAP.

20. The apparatus of claim 19, the IWF to receive an acknowledgement of delivery of the emergency payload from the PSAP and to forward the acknowledgement to the MME for the MME to use one or more downlink generic NAS transport messages to deliver the acknowledgement to the acknowledge component.

21. At least one non-transitory machine readable medium comprising a plurality of instructions that, in response to being executed at user equipment (UE) capable of operating in compliance with one or more 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards, cause the UE to:

receive an indication that a user of the UE has invoked a non-voice emergency service (NOVES);

attempt to attach to a wireless network via an emergency access point name (APN) to deliver an emergency payload to a public service answering point (PSAP), the emergency payload to include at least one of an emergency indicator, a voice message, a video or a text message;

store the emergency payload with a timestamp to indicate a time when the NOVES was invoked, the emergency payload stored responsive to an unsuccessful attempt to attach to the wireless network;

reattempt to attach to the wireless network a set number of times;

deliver the emergency payload with the timestamp responsive to a successful attachment; and

receive an acknowledgement of delivery of the emergency payload to the PSAP and erase the stored emergency payload with the timestamp based on the acknowledgement.

22. The at least one non-transitory machine readable medium of claim 21, the set number of times comprises a configurable number of times.

23. The at least one non-transitory machine readable medium of claim 22, comprising instructions that, in response to being executed at the UE, cause the UE to abort reattempts to attach to the wireless network based on a number of reattempts exceeding the configurable number of times.

24. The at least one non-transitory machine readable medium of claim 21, the emergency payload to include at least one of an emergency indicator, a voice message, a video or a text message comprises a preconfigured emergency indicator, a pre-configured voice message, a pre-configured video or a pre-configured text message.

25. The at least one non-transitory machine readable medium of claim 21, the emergency indicator comprises a home intruder alert, a burglary in progress alert, a medical emergency, a vehicle accident, a lost person, an abduction alert or a workplace violence alert.

26. The at least one non-transitory machine readable medium of claim 21, comprising the unsuccessful attempt to attach to the wireless network via the APN is caused by one of an inadequate signal quality to attach to the wireless communication network, the wireless communication network is temporarily inoperable, the wireless communication network is congested or the APN is congested or temporarily overloaded.